Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [aspectj-users] Websphere, outdated aspectjrt.jar

I think as Scott previously mentioned you should try "Parent-last" for
the classloader policies in websphere

In the past I have used the classloader policies to address similar
issues, although not specifically related to aspectj (mine was with
xerces, I believe,  but memory fails me)

http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzatz/51/program/clsadmcns.htm

Thanks
Bhaskar


On Wed, Mar 19, 2008 at 1:14 PM, Pavel <pagrus@xxxxxxxxx> wrote:
> Thanks for the tip Andy.
>
> Unfortunately with or without the X="ajruntimetarget:1.2" I end up with the
> same error,
>
> java.lang.NoSuchMethodError:
> org/aspectj/runtime/reflect/Factory.makeMethodSig(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)Lorg/aspectj/lang/reflect/MethodSignature;
>
> Pavel
>
> On Wed, Mar 19, 2008 at 2:24 AM, Andy Clement <andrew.clement@xxxxxxxxx>
> wrote:
> > Try this:
> >
> > ajc -Xajruntimetarget:1.2 Blah.java
> >
> > or
> >
> > <iajc ...... X="ajruntimetarget:1.2" .... >
> >
> >
> > Andy.
> >
> >
> >
> >
> > On 18/03/2008, Pavel <pagrus@xxxxxxxxx> wrote:
> > > Greetings,
> > >
> > > I noticed that woven classes do not deploy on WAS 6.1 due to old version
> of
> > > aspectjrt.jar in server lib folder. It all works fine on JBoss.
> > > Changing anything outside of my application EAR is not an option,
> especially
> > > when it comes to server libraries.
> > >
> > > Currently there is only one aspect for tracking domain object
> "dirtiness".
> > > The pointcut captures execution of set* methods, and around advice uses
> > > JoinPointStaticPart to invoke corresponding getter and compare result
> > > against value being set. The aspect is woven at build time with <iajc>.
> > >  As I understand, JoinPointStaticPart is what makes classes dependent on
> > > aspectjrt.jar, but I'm not sure if the aspect can be implemented without
> it.
> > >
> > > Can you please suggest a way out? To me this issue looks like a bold
> > > showstopper - you cannot build production-ready applications for WAS 6.x
> > > with AspectJ 1.5. I was hoping there is some sort of non-intrusive known
> > > solution/workaround.
> > >  My last resort is to drop AspectJ and try to get away with spring
> proxies,
> > > but this will make things harder, and possibly slower.
> > >
> > > Thanks,
> > > Pavel
> > > _______________________________________________
> > >  aspectj-users mailing list
> > >  aspectj-users@xxxxxxxxxxx
> > > https://dev.eclipse.org/mailman/listinfo/aspectj-users
> > >
> > >
> > _______________________________________________
> > aspectj-users mailing list
> > aspectj-users@xxxxxxxxxxx
> > https://dev.eclipse.org/mailman/listinfo/aspectj-users
> >
>
>
> _______________________________________________
>  aspectj-users mailing list
>  aspectj-users@xxxxxxxxxxx
>  https://dev.eclipse.org/mailman/listinfo/aspectj-users
>
>


Back to the top