-
Bug
-
Resolution: Done
-
Minor
-
None
-
None
-
Workaround Exists
-
Consider the following SEI:
package org.jboss.test.ws.jbws1217;
public interface MySEI extends java.rmi.Remote
{
public void testException() throws com.other.exception.TestException, java.rmi.RemoteException;
}
And the additional classes:
package com.other.exception;
public class TestException
extends com.other.base.BaseException{
public TestException(){
}
}
package com.other.base;
public class BaseException
extends Exception{
public BaseException(){
}
}
Using the following wstools config:
<configuration xmlns="http://www.jboss.org/jbossws-tools">
<global>
<package-namespace package="com.other.base" namespace="http://com.other.base"/>
<package-namespace package="com.other.exception" namespace="http://com.other.exception"/>
</global>
<java-wsdl>
<service name="MySEI" style="rpc" endpoint="org.jboss.test.ws.jbws1217.MySEI"/>
<namespaces target-namespace="http://org.jboss.test.ws.jbws1217" type-namespace="http://org.jboss.test.ws.jbws1217"/>
<mapping file="jaxrpc-mapping.xml" />
<webservices ejb-link="MyEJB"/>
</java-wsdl>
</configuration>
The WSDL generated ignores the global mappings and the namespace is derived from the class packages.
- is incorporated by
-
JBPAPP-2327 JBossWS - JavatoWSDL Package to Namespace mapping does not support multiple packages
- Closed
- is related to
-
JBWS-1217 WSDLtoJava Namespace to package mapping does not support multiple namespaces
- Closed