On Aug 23, 2007, at 3:29 PM, Marshall Schor wrote:
I like this idea. I think there are some details to work out.
Most of these are maybe just things I need to learn :-) Here's a few:
1) Whatever approach we take for this - it would be nice to align with
existing Eclipse support for this kind of thing (I assume there is
some,
but I
haven't explored what it is).
Eclipse supports java 1.5 language features.
2) We have to think about having now 2 places where the same thing is
specified.
If both places are used, do we need to check for "consistency" at run
startup time?
The new one should fail to run if the parameters are specified in the
descriptor.
The AE factory code reads the config values from the descriptor and
sets the
corresponding values to the member variables of the AE which have
the parameter annotation. This can be done with the java reflection api.
3) Can we have some kind of backwards-compatible approach that
achieves
more of
the goals of writing information about configuration parameters in
just
one place? Should
we take some inspiration from how EMF does things, or how Spring
support
is done in
Eclipse (Spring uses injection, and has some Eclipse plugins - see for
instance
http://springide.org)
Do you mean that the new annotators run with an older release of uime ?
This is possible as fair as I know it not a problem if an annotation
can be found
on the classpath.
Jörn
