| Re: [aspectj-users] Using the AspectJ load time weaver with Jetty |
Cool that your handler is written in Scala :)In that case it suggests to me something related to the classloaders involved and the delegation strategy. If the agent is specified via -javaagent but the environment is not using a parent first loading strategy it may locate a different IMessageHandler if it can find another aspectjweaver/aspectjtools somewhere. Are there any other copies of aspectjtools/aspectjweaver around? (IMessageHandler isn't in aspectjrt so we don't need to worry about that)cheers,AndyOn 5 August 2014 11:58, Ivan Topolnjak <ivantopo@xxxxxxxxx> wrote:
Andy,
setting the custom message handler is something that we are doing on purpose and the KamonWeaverMessageHandler class [1] in fact is a IMessageHandler, which works nicely in other non-servlet environments. Removing the -XmessageHandlerClass option makes it work fine again, but I guess that there should be a way to make it work the same way as with a regular application, do you think it is possible to achieve that?
[1] https://github.com/kamon-io/Kamon/blob/master/kamon-core/src/main/scala/kamon/weaver/logging/KamonWeaverMessageHandler.scala
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users
_______________________________________________
aspectj-users mailing list
aspectj-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/aspectj-users