Re: [Springframework-developer] Extending Spring AOP

[Eugene K. <eu...@md...>]

Folks,

   That is an interesting discussion...

   I've been looking to Janino for quite some time (actually it is used 
for some of the ASM's tests, especially to test for ASMifier tool).

   I can say that maintainer is quite busy and there still some bugs (at 
least one we hit from ASM test cases).

   However there is some activity going on about moving Janino to 
Codehaus and also it has been suggested to port Janino to use ASM as an 
internal bytecode toolkit underneath (right now it has its own 
proprietory bytecode manipulation framework). Also I know that Groovy 
and AW teams has been looking at Janino in order to use it for bytecode 
generation. The main reason is that Janino has extremly simplistic AST 
model, that allows to generate high level language constructs in memory 
without parsing strings (so, you can skip Velocity all together, which 
would be an important part in order to reduce dependencies for core AOP 
framework).

   regards,
   Eugene


> Good point. What is the license (and maturity) of Janino? AWProxy is 
> also very new.
> 
> Colin Sampaleanu wrote:
> 
>> One concern with AspectWerkz is the LGPL license. While Hibernate is 
>> also LGPL licensed, it is less a core part of Spring than the AOP 
>> stuff is. Now both Hibernate and AspectWerkz have a 'clarifying' 
>> statement about their interpretation of the LGPL:
>>  http://aspectwerkz.codehaus.org/license.html
>> such that there is less ambiguity (in theory) about linkage to it, but 
>> I would be a bit reticent to have the main (non-proxy) AOP 
>> implementation in Spring be based on AspectWerkz because of concerns 
>> that Spring using organizations would have about LGPL. Whatever it's 
>> intentions, the LGPL is so badly worded that a number of companies 
>> will simply not use any libraries which are LGPL licensed...
>>
>> Colin