[jbossws-issues] [JBoss JIRA] Commented: (JBWS-2193) Namespace issue for SEIs extending common interface
[
https://jira.jboss.org/jira/browse/JBWS-2193?page=com.atlassian.jira.plug...
]
Richard Opalka commented on JBWS-2193:
--------------------------------------
I was able to achieve what user wants using the following code:
/////////////
// SEI A
/////////////
package test.namespace;
import javax.xml.ws.*;
import javax.jws.WebService;
@WebService
(
name = "A",
targetNamespace = "a.com"
)
public interface A extends C
{
@RequestWrapper(className="test.namespace.a.One",
targetNamespace="a.com")
@ResponseWrapper(className="test.namespace.a.OneResponse",
targetNamespace="a.com")
public void one();
@RequestWrapper(className="test.namespace.a.Zero",
targetNamespace="a.com")
@ResponseWrapper(className="test.namespace.a.ZeroResponse",
targetNamespace="a.com")
public void zero();
}
/////////////
// SEI B
/////////////
package test.namespace;
import javax.xml.ws.*;
import javax.jws.WebService;
@WebService
(
name = "B",
targetNamespace = "b.com"
)
public interface B extends C
{
@RequestWrapper(className="test.namespace.b.Two",
targetNamespace="b.com")
@ResponseWrapper(className="test.namespace.b.TwoResponse",
targetNamespace="b.com")
public void two();
@RequestWrapper(className="test.namespace.b.Zero",
targetNamespace="b.com")
@ResponseWrapper(className="test.namespace.b.ZeroResponse",
targetNamespace="b.com")
public void zero();
}
Using Request/Response wrappers helps to achieve that.
Namespace issue for SEIs extending common interface
---------------------------------------------------
Key: JBWS-2193
URL: https://jira.jboss.org/jira/browse/JBWS-2193
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-2.0.1.SP2, jbossws-2.0.2, jbossws-native-2.0.3,
jbossws-native-3.0.1
Environment: WinXP,JBOSS4.2.2 and JBOSSWS 2.0.1 or JBOSSWS2.0.3
Reporter: Yogesh B
Assignee: Richard Opalka
Fix For: jbossws-native-3.0.3
Attachments: test-JBWS-2193.zip
HI Team,
I have two webservices with separate SEIs (say A in targetNamespace X and B in
targetNamespace Y) each one extending a common interface (say C)
When I generated the WSDLs using the wsprovide tool, I can see the two wsdl files each
containing the schema for the operations of common interface C getting generated as part
of the SEI A's namespace and SEI B's namespace individually which is expected as
per the standards..
I deployed these webservices in JBoss4.2.2 with JBossWS2.0.3. When I tried to open the
wsdls from the JBoss server, the wsdls generated from the jboss server seems to have the
operations of common interface C available as part of the SEI A. But for the SEI B, the
operations of common interface C are imported from SEI A's namespace.
I was expecting the operations of common interface C to be available in each individual
webservice's namespace as unique operations.
I also tried to explicitly specify the XmlType annotation in the common interface class C
to have a common namespace but even this attempt got failed.
Pls let me know how to workaround this problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira