On Mar 12, 2009, at 12:45 PM, David Blevins wrote:
On Mar 12, 2009, at 5:25 AM, Karan Malhi wrote:
Regardless, that won't stop us from implementing it :) I suspect
if we do
it and other vendors follow suit, it'll pretty much have to make
it into the
spec next time around.
Nice! . Is this on the top of your priority list? I have an area
in struts2
integration which could use this funcionality.
Not the top, but very high. Top priority in my mind right now is
getting our JNDI awkwardness straightened out.
The easiest way to implement this would be to scan at deployment
like everything else perhaps by adding an
"@org.apache.openejb.annotations.Injectable" annotation or
something. Would be great if we didn't have to do even that, but
certainly would be the easiest first step. Could probably get that
in in a day or two and wouldn't at all limit our ability to do it
without the annotation later. With the annotation, the user would
get the same deploy time checks as other EE components and without
it'd be all runtime checks. So both seem like a pretty ideal
solution.
Going to see if I can't take a swing at this feature as described
here. Likely will involve adding a new container/openejb-annotation/
module to hold the annotation so people have a jar they can use free
of any other dependencies and just holds "API" things. If we end up
supporting more annotations, we'll have a place to put them.
-David
