[aspectwerkz-dev] [jira] Deleted: (AW-233) WLS ejb deployment and AOPC duplicate system id
"
[email protected] (JIRA)" <jira-yCVjj/
[email protected]>
Fri, 3 Aug 2007 07:11:46 +1000 (EST)
| Newsgroups |
gmane.comp.java.aspectwerkz.devel |
| Message-ID |
<[email protected]> |
[ http://jira.codehaus.org/browse/AW-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
[email protected] deleted AW-233:
---------------------------------
> WLS ejb deployment and AOPC duplicate system id
> -----------------------------------------------
>
> Key: AW-233
> URL: http://jira.codehaus.org/browse/AW-233
> Project: AspectWerkz
> Issue Type: Bug
> Reporter: Alexandre Vasseur
>
> Alex:
> You can safely ignore the "duplicate code". It happens once and a while, but is not an issue.
> As regards WLS 8.1 integration, there has been an issue reported when referencing twice an EAR/my.jar from an EAR/ejb.jar ' Manifest Classpath. I have no good solution right now.
> As a temp fix, I suggest if possible to
> - avoid having too many system where possible
> - use APP-INF/lib/some.jar/META-INF/aop.xml to host the system that should be shared among the whole ear file
> It is on my top list to implement a specific WLS deployer to make use of WLS "GenericClassLoader" and alike. I will let you know when I am done - target is end of august.
> The message that appears here is very valuable, since there are duplicates reported *within* a single classloader.
> If someone is fine to hack the source (SystemDefinitionContainer class if I am right), catch the definition exception there without rethrowing it, and writing a message properly and going on should be a temp fix to allow app deployment with ignoring the duplicates, until a better fix.
> Alex
> ----- Original Message -----
> From: <freds AT alphacsp DOT com>
> To: <[email protected]>
> Sent: Wednesday, August 04, 2004 2:51 PM
> Subject: [aspectwerkz-user] Using AspectWerkz with WLS8.1 in Exploded EAR
> > I started to use AspectWerkz on our application and after solving
> > multiple newbie issues we stambled on this one:
> >
> > ******************************************************************
> > * ClassLoader = sun.misc.Launcher$ExtClassLoader@b169f8
> > * Aspect total count = 0
> > ******************************************************************
> > ******************************************************************
> > * ClassLoader = sun.misc.Launcher$AppClassLoader@4b222f
> > * Aspect total count = 0
> > * no -Daspectwerkz.definition.file
> > ******************************************************************
> > ******************************************************************
> > * ClassLoader = weblogic.utils.classloaders.GenericClassLoader@25980092
> > * Aspect total count = 0
> > ******************************************************************
> > ******************************************************************
> > * ClassLoader = weblogic.utils.classloaders.GenericClassLoader@29486315
> > * Aspect total count = 0
> > ******************************************************************
> > ******************************************************************
> > * ClassLoader = weblogic.utils.classloaders.GenericClassLoader@11829808
> > * SystemID = idit
> > * SystemID = idit-reference
> > * SystemID = idit-sce
> > * SystemID = idit-security
> > * SystemID = idit-sce
> > * SystemID = idit-reference
> > * SystemID = idit-security
> > * Aspect total count = 7
> > * zip:U:/Software/wls81/noc/idit/myserver/.wlnotdelete/extract/myserver_noc-
> > International-ear/APP-INF/lib/idit-backend58088.j
> > ar!/META-INF/aop.xml
> > * file:U:/Software/wls81/noc/idit/applications/noc-International-ear/idit-
> > reference-ejb/META-INF/aop.xml
> > * file:U:/Software/wls81/noc/idit/applications/noc-International-ear/idit-sce-
> > ejb/META-INF/aop.xml
> > * file:U:/Software/wls81/noc/idit/applications/noc-International-ear/idit-
> > security-ejb/META-INF/aop.xml
> > * file:U:/Software/wls81/noc/idit/applications/noc-International-ear/idit-sce-
> > ejb/META-INF/aop.xml
> > * file:U:/Software/wls81/noc/idit/applications/noc-International-ear/idit-
> > reference-ejb/META-INF/aop.xml
> > * file:U:/Software/wls81/noc/idit/applications/noc-International-ear/idit-
> > security-ejb/META-INF/aop.xml
> > ******************************************************************
> > <Aug 4, 2004 4:21:46 PM IDT> <Error> <Deployer> <BEA-149231> <Unable to set the
> > activation state to true for the application
> > noc-International-ear.
> > org.codehaus.aspectwerkz.exception.DefinitionException: UUID is not unique
> > within hierarchy: idit-reference
> > at org.codehaus.aspectwerkz.AspectSystem.assertUuidUniqueWithinHierarchy
> > (AspectSystem.java:334)
> > at org.codehaus.aspectwerkz.AspectSystem.<init>(AspectSystem.java:100)
> > at org.codehaus.aspectwerkz.SystemLoader.getSystem(SystemLoader.java:48)
> > at org.codehaus.aspectwerkz.joinpoint.management.JoinPointManager.<init>
> > (JoinPointManager.java:101)
> > at
> > org.codehaus.aspectwerkz.joinpoint.management.JoinPointManager.getJoinPointManag
> > er(JoinPointManager.java:134)
> > at
> > com.idit.printing_manager.server.session.bean.PrintingSessionSLBean.<clinit>
> > (PrintingSessionSLBean.java)
> > at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
> > at sun.reflect.NativeConstructorAccessorImpl.newInstance
> > (NativeConstructorAccessorImpl.java:39)
> > at sun.reflect.DelegatingConstructorAccessorImpl.newInstance
> > (DelegatingConstructorAccessorImpl.java:27)
> > at java.lang.reflect.Constructor.newInstance(Constructor.java:274)
> >
> >
> > Our environment is:
> > WLS 8.1 sp2 with a big exploded EAR and today only 4 aspect systems:
> > - One in a global backend jar deployed in the EAR as a java jar tool, and the
> > aop.xml is in its .jar#META-INF dir.
> > - Three aop.xml in different META-INF dir of some of our EJB declared in our
> > exploded EAR.
> >
> > Until now the exception and messages from AspectWerkz were quite clear and we
> > manage to solve the problem, but now the fact that its trying to load 2 times
> > every aop.xml in our EJBs is strange and I don't know what to do. I checked and
> > there is only 3 aop.xml file in my system plus the one inside the backend.jar.
> >
> >
> >
> >
> >
> >
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email