[JBoss JIRA] Created: (JBWS-2018) JavatoWSDL Package to Namespace mapping does not support multiple packages
1:56 a.m.
JavatoWSDL Package to Namespace mapping does not support multiple packages
--------------------------------------------------------------------------
Key: JBWS-2018
URL: http://jira.jboss.com/jira/browse/JBWS-2018
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: tools-jaxrpc
Reporter: Magesh Kumar B
Assigned To: Magesh Kumar B
Priority: Minor
Fix For: jbossws-native-2.0.4
Consider the following WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name='MySEIService'
targetNamespace='http://javatype.mycompany.com'
xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://other.com'
xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
xmlns:tns='http://javatype.mycompany.com'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<types>
<schema targetNamespace='http://other.com'
xmlns='http://www.w3.org/2001/XMLSchema'
xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:tns='http://other.com'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<complexType name='TestException'>
<sequence/>
</complexType>
<element name='TestException' type='tns:TestException'/>
</schema>
</types>
<message name='MySEI_testException'/>
<message name='MySEI_testExceptionResponse'/>
<message name='TestException'>
<part element='ns1:TestException' name='TestException'/>
</message>
<portType name='MySEI'>
<operation name='testException'>
<input message='tns:MySEI_testException'/>
<output message='tns:MySEI_testExceptionResponse'/>
<fault message='tns:TestException' name='TestException'/>
</operation>
</portType>
<binding name='MySEIBinding' type='tns:MySEI'>
<soap:binding style='rpc'
transport='http://schemas.xmlsoap.org/soap/http'/>
<operation name='testException'>
<soap:operation soapAction=''/>
<input>
<soap:body namespace='http://javatype.mycompany.com'
use='literal'/>
</input>
<output>
<soap:body namespace='http://javatype.mycompany.com'
use='literal'/>
</output>
<fault name='TestException'>
<soap:fault name='TestException' use='literal'/>
</fault>
</operation>
</binding>
<service name='MySEIService'>
<port binding='tns:MySEIBinding' name='MySEIPort'>
<soap:address location='REPLACE_WITH_ACTUAL_URL'/>
</port>
</service>
</definitions>
Using the following wstools config:
<configuration xmlns="http://www.jboss.org/jbossws-tools">
<global>
<package-namespace package="com.other"
namespace="http://other.com"/>
<package-namespace package="com.mycompany.javatype"
namespace="http://javatype.mycompany.com"/>
</global>
<wsdl-java file="MySEIService.wsdl">
<mapping file="jaxrpc-mapping.xml" />
</wsdl-java>
</configuration>
The TestException class is not generated in the com.other package.
--
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
2:14 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2018) JavatoWSDL Package to Namespace mapping does not support multiple packages
[ http://jira.jboss.com/jira/browse/JBWS-2018?page=all ]
Magesh Kumar B updated JBWS-2018:
---------------------------------
Description:
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.
was:
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 ignores the global mappings and generates the namespace derived from teh class
packages.
JavatoWSDL Package to Namespace mapping does not support multiple
packages
--------------------------------------------------------------------------
Key: JBWS-2018
URL: http://jira.jboss.com/jira/browse/JBWS-2018
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: tools-jaxrpc
Reporter: Magesh Kumar B
Assigned To: Magesh Kumar B
Priority: Minor
Fix For: jbossws-native-2.0.4
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.
--
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
2:14 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2018) JavatoWSDL Package to Namespace mapping does not support multiple packages
[ http://jira.jboss.com/jira/browse/JBWS-2018?page=all ]
Magesh Kumar B updated JBWS-2018:
---------------------------------
Workaround Description: Manually edit the wsdl. (was: Manually move the classes to
their appropriate packages.)
Description:
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 ignores the global mappings and generates the namespace derived from teh class
packages.
was:
Consider the following WSDL:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name='MySEIService'
targetNamespace='http://javatype.mycompany.com'
xmlns='http://schemas.xmlsoap.org/wsdl/' xmlns:ns1='http://other.com'
xmlns:soap='http://schemas.xmlsoap.org/wsdl/soap/'
xmlns:tns='http://javatype.mycompany.com'
xmlns:xsd='http://www.w3.org/2001/XMLSchema'>
<types>
<schema targetNamespace='http://other.com'
xmlns='http://www.w3.org/2001/XMLSchema'
xmlns:soap11-enc='http://schemas.xmlsoap.org/soap/encoding/'
xmlns:tns='http://other.com'
xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance'>
<complexType name='TestException'>
<sequence/>
</complexType>
<element name='TestException' type='tns:TestException'/>
</schema>
</types>
<message name='MySEI_testException'/>
<message name='MySEI_testExceptionResponse'/>
<message name='TestException'>
<part element='ns1:TestException' name='TestException'/>
</message>
<portType name='MySEI'>
<operation name='testException'>
<input message='tns:MySEI_testException'/>
<output message='tns:MySEI_testExceptionResponse'/>
<fault message='tns:TestException' name='TestException'/>
</operation>
</portType>
<binding name='MySEIBinding' type='tns:MySEI'>
<soap:binding style='rpc'
transport='http://schemas.xmlsoap.org/soap/http'/>
<operation name='testException'>
<soap:operation soapAction=''/>
<input>
<soap:body namespace='http://javatype.mycompany.com'
use='literal'/>
</input>
<output>
<soap:body namespace='http://javatype.mycompany.com'
use='literal'/>
</output>
<fault name='TestException'>
<soap:fault name='TestException' use='literal'/>
</fault>
</operation>
</binding>
<service name='MySEIService'>
<port binding='tns:MySEIBinding' name='MySEIPort'>
<soap:address location='REPLACE_WITH_ACTUAL_URL'/>
</port>
</service>
</definitions>
Using the following wstools config:
<configuration xmlns="http://www.jboss.org/jbossws-tools">
<global>
<package-namespace package="com.other"
namespace="http://other.com"/>
<package-namespace package="com.mycompany.javatype"
namespace="http://javatype.mycompany.com"/>
</global>
<wsdl-java file="MySEIService.wsdl">
<mapping file="jaxrpc-mapping.xml" />
</wsdl-java>
</configuration>
The TestException class is not generated in the com.other package.
JavatoWSDL Package to Namespace mapping does not support multiple
packages
--------------------------------------------------------------------------
Key: JBWS-2018
URL: http://jira.jboss.com/jira/browse/JBWS-2018
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: tools-jaxrpc
Reporter: Magesh Kumar B
Assigned To: Magesh Kumar B
Priority: Minor
Fix For: jbossws-native-2.0.4
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 ignores the global mappings and generates the namespace derived from teh class
packages.
--
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
6:51 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2018) JavatoWSDL Package to Namespace mapping does not support multiple packages
[ http://jira.jboss.com/jira/browse/JBWS-2018?page=comments#action_12401918 ]
Magesh Kumar B commented on JBWS-2018:
--------------------------------------
Fixed and available in trunk for release 2.0.4. Will add a test case soon and resolve the
issue.
JavatoWSDL Package to Namespace mapping does not support multiple
packages
--------------------------------------------------------------------------
Key: JBWS-2018
URL: http://jira.jboss.com/jira/browse/JBWS-2018
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: tools-jaxrpc
Reporter: Magesh Kumar B
Assigned To: Magesh Kumar B
Priority: Minor
Fix For: jbossws-native-2.0.4
Time Spent: 3 days, 4 hours
Remaining Estimate: 0 minutes
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.
--
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
7:50 a.m.
New subject: [JBoss JIRA] Commented: (JBWS-2018) JavatoWSDL Package to Namespace mapping does not support multiple packages
[ http://jira.jboss.com/jira/browse/JBWS-2018?page=comments#action_12401932 ]
Magesh Kumar B commented on JBWS-2018:
--------------------------------------
[junit] Running org.jboss.test.ws.tools.jbws2018.JBWS2018TestCase
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.828 sec
JavatoWSDL Package to Namespace mapping does not support multiple
packages
--------------------------------------------------------------------------
Key: JBWS-2018
URL: http://jira.jboss.com/jira/browse/JBWS-2018
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: tools-jaxrpc
Reporter: Magesh Kumar B
Assigned To: Magesh Kumar B
Priority: Minor
Fix For: jbossws-native-2.0.4
Time Spent: 3 days, 5 hours
Remaining Estimate: 0 minutes
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.
--
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
2:36 a.m.
New subject: [JBoss JIRA] Reopened: (JBWS-2018) JavatoWSDL Package to Namespace mapping does not support multiple packages
[ http://jira.jboss.com/jira/browse/JBWS-2018?page=all ]
Magesh Kumar B reopened JBWS-2018:
----------------------------------
JavatoWSDL Package to Namespace mapping does not support multiple
packages
--------------------------------------------------------------------------
Key: JBWS-2018
URL: http://jira.jboss.com/jira/browse/JBWS-2018
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: tools-jaxrpc
Reporter: Magesh Kumar B
Assigned To: Magesh Kumar B
Priority: Minor
Fix For: jbossws-native-2.0.4
Time Spent: 3 days, 5 hours
Remaining Estimate: 0 minutes
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.
--
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
6414
days inactive
6423
days old
jbossws-issues@lists.jboss.org
5 comments
1 participants
participants (1)
-
Magesh Kumar B (JIRA)