Fabien,

I confess that I have never used webstart but understand what it does. It 
would seem that the monitor (com.sun.javaws.Main?) is running your 
application (deploy.jar?) in a new JVM but _not_ using the same options, 
including -javaagent. Does the webstart documentation mention how to 
specify options for the application VM? Have you tried weaving the 
application ahead-of-time instead?

Matthew Webster
AOSD Project
Java Technology Centre, MP146
IBM Hursley Park, Winchester,  SO21 2JN, England
Telephone: +44 196 2816139 (external) 246139 (internal) 
Email: Matthew Webster/UK/IBM @ IBMGB, [EMAIL PROTECTED]
http://w3.hursley.ibm.com/~websterm/



"Fabien Bergeret" <[EMAIL PROTECTED]> 
Sent by: [EMAIL PROTECTED]
03/01/2007 17:01
Please respond to
[email protected]


To
"aspectj-users" <[email protected]>
cc

Subject
[aspectj-users] webstart integration






Hi,

I'm trying to integrate aspectj in a webstart application. The
idea is to log some interesting behavior of the application
for security purposes.
Here is the relevant lines I use in a ant script file: 
<target name="dynamicWS" if="doWs">
                                 <java classname="com.sun.javaws.Main" 
fork="true">
                                                 <classpath>
 <pathelement
location="${aspectj.home}/lib/aspectjweaver.jar" />
 <pathelement location="${log4j.home}/log4j-1.2.14.jar" />
 <pathelement location="aspect.jar" />
 <pathelement location="${java.home}/lib/deploy.jar"/>
 <pathelement path="${java.class.path}" />
                                                 </classpath>
                                                 <jvmarg
value="-javaagent:${aspectj.home}\lib\aspectjweaver.jar" />
                                                 <jvmarg
value="-Xbootclasspath/a:${java.home}\lib\javaws.jar;${java.home}\lib\deploy.jar"/>
                                                 <arg 
value="${runtimeParameter}" />
                                 </java>
                 </target>
What it does: run the application
What it doesn't do: starting aspectj

If I remove the -Xbootclasspath line, it starts java WebStart
monitor, with aspectj, but the web start monitor seems to make
a Runtime.exec() call, and the application itself runs in
another jvm ... and the application itself runs without aspectj.
Any idea ?


Envoyez vos cartes de voeux depuis www.laposte.net 
Elles seront ensuite distribuées par le facteur : pratique et malin !

_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users

_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users

Reply via email to