psseshwari, you don't give much in the way of details as to what's happening or why your app should be instrumented.
have you tried the examples for load time aop?
I tried the injboss aop example. I ran the build.xml using ant as deploy-basic-lt-war and the output i get is
15:11:18,052 INFO [STDOUT] **** ExampleValue empty Constructor
15:11:18,052 INFO [STDOUT] **** ExampleValue.getMessage()
15:11:25,673 INFO [STDOUT] **** BasicExampleServlet.service()
15:11:25,673 INFO [STDOUT] **** ExampleValue String Constructor
15:11:25,703 INFO [STDOUT] **** ExampleValue.getMessage()
On the other hand, when I ran the ant as deoloy-basic-ct-war the output is
15:20:09,036 INFO [STDOUT] <<< Entering SimpleInterceptor:
invocation class: org.jboss.injbossaop.lib.ExampleValue$getMessage_53534
type: Method Invocation
Class containing method: org.jboss.injbossaop.lib.ExampleValue
15:20:09,036 INFO [STDOUT] **** ExampleValue.getMessage()
15:20:09,036 INFO [STDOUT] >>> Leaving SimpleInterceptor
I copied the jboss-classloader-transformer.jar, jdk14-pluggable-instrumentor.jar to the bin directory of JBoss server, modified the jboss-service.xml to set the EnableLoadTimeWeaving attribute to true. Please let me know if i'm missing anything.
It works for me using Windows. I will try it out on cygwin to see if there is a problem there (I don't have linux installed)