Schema inside of WSDL doc

["Murray, Bryan P." <br...@hp.com>]

I have a question. I have been modifying WSDL and schema to get a feel
for how Wsdl2Java handles differing formats. I have discovered 2 things
that I am pretty sure are correct WSDL, but are not accepted by the
tool.

1) I moved all of my schema stuff into a separate file with a different
namespace from the WSDL document, and then added an import element as a
child of the schema element that is a child of the wsdl:types element.
Wsdl2Java now fails with a NullPointerException in
getResourcePropertyNames(WsrfWsdlUtils.java:107).

2) To work around the previous problem, I tried removing the import
statement, and added a 2nd schema element as a child of the wsdl:types
element containing my entire schema document. This also failed, but if I
switched the order of the schema elements it works. 

>From this I deduce 2 things:

A) The schema import does not actually read the remote schema document.

B) The tool only does something with the first schema child element of
wsdl:types.


I would appreciate a confirmation of these deductions. Problem #2 is not
important to me at this time. However, problem #1 gets in my way as it
is my favorite method of constructing WSDL documents.

Bryan

---------------------------------------------------------------------
To unsubscribe, e-mail: apollo-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: apollo-dev-help@ws.apache.org

Re: Schema inside of WSDL doc

[Ian Springer <ip...@apache.org>]

Hi Bryan,

The new alpha2 release I just posted should support schema 
imports/includes as well as multiple schema elements within the 
wsdl:types. Let me know how this works for you.

Regards,
Ian

Murray, Bryan P. wrote:

>I have a question. I have been modifying WSDL and schema to get a feel
>for how Wsdl2Java handles differing formats. I have discovered 2 things
>that I am pretty sure are correct WSDL, but are not accepted by the
>tool.
>
>1) I moved all of my schema stuff into a separate file with a different
>namespace from the WSDL document, and then added an import element as a
>child of the schema element that is a child of the wsdl:types element.
>Wsdl2Java now fails with a NullPointerException in
>getResourcePropertyNames(WsrfWsdlUtils.java:107).
>
>2) To work around the previous problem, I tried removing the import
>statement, and added a 2nd schema element as a child of the wsdl:types
>element containing my entire schema document. This also failed, but if I
>switched the order of the schema elements it works. 
>
>>>From this I deduce 2 things:
>
>A) The schema import does not actually read the remote schema document.
>
>B) The tool only does something with the first schema child element of
>wsdl:types.
>
>
>I would appreciate a confirmation of these deductions. Problem #2 is not
>important to me at this time. However, problem #1 gets in my way as it
>is my favorite method of constructing WSDL documents.
>
>Bryan
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: apollo-dev-unsubscribe@ws.apache.org
>For additional commands, e-mail: apollo-dev-help@ws.apache.org
>
>
>
>  
>


---------------------------------------------------------------------
To unsubscribe, e-mail: apollo-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: apollo-dev-help@ws.apache.org