Newbie: How do you modify the java package/namespace mapping

[summer.hill]

I am developing a series of JSR181 annotated webservices that I automatically deploy to the jboss deploy directory. JBoss correctly deploys the ejbs and the webservices are available and all working fine.

BUT, I can't find a way of configuring how the java packages containing custom java classes are mapped to namespaces in the generated wsdl. This seems to be possible using the xml configuration for wstools, but I am not using wstools as I am allowing JBoss to do all the deployment for me.

The wstools conifguration xsd has the following element which is probably what I need to set somehow WITHOUT using wstools.

<xs:sequence>
 <xs:element name="package-namespace" type="ns1:pkgNSType" minOccurs="0" maxOccurs="unbounded">
 <xs:annotation>
 <xs:documentation>Allows customization of the java package name to xml namespace mapping. This is specified in package/namespace element pairs.</xs:documentation>
 </xs:annotation>
 </xs:element>
 </xs:sequence>

How can I configure the WSDL generation in JBOSS to modify java package to namespace mapping????

Thanks

James

[thomas.diesler]

Have a look at @WebService (targetNamespace)

[summer.hill]

Thanks for the tip Thomas.

I've already done this for my @WebService annotations. The real problem I am having is with passing java objects as parameter or return values from the @WebMethods.

The WSDL generated places the java objects in their own WSDL namespace named after the java package in which they reside. BUT, there is a DUPLICATE definition of each java object in the WSDL namespace as well where the @WebService (targetNamespace) is defined. This seems a little strange.

What I really want to do, is have all java objects in a shared 'types' namespace and have every other namespace reference them (like a header file).

Surely this can be achieved?

I am using jboss-ws 1.0.2.

[jpremji]

I am having the same issue. It would seem that even after specifying the target namespace, the wsdl that is generated contains 2 complex elements of the same java type. This then causes confusion to the client when calling the method that would return or accept this type.

[stevenh]

"jpremji" wrote:
I am having the same issue. It would seem that even after specifying the target namespace, the wsdl that is generated contains 2 complex elements of the same java type. This then causes confusion to the client when calling the method that would return or accept this type.

I have been poking at this problem a little to try, I have found that the schema generation is a little fragile. Ie i would have my complex object in one schema, change a method name and it would split it out to two schemas and import the second one into the first.

http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3968857

My work around was to generate the schemas so i was happy with them, and use the wsdllocation attribute on the webservice annotation. This ment that it would present the correct wsdl and would still actually respond to it.

Steve.

[thomas.diesler]

Yes, WSDL generation for JSR-181 only work s for trivial use cases. This is because JSR181 should really not work at all for JAXRPC. It is targeted for JAXWS where all marshalling unmarshhalling is delegated to JAXB

Please monitor

http://jira.jboss.org/jira/browse/JBWS-1101