[weld-issues] [JBoss JIRA] Commented: (CDITCK-201) InjectionIntoWebServiceEndPointTest bundles incorrect artifacts

Jozef Hartinger (JIRA) jira-events at lists.jboss.org
Mon Jan 3 09:07:17 EST 2011


    [ https://issues.jboss.org/browse/CDITCK-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572657#comment-12572657 ] 

Jozef Hartinger commented on CDITCK-201:
----------------------------------------

Looks like a web service and its client cannot be placed in the same archive when using Apache CXF.

On the client side, wsimport produces several artifacts including JAXB wrappers for method parameters and return type (IsSheepInjected.class, IsSheepInjectedResponse.class)
On the server side, apache CXF produces these wrappers during WS bootstrap i.e. org.jboss.jsr299.tck.tests.lookup.injection.non.contextual.ws.jaxws_asm.IsSheepInjected

When both the web service and its client are deployed within the same app, the JAXB class ambiguity results in "Two classes have the same XML type name" as described in CDITCK-197.

Note that other JAX-WS implementations are probably not affected.



> InjectionIntoWebServiceEndPointTest bundles incorrect artifacts
> ---------------------------------------------------------------
>
>                 Key: CDITCK-201
>                 URL: https://issues.jboss.org/browse/CDITCK-201
>             Project: CDI TCK
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Tests
>    Affects Versions: 1.0.4.CR1
>            Reporter: Jozef Hartinger
>            Assignee: Jozef Hartinger
>             Fix For: 1.0.4.CR2
>
>
> This is a problem with TCK not bundling correct web service artifacts which causes mismatch between client and server. Service has:
>  
> @WebService(name="SheepWS")
> public class SheepWSEndPoint
> {
> ...
>   @WebMethod
>   public boolean testSheepInjected() {
>      return (sheep != null) && initializerCalled;
>   }
> }
> WSDL is created by the runtime/tools  using testSheepInjected() method. So without customizations, wsimport generates the following artifacts from that wsdl:
> WEB-INF/classes/org/jboss/jsr299/tck/tests/lookup/injection/non/contextual/ws/TestSheepInjected.class
> WEB-INF/classes/org/jboss/jsr299/tck/tests/lookup/injection/non/contextual/ws/TestSheepInjectedResponse.class
> But, the bundled artifacts in the war are :
> WEB-INF/classes/org/jboss/jsr299/tck/tests/lookup/injection/non/contextual/ws/IsSheepInjected.class
> WEB-INF/classes/org/jboss/jsr299/tck/tests/lookup/injection/non/contextual/ws/IsSheepInjectedResponse.class
> and the annotations in these classes don't reflect what WSDL has(or what service is expecting)

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the weld-issues mailing list