This content has been marked as final.
Show 4 replies
-
1. Re: AOP WAR and EAR deployment - JBOSS 4.2.0GA
psourisseau Oct 2, 2007 2:40 PM (in response to psourisseau)Excuse-me complete definition is :
<interceptor-ref name="nf.linga.common.aop.interceptors.audit.TechnicalAuditInterceptor"/> -
2. Re: AOP WAR and EAR deployment - JBOSS 4.2.0GA
psourisseau Oct 2, 2007 2:43 PM (in response to psourisseau)Excuse-me the aop rule :
<interceptor class="nf.linga.common.aop.interceptors.audit.TechnicalAuditInterceptor" /> <bind pointcut="execution( * nf.linga.common.processor.impl.chained.ChainedProcessorImpl->doProcess(nf.linga.common.LingaMessage) )"> <interceptor-ref name="nf.linga.common.aop.interceptors.audit.TechnicalAuditInterceptor"/> </bind>
-
3. Re: AOP WAR and EAR deployment - JBOSS 4.2.0GA
afloom Oct 3, 2007 2:17 AM (in response to psourisseau)When you deploy your ear, do you have the aop jar file in the ear as well as in the included war (that is, twice)? That would then explain why the interceptor twice.
/Anders -
4. Re: AOP WAR and EAR deployment - JBOSS 4.2.0GA
flavia.rainone Oct 20, 2007 8:30 PM (in response to psourisseau)Anders is right. Once myaop.jar is referenced somewhere, it is deployed globally on your JBoss AS (so, its effect is not strict to the deployment unit that contains the manifest file). Hence, referencing it twice, even if you're doing this from inside different deployment units, is the same as deploying the same component twice.