[JBoss JIRA] (AS7-3285) Annotated classes excluded in module import are still processed during deployment.
4:48 a.m.
Peter Skopek created AS7-3285:
---------------------------------
Summary: 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: Jason Greene
Fix For: 7.1.0.Final
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
4:50 a.m.
[
https://issues.jboss.org/browse/AS7-3285?page=com.atlassian.jira.plugin.s...
]
Peter Skopek updated AS7-3285:
------------------------------
Attachment: picketlink-sts.war
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: Jason Greene
Fix For: 7.1.0.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
4:54 a.m.
[
https://issues.jboss.org/browse/AS7-3285?page=com.atlassian.jira.plugin.s...
]
Peter Skopek updated AS7-3285:
------------------------------
Steps to Reproduce:
1. create following security domains:
{noformat}
<security-domain name="jmx-console"
cache-type="default">
<authentication>
<login-module code="UsersRoles"
flag="required">
<module-option name="usersProperties"
value="users.properties"/>
<module-option name="rolesProperties"
value="roles.properties"/>
</login-module>
</authentication>
</security-domain>
<security-domain name="idp"
cache-type="default">
<authentication>
<login-module code="UsersRoles"
flag="required">
<module-option name="usersProperties"
value="users.properties"/>
<module-option name="rolesProperties"
value="roles.properties"/>
</login-module>
</authentication>
</security-domain>
<security-domain name="sp"
cache-type="default">
<authentication>
<login-module
code="org.picketlink.identity.federation.bindings.jboss.auth.SAML2LoginModule"
flag="required"/>
</authentication>
</security-domain>
{noformat}
2. Deploy attached file (picketlink-sts.war)
3. check server log
was:Deploy attached file.
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: Jason Greene
Fix For: 7.1.0.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
4:56 a.m.
[
https://issues.jboss.org/browse/AS7-3285?page=com.atlassian.jira.plugin.s...
]
Peter Skopek reassigned AS7-3285:
---------------------------------
Assignee: Stuart Douglas (was: Jason Greene)
Stuart agreed to take care of this.
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
Fix For: 7.1.0.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
6:25 p.m.
[
https://issues.jboss.org/browse/AS7-3285?page=com.atlassian.jira.plugin.s...
]
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
10:08 p.m.
[
https://issues.jboss.org/browse/AS7-3285?page=com.atlassian.jira.plugin.s...
]
Jason Greene commented on AS7-3285:
-----------------------------------
I agree. It makes more sense to do this at index generation time. I had assumed this was
about deployments, which would have made a lot more sense.
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
3:58 a.m.
[
https://issues.jboss.org/browse/AS7-3285?page=com.atlassian.jira.plugin.s...
]
Peter Skopek commented on AS7-3285:
-----------------------------------
There are three web apps in PicketLink which all have their servlets packed in
picketlink-fed-2.0.1.final.jar.
All the three apps are part of PickeLink and user can select which one will deploy.
My use case is based on this fact.
I don't think that users should mess with jandex on picketlink module to produce
correct web app they need for deployment.
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
4:23 a.m.
[
https://issues.jboss.org/browse/AS7-3285?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-3285:
-----------------------------------
Not sure but one possible approach would be to use a web.xml for these web apps to map the
correct servlets and then mark it as metadata-complete=true so that the annotation
processing is skipped.
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
4:25 a.m.
[
https://issues.jboss.org/browse/AS7-3285?page=com.atlassian.jira.plugin.s...
]
jaikiran pai edited comment on AS7-3285 at 2/7/12 5:23 AM:
-----------------------------------------------------------
Not sure, but one possible approach would be to use a web.xml for these web apps to map
the correct servlets and then mark it as metadata-complete=true so that the annotation
processing is skipped.
was (Author: jaikiran):
Not sure but one possible approach would be to use a web.xml for these web apps to map
the correct servlets and then mark it as metadata-complete=true so that the annotation
processing is skipped.
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
12:24 a.m.
[
https://issues.jboss.org/browse/AS7-3285?page=com.atlassian.jira.plugin.s...
]
Jason Greene closed AS7-3285.
-----------------------------
Assignee: Jason Greene (was: Stuart Douglas)
Fix Version/s: No Release
(was: 7.1.1.Final)
Resolution: Won't Fix
I recommend one of three solutions:
1. Split out the web applications which use standard Java EE6 web fragments, which users
can embed in their deployment
2. Break this into 4 modules, one main one, and one for each web app module which has
it's own jandex index. They can share the same backing jar if needed via a re-exported
dep.
3. What jaikiran suggests
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: Jason Greene
Labels: eap6_prd_req
Fix For: No Release
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
5201
days inactive
5229
days old
9 comments
4 participants
participants (4)
-
jaikiran pai (JIRA) -
Jason Greene (JIRA)
-
Peter Skopek (JIRA)
-
Stuart Douglas (JIRA)