[jbossws-issues] [JBoss JIRA] Updated: (JBWS-2193) Namespace issue for SEIs extending common interface

Wed Jun 11 17:24:15 EDT 2008

     [ http://jira.jboss.com/jira/browse/JBWS-2193?page=all ]

Alessio Soldano updated JBWS-2193:
----------------------------------

    Fix Version/s:  jbossws-native-3.0.3

> Namespace issue for SEIs extending common interface
> ---------------------------------------------------
>
>                 Key: JBWS-2193
>                 URL: http://jira.jboss.com/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.2,  jbossws-native-2.0.3, jbossws-2.0.1.SP2, jbossws-native-3.0.1
>         Environment: WinXP,JBOSS4.2.2 and JBOSSWS 2.0.1 or JBOSSWS2.0.3
>            Reporter: Yogesh B
>             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: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira