On 20 avr, 08:43, nicolas de loof <[email protected]> wrote:
> > > I wonder if there is any way to also "pre-process" Java sources, for
> > example
> > > this would enable support for Aspect Oriented Programming or maybe some
> > > DataBinding framework.
>
> > Depends what you mean by "pre-process"... Generally, generators
> > analyze the class they're called for (for example, looking for
> > specific annotations on methods or on the class itself) and according
> > to this generate a Java class extending the one they've been called
> > for.
> > (is this understandable? is this at least no-so-bad english?)
>
> In many case the generator will create from MyClassX some MyClassXImpl or
> equivalent that extends the original one, bu not REPLACE it as Java source.
> This is what I mean by "pre-process".
>
> For example, to implement a AOP framework I'd like to instrument all calls
> to some method. For this reason I'd like a generator / pre-processor to
> check the source files and detect the matching pointcuts to add some adived
> code. Many other example can apply, including annotation processing for
> declarative coding (ex : @Property annotation to automagically introduce the
> required PropertyChangeListeners)
You would generate a subclass that delegates to super.method() after/
before the aspect(s) code.
> I never tried it myself, but I'n not sure a generator can REPLACE the
> original Java Source.
AFAICT, it can't, but there's probably no need for this.
> I may be wrong but I also thing the generated code is
> only available when using GWT.create(),
The generator is only called at the point where GWT.create() is called
(I may be wrong but you could generate a different output for each
GWT.create() call-point for the same class literal), so yes, you're
right.
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
