Namespace incorrect for complex types ------------------------------------- Key: JBWS-1509 URL: http://jira.jboss.com/jira/browse/JBWS-1509 Project: JBoss Web Services Issue Type: Bug Security Level: Public (Everyone can see) Components: jaxws Affects Versions: jbossws-2.0.0.CR2, jbossws-1.0.4, jbossws-1.0.3.SP1 Environment: WindowsXP, Sun java 1.5.0_10, jboss4.0.5/jboss5.0.0.Beta1 Reporter: Peter Yuill Using a JSR181 pojo service with a targetNamespace set in the @WebService annotation creates WSDL with incorrect targetNamespace for some referenced complex types. The correct namespace is determined for types referenced directly, but the default namespace is allocated to any indirectly referenced type. For example the following service code: @WebService(targetNamespace="http://test.com") @SOAPBinding(style=SOAPBinding.Style.RPC, use=SOAPBinding.Use.LITERAL) public class TestWS implements ServiceLifecycle { @WebMethod public Type1 getType1() {return new Type1();} @WebMethod public Type2[] getType2() {return new Type2[0];} @WebMethod public Type3 getType3() {return new Type3();} generates the correct namespace (http://test.com) for Type1, Type3 and Type2.Array, but generates the default (http://test/jaws) for Type2 and Type4 (referenced by Type3). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira