| SOAP schema not considered by XSD Validator by default [message #76502] |
Wed, 03 December 2008 10:02  |
Eclipse User |
|
|
|
Hello Ed,
As of now XSD and WSDL Editors doesn't import the SOAP schema by
default for the types. It shows a scary error markers in the editor as
well in the project explorer tree and lots of users actually complaint
about these error markers and we have to explain them the problem.
It would be really great if the SOAP schema is considerd when
validating by the validator which will make the workspace look clean and
also will relieve the users from keeping the SOAP schema in the workspace
and importing it explictily.
Thanks and regards,
Keshav Veerapaneni.
|
|
|
| Re: SOAP schema not considered by XSD Validator by default [message #76521 is a reply to message #76502] |
Wed, 03 December 2008 10:38  |
| Eclipse User |
|
|
|
Keshav,
Comments below.
Keshavrao wrote:
> Hello Ed,
>
> As of now XSD and WSDL Editors doesn't import the SOAP schema by
> default for the types. It shows a scary error markers in the editor as
> well in the project explorer tree and lots of users actually complaint
> about these error markers and we have to explain them the problem.
All schemas, except the schema for schemas containing the built-in XML
Schema types, must be imported explicitly. That's how the specification
is defined. Why should SOAP be special? It doesn't make sense to me.
> It would be really great if the SOAP schema is considerd when
> validating by the validator which will make the workspace look clean
> and also will relieve the users from keeping the SOAP schema in the
> workspace and importing it explictily.
It seems better to make sure that the schemas are well formed.
>
>
> Thanks and regards,
> Keshav Veerapaneni.
>
|
|
|
| Re: SOAP schema not considered by XSD Validator by default [message #603528 is a reply to message #76502] |
Wed, 03 December 2008 10:38 |
| Eclipse User |
|
|
|
Keshav,
Comments below.
Keshavrao wrote:
> Hello Ed,
>
> As of now XSD and WSDL Editors doesn't import the SOAP schema by
> default for the types. It shows a scary error markers in the editor as
> well in the project explorer tree and lots of users actually complaint
> about these error markers and we have to explain them the problem.
All schemas, except the schema for schemas containing the built-in XML
Schema types, must be imported explicitly. That's how the specification
is defined. Why should SOAP be special? It doesn't make sense to me.
> It would be really great if the SOAP schema is considerd when
> validating by the validator which will make the workspace look clean
> and also will relieve the users from keeping the SOAP schema in the
> workspace and importing it explictily.
It seems better to make sure that the schemas are well formed.
>
>
> Thanks and regards,
> Keshav Veerapaneni.
>
|
|
|
Powered by
FUDForum. Page generated in 0.03471 seconds
Home