Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 338632

Summary:

Custom validation constraint for element references shows broken reference

Product:

z_Archived

Reporter:

Stanislav Nichev <stanislav.nichev>

Component:

WTP Incubator

Assignee:

Dimitar Tenev <dimitar.tenev>

Status:

CLOSED INVALID

QA Contact:

Dimitar Tenev <dimitar.tenev>

Severity:

normal

Priority:

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows Vista

Whiteboard:

Attachments:

Description	Flags
wsdl file to reproduce the issue	none

Description Stanislav Nichev

2011-03-02 04:15:29 EST

Build Identifier: 

Hi Colleagues,

In SIE the following scenario fails:
1) Open the attached WSDL
2) Go to the DT tab and select "http://www.example.org/NewWSDLFile/"/ StructureType1/GlobalElement
3) Go to the source tab
4) Update the prefix from type="tns:GlobalElement" to type="ns0:GlobalElement"
5) Go back to the DT tab - a validation error is shown. This validation error ends with a dot, so it's comming from the custom validation :)

As a hint, the custom constraint is here: "org.eclipse.wst.sse.sieditor.model.validation.constraints.UnresolvedXsdContentsValidation"

Regards,
Stanislav

Reproducible: Always

Comment 1 Stanislav Nichev

2011-03-02 04:16:04 EST

Created attachment 190112 [details]
wsdl file to reproduce the issue

Comment 2 Stanislav Nichev

2011-06-19 08:49:00 EDT

Hi Colleagues,

Actually, the custom validation is perfect ;) (or at least in this case).
The first schema does not have an import directive to the second schema.

I'm closing this bugzilla, since it is invalid.

Regards,
Stanislav