[jboss-jira] [JBoss JIRA] (AS7-3285) Annotated classes excluded in module import are still processed during deployment.

[Stuart Douglas (JIRA)]

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

Stuart Douglas updated AS7-3285:
--------------------------------

    Fix Version/s: 7.1.1.Final
                       (was: 7.1.0.Final)


This is actually a non-trivial task, as it will require some Jandex changes to support filtering, and this looks like it will add a fair bit of complexity for what seems to be an edge case. 

I am also not convinced that your example is a valid use case, picketlink is part of the server, IMHO the end user should not have to use jboss-deployment-structure.xml and annotation imports to make use of picketlinks functionality.  

Another thing to note is that if an end user wants to do something like this the jandex ant task can simply be configured to exclude classes when it is indexing, using the normal ant FileSet excludes.  
                
> Annotated classes excluded in module import are still processed during deployment.  
> ------------------------------------------------------------------------------------
>
>                 Key: AS7-3285
>                 URL: https://issues.jboss.org/browse/AS7-3285
>             Project: Application Server 7
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 7.1.0.CR1b
>            Reporter: Peter Skopek
>            Assignee: Stuart Douglas
>              Labels: eap6_prd_req
>             Fix For: 7.1.1.Final
>
>         Attachments: picketlink-sts.war
>
>
> Annotation attribute works, but import filter is not taken into account and all annotations found in dependant module are processed.
> See in following server log snippet that @WebServiceProvider at class org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP is processed despite the class was ordered to not be imported in jboss-deployment-structure.xml.
> 11:15:08,018 INFO [org.jboss.as.server.deployment] (MSC service thread 1-2) Starting deployment of "picketlink-sts.war"
> 11:22:31,125 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-5) Add Service
> id=PicketLinkSTS
> address=http://localhost:8080/picketlink-sts
> 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
> 11:22:31,126 INFO [org.jboss.wsf.stack.cxf.metadata.MetadataBuilder] (MSC service thread 1-5) Add Service
> id=org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP
> address=http://localhost:8080/picketlink-sts/SOAPSAMLXACMLPDP
> implementor=org.picketlink.identity.federation.core.pdp.SOAPSAMLXACMLPDP
> invoker=org.jboss.wsf.stack.cxf.JBossWSInvoker
> serviceName={urn:picketlink:identity-federation:pdp}SOAPSAMLXACMLPDP
> portName={urn:picketlink:identity-federation:pdp}SOAPSAMLXACMLPort
> wsdlLocation=null
> mtomEnabled=false
> Content of my jboss-deployment-structure.xml
> {noformat}
> <jboss-deployment-structure>
>   <deployment>
>     <!-- Add picketlink module dependency -->
>     <dependencies>
>       <module name="org.picketlink" annotations="true">
>         <imports>
>            <exclude path="org/picketlink/identity/federation/core/pdp/**"/>
>         </imports>
>       </module>
>     </dependencies>
>   </deployment>
> </jboss-deployment-structure>
> {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