Bugzilla – Full Text Bug Listing
| Summary: | Issues with WSDL where schema has types referring to the namespace defined at the definition level and not at the schema level | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | seth <asethiya> | ||||
| Component: | wst.wsdl | Assignee: | wst.wsdl <wst.wsdl-inbox> | ||||
| Status: | NEW --- | QA Contact: | Keith Chong <keith.chong.ca> | ||||
| Severity: | normal | ||||||
| Priority: | P3 | ||||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Hi Seth, can you please attach your test case? Thanks. Created attachment 183434 [details] Teste Case Sample I observed that since schema does not define xmlns:s0="http://microsoft.com/webservices/" classA could not be resolved. <s:element minOccurs="0" maxOccurs="1" name="ReturnDeadNameSpaceResult" type="s0:ClassA" /> |
Build Identifier: 20100218-1602 If a namespace xmlns:somenamespace is defined at wsdl level and inline schema type referes to the namespace, eclipse demands that namespace should also be defined at the inline schema level. It should not be necessary and eclipse should be able to resolve the namespace in inline schema from the wsdl namespaces. Reproducible: Always Steps to Reproduce: 1.Create a WSDL with definition defining namespace xmlns:ti="some uri" 2.Define inline schema and create a type with basetype referring to namespace ti. <complextype name="name" extension="ti:someType". Do not define xmlns:ti="some uri at the schema level" 3.Eclipse fails to resolve base type for complex type name.