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

[Jozef Hartinger (JIRA)]

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

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

Aaah, there actually is a way of excluding the test already http://anonsvn.jboss.org/repos/weld/cdi-tck/branches/1.0/impl/src/main/java/org/jboss/jsr299/tck/impl/WebProfileMethodSelector.java

> 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