[ https://jira.jboss.org/jira/browse/JBAS-6842?page=com.atlassian.jira.plug... ] Miroslav Havram updated JBAS-6842: ---------------------------------- Attachment: JBAS-6842.zip Attached is the test case already mentioned in discusion. Positive case is when there will be deployd only one bean. In negative case there are deployed two of them. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6842?page=com.atlassian.jira.plug... ] Ales Justin reassigned JBAS-6842: --------------------------------- Assignee: jaikiran pai (was: Ales Justin) Let's see if Jaikiran can duplicate this and drill down on the actual cause. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6842?page=com.atlassian.jira.plug... ] jaikiran pai commented on JBAS-6842: ------------------------------------ I could reproduce this even in 5.1.0 AS. I see what's happening in this case although i need to do some more analysis. I'll update this JIRA or open a thread in the forum for discussion. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6842?page=com.atlassian.jira.plug... ] jaikiran pai commented on JBAS-6842: ------------------------------------ Its the org.jboss.deployment.OptAnnotationMetaDataDeployer which is the culprit. It's implementation of deploy (through it's superclass AnnotationMetaDataDeployer) does this : protected void deploy(VFSDeploymentUnit unit) throws DeploymentException { ... List<VirtualFile> classpath = unit.getClassPath(); if(classpath == null || classpath.isEmpty()) return; boolean trace = log.isTraceEnabled(); if (trace) log.trace("Deploying annotations for unit: " + unit + ", classpath: " + classpath); try { processMetaData(unit, webMetaData, clientMetaData, classpath); ... So for the unit corresponding to the ear file (test-ear.ear), it picks up the .ear/lib/shared-ejb.jar from the unit.getClasspath() and starts creating metadata out of the annotaitons in the shared-ejb.jar since lib/shared-ejb.jar forms the classpath of the ear: 2009-10-03 02:02:19,581 TRACE [org.jboss.deployment.OptAnnotationMetaDataDeployer] (main) Deploying annotations for unit: AbstractVFSDeploymentContext@9405908{vfszip:/home/jpai/jboss-5.1.0.GA/server/default/deploy/test-ear.ear/}, classpath: [MemoryContextHandler@25410398[path= context=vfsmemory://3j001-dizj50-g0be59bs-1-g0be5nsz-2d real=vfsmemory://3j001-dizj50-g0be59bs-1-g0be5nsz-2d], DelegatingHandler(a)25319602[path=test-ear.ear/lib/shared-ejbs.jar context=file:/home/jpai/jboss-5.1.0.GA/server/default/deploy/ real=file:/home/jpai/jboss-5.1.0.GA/server/default/deploy/test-ear.ear/lib/shared-ejbs.jar], DelegatingHandler(a)6213371[path=test-ear.ear context=file:/home/jpai/jboss-5.1.0.GA/server/default/deploy/ real=file:/home/jpai/jboss-5.1.0.GA/server/default/deploy/test-ear.ear]] So effectively, the ear unit now has a JBossMetaData created and attached to it from the annotation processing on lib/shared-ejb.jar file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6842?page=com.atlassian.jira.plug... ] Ales Justin reassigned JBAS-6842: --------------------------------- Assignee: Ales Justin (was: jaikiran pai) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBAS-6842?page=com.atlassian.jira.plug... ] Ales Justin resolved JBAS-6842. ------------------------------- Fix Version/s: JBossAS-5.2.0.Beta1 Resolution: Done Fixed EarLibExcludeDeployer$UrlExcludeResourceFilter in 5_x branch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira