Community
Participate
Working Groups
Today, user has to run the adapter before getting validation done. There are two types of validation done by GLA runtime: 1) It does schema validation on the GLA adapter file itself against the GLA adapter schema files. This is done when configuring the adapter in the runtime. When in the GLA editor this validation is done when the adapter file is saved and also when it is run. In both cases errors found are shown in the Problems view. Note, this schema validation is only done when eclipse is running with an IBM JDK. The Sun JDK does support XML schema validation. I don't know what the Sun XML validator is that Lennart mentioned. 2) In the GLA formatter component when it creates the CBE, it checks for all of the mandatory CBE fields before returning the CBE. If the CBE is missing mandatory fields, an error message is logged and the CBE is not returned. When in the GLA editor the GLA formatter is only executed when the adapter file is run and any missing CBE field errors found are displayed in the Problems view. The GLA runtime cannot perform any validation on the CBE's it generates until it tries to generate them during execution of the adapter. The GLA only knows about CBE's in the formatter and outputter components. Checking for the presence of rules for the mandatory CBE fields when the adapter is saved would have to be done by the GLA editor UI. It sounds like Lennart wants that kind of CBE validation.
Please raise the priority to P2
Update component
Candidate for 4.2
Adding myself to cc list so I will get notified when "Design Summary" section of the design document is completed.
My comments in upper case: In the GLA formatter component when it creates the CBE, it checks for all of the mandatory CBE fields before returning the CBE. If the CBE is missing mandatory fields, an error message is logged IN HGLA.LOG
Here's the user comment: Q: 3A1 (2) Could this be improved by TPTP bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=104487? A: Yes. CBE validation would improve this to a 3. If the GLA would then tell the user what to update, this could potentially score higher. (i.e., don't just say "CBE Validation failed" but bring the user to the exact field that failed, provide a recommendation on how to correct the error, and allow the user to correct.) Here's the definition for 3A1: Anticipates and prevents problems - Applications need to be operational for extended periods of time. To reduce downtime, offerings need to be self-healing where possible so problems don't interrupt operations.
fixed A validate button is available on the Parser and parser subelements. The action validates the completeness of the parser subcomponents by validating the content against the cbe schema
The following docs have been checked into HEAD (for the TPTP 4.2 release): org.eclipse.tptp.monitoring.doc.isv/concepts/cadapt.html org.eclipse.tptp.monitoring.doc.isv/tasks/tcreatingadapt.html
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
