[aspectwerkz-user] aop.xml is not recognised in Tomcat 4.6 with JDK 1.3.1 - compile time weaving

[l***@wipro.com]

Hi,

The aop.xml is not getting loaded in tomcat 4.6 with jdk 1.3.1.

I compiled the application classes with aop.xml using awc utility.

My application war has aop.xml both in META-INF and WEB-INF, then aop.xml is recognised successfully.

But if I removed aop.xml from the war file and add path to aop.xml in the startup file (as jar or xml file in -cp option or in the -Xbootclasspath) as below

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
set %JAVA_OPTS% = %JAVA_OPTS% %JAVA_HOME%\bin\java -Xbootclasspath/p:E:\temp-eprofiler\enhanced.jar; -Daspectwerkz.transform.verbose=false -Daspectwerkz.definition.file=E:\cvs-eprofiler\eProfiler_CVS\eProfiler-BV\compiletime\aopxml.jar -Xbootclasspath/a:%ASPECTWERKZ_HOME%\lib\aspectwerkz-core-2.0.jar;%BOOT_PATH% -cp "JAVA_HOME/lib/tools.jar;%ASPECTWERKZ_HOME%\lib\aspectwerkz-core-2.0.jar;%ASPECTWERKZ_HOME%\lib\aspectwerkz-%ASPECTWERKZ_VERSION%.jar;%ASPECTWERKZ_HOME%\lib\aspectwerkz-extensions-%ASPECTWERKZ_VERSION%.jar;E:\cvs-eprofiler\eProfiler_CVS\eProfiler-BV\compiletime\aopxml.jar;%DEPS%" -Daspectwerkz.home="%ASPECTWERKZ_HOME%" %*

OR


set %JAVA_OPTS% = %JAVA_OPTS% %JAVA_HOME%\bin\java -Xbootclasspath/p:E:\temp-eprofiler\enhanced.jar; -Daspectwerkz.transform.verbose=false -Daspectwerkz.definition.file=E:\cvs-eprofiler\eProfiler_CVS\eProfiler-BV\compiletime\aop.xml -Xbootclasspath/a:%ASPECTWERKZ_HOME%\lib\aspectwerkz-core-2.0.jar;%BOOT_PATH% -cp "JAVA_HOME/lib/tools.jar;%ASPECTWERKZ_HOME%\lib\aspectwerkz-core-2.0.jar;%ASPECTWERKZ_HOME%\lib\aspectwerkz-%ASPECTWERKZ_VERSION%.jar;%ASPECTWERKZ_HOME%\lib\aspectwerkz-extensions-%ASPECTWERKZ_VERSION%.jar;E:\cvs-eprofiler\eProfiler_CVS\eProfiler-BV\compiletime\aop.xml;%DEPS%" -Daspectwerkz.home="%ASPECTWERKZ_HOME%" %*

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------


I am getting java.lang.ExceptionInInitializerError: org.codehaus.aspectwerkz.aspect.management.NoAspectBoundException: NoAspectBound: Could not find AspectDefinition.

Why is the aop.xml not recognised ?

Any help is highly appreciated.

Thanks and Regards,
Lalithamba.




The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.

WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.

www.wipro.com

[l***@wipro.com]

Hi,

I would like to know the starting point in aspectwerkz sourcecode where aop.xml is picked up if its present in the application's META-INF and WEB-INF directory.
I am trying to debug the same in ecclipse, but I am not successful yet.

Thanks and Regards,
Lalithamba.

[akhilesh laddha]

Hi,
According to AspectwerkZ document, to work with JDK 1.3, piccolo-1.03.jar and xerces.jar files should be in JAVA_HOME/jre/lib/ext directory . There is a scenario, where, do not have access to the ext directory. Is this right to place these Jar’s in bootclass path.

What are implications if these jars are not placed due to conflicts with the application?

Thanks
Akhilesh


---------------------------------
Luggage? GPS? Comic books?
Check out fitting gifts for grads at Yahoo! Search.

[Jonas Bonér]

I think that should work just fine.
--
Jonas Bonér

http://jonasboner.com

Post by akhilesh laddha
Hi,
According to AspectwerkZ document, to work with JDK 1.3, piccolo-1.03.jar
and xerces.jar files should be in JAVA_HOME/jre/lib/ext directory . There is
a scenario, where, do not have access to the ext directory. Is this right
to place these Jar's in bootclass path.
What are implications if these jars are not placed due to conflicts with the application?
Thanks
Akhilesh
________________________________
Luggage? GPS? Comic books?
Check out fittin

[Jonas Bonér]

I think that should work just fine.

--
Jonas Bonér

http://jonasboner.com

Post by akhilesh laddha
Hi,
According to AspectwerkZ document, to work with JDK 1.3, piccolo-1.03.jar
and xerces.jar files should be in JAVA_HOME/jre/lib/ext directory . There is
a scenario, where, do not have access to the ext directory. Is this right
to place these Jar's in bootclass path.
What are implications if these jars are not placed due to conflicts with the
application?
Thanks
Akhilesh
________________________________
Luggage? GPS? Comic books?
Check out fitting gifts for grads71 at Yah