[jboss-jira] [JBoss JIRA] (AS7-3106) @WebServiceProvider annotation is not processed when implementation class loaded from dependent module

[Jason Greene (Closed) (JIRA)]

     [ https://issues.jboss.org/browse/AS7-3106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Greene closed AS7-3106.
-----------------------------

         Assignee: Jason Greene  (was: Alessio Soldano)
    Fix Version/s: No Release
                       (was: 7.1.0.CR1)
       Resolution: Won't Fix


For performance reasons static modules are indexed for annotations by default.

You can however index them at build time and include the index in the module (either within the jar or as a static file). You  then must use the annotations dependency option when importing the module. Take a look at the resteasy modules in AS7 for example of how to do this.
                
> @WebServiceProvider annotation is not processed when implementation class loaded from dependent module
> ------------------------------------------------------------------------------------------------------
>
>                 Key: AS7-3106
>                 URL: https://issues.jboss.org/browse/AS7-3106
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Web Services
>    Affects Versions: 7.1.0.Beta1b
>            Reporter: Peter Skopek
>            Assignee: Jason Greene
>             Fix For: No Release
>
>         Attachments: picketlink-sts-correct.war, picketlink-sts.war
>
>
> When deploying picketlink-sts.war with dependent module org.picketlink specified in META-INF/jboss-deployment-structure.xml which contains class referred to as servlet (in web.xml) annotated with @WebServiceProvider it is deployed as servlet and not as webservice.
> If I copy the class file to war to WEB-INF/classes it works as expected.
> See two attached .war files.
> Only correct one creates following log entries:
> {noformat}
> 17:30:33,595 INFO  [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-5) Add Service
>  id=PicketLinkSTS
>  address=http://localhost:8080/picketlink-sts-correct
>  implementor=org.picketlink.identity.federation.core.wstrust.PicketLinkSTS
>  invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
>  serviceName={urn:picketlink:identity-federation:sts}PicketLinkSTS
>  portName={urn:picketlink:identity-federation:sts}PicketLinkSTSPort
>  wsdlLocation=null
>  mtomEnabled=false
> 17:30:33,597 INFO  [org.jboss.ws.common.management.DefaultEndpointRegistry] (MSC service thread 1-5) register: jboss.ws:context=picketlink-sts-correct,endpoint=PicketLinkSTS
> 17:30:33,859 INFO  [org.apache.cxf.service.factory.ReflectionServiceFactoryBean] (MSC service thread 1-5) Creating Service {urn:picketlink:identity-federation:sts}PicketLinkSTS from WSDL: WEB-INF/wsdl/PicketLinkSTS.wsdl
> 17:30:34,070 INFO  [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-5) Setting new service endpoint address in wsdl: http://localhost:8080/picketlink-sts/PicketLinkSTS
> 17:30:34,132 INFO  [org.jboss.wsf.stack.cxf.transport.AddressRewritingEndpointInfo] (MSC service thread 1-5) Setting new service endpoint address in wsdl: http://localhost:8080/picketlink-sts-correct
> 17:30:34,179 INFO  [org.apache.cxf.endpoint.ServerImpl] (MSC service thread 1-5) Setting the server's publish address to be http://localhost:8080/picketlink-sts-correct
> {noformat}
>   

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira