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

Bug 343037

Summary:

Export schema command produces invalid documents when multiple schemas are being exported

Product:

z_Archived

Reporter:

Dimitar Donchev <dimitar.donchev>

Component:

WTP Incubator

Assignee:

Dimitar Donchev <dimitar.donchev>

Status:

ASSIGNED ---

QA Contact:

Dimitar Tenev <dimitar.tenev>

Severity:

major

Priority:

Version:

unspecified

Target Milestone:

---

Hardware:

OS:

Windows 7

Whiteboard:

Attachments:

Description	Flags
Try to export *ns2 namespaced schema from this doc	none
to reproduce	none
patch fixing the DOM migration issue	none

Description Dimitar Donchev

2011-04-16 10:06:52 EDT

Export schema command produces new XML schemas with empty <import" schema location="XXXXXXXXXXXXX"/> attributes!

Try exporting http://org.dido.ns from the attached wsdl!
See the errors in 2 of the three extracted schemas.

Best Regards,
Dido

Comment 1 Dimitar Donchev

2011-04-16 10:07:37 EDT

Created attachment 193416 [details]
Try to export *ns2 namespaced schema from this doc

Comment 2 Dimitar Donchev

2011-04-16 10:09:39 EDT

Created attachment 193417 [details]
to reproduce

Try exporting  http://org.dido.ns2 from this doc. See the producet artefacts

Comment 3 Dimitar Donchev

2011-04-16 10:13:19 EDT

Comment on attachment 193416 [details]
Try to export *ns2 namespaced schema from this doc

sorry, chose a wrong file to attach.

Comment 4 Stanislav Nichev

2011-06-11 15:51:57 EDT

Created attachment 197845 [details]
patch fixing the DOM migration issue

Hi Colleagues,

I have prepared a fix for this issue. The problem was in the DOM migration.
The logic relied on element.getAttribute() to return null when there was no attribute defined.

Regards,
Stanislav