About my packaging structure, I referred to JBossAOP tutorial: Running and
packaging in JBoss available at
http://docs.jboss.com/aop/1.3/aspect-framework/examples/injboss/aopInJbossPackaging.html.
There is a section named "WAR and .aop lib file contained in a JAR" in there.
Got it to function c
fix: p/s: Wondering why I can't get Luntain's suggestion to work...
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939716#3939716
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939716
-
OK, just got AOP to function correctly in JBoss-4.0.4.CR2. It seems that when I
executed run.bat from inside Windows, it didn't make the current directory as
its working directory, so it couldn't find pluggable-instrumentor.jar.. So I
just had to make the current directory as the working directo
Following Kabir's advice by reading section 10.3.3 (JBoss 4.x and JDK 5) of the
reference manual, the JBossAS would not even boot.
The steps I taken:
1. Changed jboss-service.xml in jboss-aop-jdk50.deployer:
org.jboss.aop.deployment.AspectManagerService to
org.jboss.aop.deployment.AspectManage
Just tried using Luntain's suggestion, still no success. I'll be trying Kabir's
suggestion next.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3939703#3939703
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3939703
---
|+-- LearningWeb.war
||+-- WEB-INF [dir]
|| +-- web.xml
|| +-- classes [dir]
| | +-- amry [dir]
|| +-- learning [dir]
||+-- CatchAll.class
|+-- myinterceptor.aop
A quick solution to this is to modify the current log4j.xml in the server conf
directory. Just add the following entry into it and all should be fine:
|
|
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3937629#3937629
Reply to the post :
h
