Re: [aspectj-users] Weaving aspects into libraries

["Mohan Radhakrishnan" <radhakrishnan.mohan@xxxxxxxxx>]

Hi,
        Good question.

        Actually I think some type of AspectJ weaving is already going
on in many popular servers like Portal servers. This weaving can also
affect the code that you write and deploy without you knowing anything
about it. It is tricky. In our case we want to weave into proprietary
code to figure out certain extensibility points because the vendor
does not reveal anything and that is affecting a huge production
deployment of call-center software.

Thanks,
Mohan

On 4/11/08, Matthias.Gaiser@xxxxxxxxxxxxx <Matthias.Gaiser@xxxxxxxxxxxxx> wrote:
> Thank you, Andy!
>
>  Does anybody know if it is legally ok if I am using a commercial third party library and I am modifying it by weaving code into it? Usually, I am not allowed to decompile classes, change them and make a modified jar from them. How is it with the aspect orientation since I am not decompiling the code... ?
>
>  Matthias.
>
>  > -----Ursprüngliche Nachricht-----
>  > Von: aspectj-users-bounces@xxxxxxxxxxx [mailto:aspectj-users-
>  > bounces@xxxxxxxxxxx] Im Auftrag von Andy Clement
>  > Gesendet: Donnerstag, 10. April 2008 17:46
>  > An: aspectj-users@xxxxxxxxxxx
>  > Betreff: Re: [aspectj-users] Weaving aspects into libraries
>
> >
>  > With the command line compiler it can be as simple as
>  >
>  > ajc -inpath frameworkCode.jar  MyAspect.java -outjar
>  > modifiedFrameWorkCode.jar
>  >
>  > aspect could be something vaguely like:
>  >
>  > aspect Demo {
>  >   pointcut setVisibleCall(): call(* setVisible(..)) &&
>  > within(com.someframework..*);
>  >
>  >   void around(): setVisibleCall() {
>  >     // proceed();  uncomment this line to invoke setVisible(), leave
>  > it commented out to
>  >     //                 not make the call
>  >   }
>  > }
>  >
>  > Andy
>  >
>  > On 10/04/2008, Matthias.Gaiser@xxxxxxxxxxxxx
>  > <Matthias.Gaiser@xxxxxxxxxxxxx> wrote:
>  > >
>  > >
>  > >
>  > >
>  > > Hi.
>  > >
>  > >
>  > >
>  > > I am bloody beginner in aspect-oriented programming and started to
>  > use it
>  > > today.
>  > >
>  > >
>  > >
>  > > Now I have a concern, wondering if this is possible and if it is
>  > worth to
>  > > spend more time in AspectJ.
>  > >
>  > > I am using a third party library which is creating dialogs based on a
>  > Frame
>  > > I initialize this library with, so my Frame is the parent of all
>  > dialogs
>  > > which are popping up. Via the Frame I can then access the dialogs and
>  > handle
>  > > them like I want to. Now I do not want to have the dialogs displayed
>  > and was
>  > > thinking about implementing an aspect which prevents my third party
>  > library
>  > > from calling setVisible() on the dialogs.
>  > >
>  > >
>  > >
>  > > Is it possible to weave aspects into code of other libraries? How is
>  > it
>  > > possible?
>  > >
>  > >
>  > >
>  > > Thanks for anyone reading and thinking about it.
>  > >
>  > > Matthias.
>  > > _______________________________________________
>  > >  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
>