On Sep 14, 2007, at 10:44 AM, Dario Laverde wrote:
Thanks for clarifying David, so with the agent and annotation
issues aside, I still
don't understand what's tricky in supporting @EJB, @Resource, etc.
compared to
standalone OpenEJB. I'd for one would like to see this working out
of the box and
would like to help Dain out here if feasible.
Great! All the help we can get here is really fantastic.
The @EJB, @Resource, etc. work out of the box for ejb modules and
client modules, but not for anything in the web module (servlet,
filter, listener) as Tomcat is the one who creates and injects on
those objects and it ignores those things for the most part.
It does have a thing called AnnotationProcessor which will inject
@EJB, @Resource and the like by looking them up from the web module's
jndi tree, but it never puts them in there in the first place. So
effectively nothing is injected. So what we need to do is grab the
web.xml, find all the servlets, filters, and listeners scrape them
for annotations and create and bind the required objects into the web
module's jndi tree. Then when Tomcat creates a servlet, filter, or
listener the Tomcat AnnotationProcessor will again scrape the object
for annotations, look for the objects in jndi, *find* them (we put
them there) and finally inject them.
Other things that need to be done are to restore the jsps that did
this: http://people.apache.org/~dblevins/screenshots
Skin the installer to look like the above
Security integration
Take your pick!
-David
