| Summary: | [Bugzilla] No validation error when del imported schema | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | Stanislav Nichev <stanislav.nichev> | ||||
| Component: | WTP Incubator | Assignee: | Dimitar Tenev <dimitar.tenev> | ||||
| Status: | NEW --- | QA Contact: | Dimitar Tenev <dimitar.tenev> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows Vista | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Created attachment 189818 [details]
reproduce data
|
Build Identifier: Hi Colleagues, In SIE 731 the following scenario fails: 1) Copy the attached file into the workspace 2) Open the attached wsdl file in the SIE 3) Remove the first schema "http://www.example.org/NewWSDLFile/" 4) No validation error shown 5) Go to "http://namespace1"/StructureType3/NewOperation 6) Type shown as "unresolved" Regards, Stanislav Memo 12.10.2010 14:30:54 Stanislav Nichev Probably a related issue: 1) Go to "http:/namespace1" 2) Delete the xsd:import to the "http://www.example.org/NewWSDLFile/" 3) No validation error as well Memo 27.10.2010 12:49:51 Stanislav Nichev Hi Colleagues, Fix has been submitted. What was fixed: element references. Still, if model reconcilation is started, the references are "fixed" due to the unupdated EMF XSD model. Bugzilla needs to be reported for the following case: 1) Element references to the deleted schema are not "broken" 2) Type references to the deleted schema are not "broken" I suppose that the same issue can be found in attribute references, attribute groups and xsd groups. A workaround can be developed - a custom constraint for the xsd model to validate the mentioned cases. The error message should be smth like: "XSD: Element reference <(><<)>(> <<(><<)>)>targetNamespace>#<element_name> is unresolved." A similar messages need to be added for the other cases. Best way: the original xsd messages to be reused. Regards, Stanislav Memo 03.11.2010 13:20:19 Stanislav Nichev Hi Colleagues, The constraint was implemented with the fix of CSN 0003200091 2010. Unit test has been update to cover the fix. Bugzilla needs to be reported in order to close this issue. Regards, Stanislav Reproducible: Always