I've noticed that after moving from Beta 2 to RC1(+), that my generated WSDL and the resulting client code is a little different in regards to schema targetnamespace.
My user defined exception package name is now the schema targetnamespace.
- <wsdl:types>
- <schema targetNamespace="http://Remote.WSB.xx.com" xmlns="http://www.w3.org/2001/XMLSchema">
<import namespace="http://schemas.xmlsoap.org/soap/encoding/" />
- <complexType name="AdminException">
<sequence />
</complexType>
<element name="AdminException" nillable="true" type="tns1:AdminException" />
</schema>
-------------------- Before it was like this.
- <wsdl:types>
- <schema targetNamespace="http://localhost:8080/WSB/soap/BasicEchoWS"
----- and my other tests are 'still' this way.
So the generated client code in 'some' cases is 'localhost' package, but in others like my user defined exception it is the actual package namespace.
Is this a result of a step toward support of user defined exceptions??
Is there a 'rule' to know which way to expect the generated client package structures to look?
One note of difference is that only 'basic' types are passed as parms or return types on my Web Service methods except for throwing the user defined exception. On my 'other' applications where the targetnamespace is localhost, user defined complex types are passed around.
Any ideas?
thanks,
Chris
