Eugene Kuleshov wrote:
> For a moment I thought you've implemented generating pointcut
> expressions by dragging aspects into the target methods... Apparently I
> were wrong. :-(
Indeed. That does sound kinda interesting though - but I'm not sure how
it could work exactly...
>> For a moment I thought you've implemented generating pointcut
>> expressions by dragging aspects into the target methods... Apparently
>> I were wrong. :-(
>
> Indeed. That does sound kinda interesting though - but I'm not sure how
> it could work exactly...
On a second thought I wonder if you can drag target method (e.g. from
outline or package explorer into editor that has aspect code, so when
dropped it would add method expression for dragged method.
Other way around should be also possible, since there is generally
one-to-one mapping between advice and advised method.
Eugene Kuleshov wrote:
> For a moment I thought you've implemented generating pointcut
> expressions by dragging aspects into the target methods... Apparently I
> were wrong. :-(
Indeed. That does sound kinda interesting though - but I'm not sure how
it could work exactly...
>> For a moment I thought you've implemented generating pointcut
>> expressions by dragging aspects into the target methods... Apparently
>> I were wrong. :-(
>
> Indeed. That does sound kinda interesting though - but I'm not sure how
> it could work exactly...
On a second thought I wonder if you can drag target method (e.g. from
outline or package explorer into editor that has aspect code, so when
dropped it would add method expression for dragged method.
Other way around should be also possible, since there is generally
one-to-one mapping between advice and advised method.