Robert,
I saw that the error originates from commons-logging. I remember vaguely
that Websphere has a bundled version of commons-logging - is that true? It
might be the case that the container's class loading of clogging conflicts
with LTW's idea of a class hierarchy. Try to switch to parent-last
classloading or alternatively replace the container's commons-logging with
slf4j (you'll need jcl-over-slf for the clogging interfaces, slf4j-api for
the slf4j interfaces and slf4j-log4j for the backend). The jcl-over-slf
intrefaces are binary-compatible with clogging but the implementation
exhibts less "dynamic" (read: often failing) behaviour at runtime.
Holger
_______________________________________________
aspectj-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/aspectj-users
