This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Hello, everyone I am not sure if this is the right place for this topic but here it goes... Is there a specification (maybe it is not even a Servlet specification) that rules about how Servlets (client-side classes in general) are supposed to deal with EJB 3.0 annotations -- such as @EJB? I looked for something like that in the JCP and found nothing.
Henrique Sousa<br />SCJP 1.4<br /> <br />All men die, not all men really live - Braveheart, 1995
In that sense, yes. The servlet app is the user interface to the EJBs.
I'm guessing that you're going to have issues unless you're running a servlet container under JDK1.5x. Not sure if the servlet classes themselves would need to be compiled under 1.5.
There are some similar issues going on with Tomcat right now. Version 5.5 requires JDK1.5x and servlets compiled under 1.5 can use the new 1.5 features such as the new for loops but these things will not work in JSP scriptlets because the compiler that ships with Tomcat (Eclipse's JDT) isn't fully 1.5 compliant yet and doesn't understand them.
Originally posted by Henrique Sousa: Well, they are client from the EJB point of view... or not?
That confusion leads me to believe that this thread would do better in the EJB forum. A lot of people here (and in the JSP forum) are having a hard enough time understanding what happens on the webserver and what happens in the user's browser without mixing the 'EJB/Servlet Container' relationship into the mix.