Community
Participate
Working Groups
Take attached zip and import into the workspace Select the SyntheticSample folder and run Validate SMLIF. I get these errors : Severity and Description Path Resource Location Creation Time Id org.apache.xpath.domapi.XPathStylesheetDOM3Exception: Prefix must resolve to a namespace: smlfn Synthetic/SyntheticSample/SMLVersion/instances/Units UserUnit.xml line 360 1178141972428 108 The context "smlfn:deref(core:source)" cannot be found by the associated schematron rule Synthetic/SyntheticSample/SMLVersion/instances/Units UserUnit.xml line 432 1178141972117 104 The context "smlfn:deref(core:source)" cannot be found by the associated schematron rule Synthetic/SyntheticSample/SMLVersion/instances/Units UserUnit.xml line 432 1178141972248 106 The target requirement is of type hosting with a dmoType that matches the source's xsd type Synthetic/SyntheticSample/SMLVersion/instances/UnitLinks OSDatabaseLink.xml line 8 1178141972158 105 The target requirement is of type hosting with a dmoType that matches the source's xsd type Synthetic/SyntheticSample/SMLVersion/instances/UnitLinks OSUserLink.xml line 8 1178141972398 107 I then select the UserUnit.xml file and run the validation against it. I expect to get the same result as above since nothing has changed. In turn, I get a message that no errors are found ( the error icon is removed from the UserUnit.xml file ) Second problem is that I have also lost the other errors, flagged against different files. The only error I see now is this : Severity and Description Path Resource Location Creation Time Id The target requirement is of type hosting with a dmoType that matches the source's xsd type Synthetic/SyntheticSample/SMLVersion/instances/UnitLinks OSDatabaseLink.xml line 8 1178141972158 105 I am running with 1.5 since 1.4 compilation gives me errors ( this is another problem ). Latest code from CVS
Created attachment 65698 [details] sample
(In reply to comment #0) > I am running with 1.5 since 1.4 compilation gives me errors ( this is another > problem ). Latest code from CVS I am running with the latest code too, and compiling with 1.4, with no errors. Are you sure you're all caught up, and have no changes in your workspace?
I took the latest code from CVS and changed the JRE env to 1.4.2 I get these errors, plus some others Severity and Description Path Resource Location Creation Time Id Bundle 'org.apache.xerces' cannot be resolved org.eclipse.cosmos.rm.validation/META-INF MANIFEST.MF line 11 1178144473765 9709 DOMImplementationLS cannot be resolved to a type org.eclipse.cosmos.rm.validation/src/org/eclipse/cosmos/rm/validation/internal/smlvalidators SchematronValidator.java line 556 1178144473755 9702
Hmmm.... I added xerces as a prereq to our plug-in. Is that not typically available in an eclipse installation?
(In reply to comment #4) > Hmmm.... I added xerces as a prereq to our plug-in. Is that not typically > available in an eclipse installation? Looks like it's not there by default. Xerces is included by WTP, and is used by our code to serialize element nodes and attributes as part of our structured schematron output support. Xerces is also a standard part of 1.5 VMs. This leaves us with the following options: 1. prereq WTP 2. prereq JDK 1.5 3. add xerces.jar to the lib files in our plug-in (requires IPzilla approval) 4. rewrite the code to serialize elements for structured schematron output (there might be some code in the SML-IF editor I can reuse for this) Thoughts?
I would be surprised to find out that WTP packages xerces since this is a common component used by anybody requiring these basic functions. Can you check if this plugin is not actually part of Orbit and WTP takes it from there. We can't consider requiring WTP. If this plugin is part of the Orbit, the build should be updated to pick up the plugin from that location; I assume that the feature file should also be updated, work with Jagmit on this. Before any changes are applied to the build we need to ask for IP approval to use this plugin.
should this be a P1 instead of P3? you have it as "critical" but P3. in general, won't priority and severity always be in sync? or will you ever have one that's high and the other low?
it should be a P1 The severity is set by the bug originator and describes the severity of the problem relative to his own usage. The priority is set by the defect owner and is used to identify the defects that will be worked on first. In general, a high severity defect has a high priority but there may be situations where defects with critical severity have a P3 priority - for example, a usecase fails on platform X but platform X is not a supported platform
fyi: http://www.eclipse.org/tptp/home/documents/process/development/bugzilla.html
moving target to i8
