On 1/22/07, Jarek Gawor <[EMAIL PROTECTED]> wrote:
Tim,
A couple of questions on the design/implementation:
1) Since the module builders will get an updated deployment
descriptors, in general, the annotation processors in Tomcat, Jetty,
Web services, EJB, etc. will just need to lookup the resources in
JNDI, right?
IIUC the changes made last night in rev 499336 allows EjbRefBuilder to
scan for and process @EJB annotations in webapps, making them
available via JNDI to tomcat's annotation processor. This approach
is similar to what Tim proposed but a little different because it
places the responsibility of scanning for annotations into the
builder's hands, and doesn't merge them into the DD. That leaves it
up to Geronimo's implementation of JSR-77 to handle the merging, but
has the advantage that error messages caused by incorrect DDs won't be
misleading.
Would it make sense to implement annotation support in the webservices
builder in the same way? If so then tomcat's annotation processor
should already be able to resolve and inject @WebServiceRefs via JNDI.
Best wishes,
Paul
