Hi Chuck, Neeraj, Please, do not mix manifest class-path with the ejb-client-jar tag. The ejb-client-jar does not imply the behavior of the class-path and this is reflected in the EJB spec - chapter 20.4 The Client View and the ejb-client JAR File. There is a parallel discussion in https://bugs.eclipse.org/bugs/show_bug.cgi?id=238830 where another IBM expert - Jason Sholl - is for keeping the current behavior. In any case, we will have an interest discussion in some minutes. Greetings, Kaloyan
________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chuck Bridgham Sent: Thursday, July 24, 2008 5:07 PM To: General discussion of project-wide or architectural issues. Cc: General discussion of project-wide or architectural issues.; [EMAIL PROTECTED] Subject: RE: [wtp-dev] EJb 3.0 and Ejb client project Hi Kaloyan, I encouraged Neeraj to post this question, because in EJB 3.0, the "ejb-client-jar" is only declaring a dependency on another jar in its MANIFEST classpath, and in reality, bean interfaces could be included in many dependent jar's. As long as its listed in the MANIFEST. We discussed locally with our IBM spec expert, and he agreed the dd xml isn't required in this case. Can we add this to the discussion in an hour? I'll call-in, and I encourage anyone else to join as well - Carl posted an agenda http://wiki.eclipse.org/JEE_Status_Meetings#Meeting_Minutes <http://wiki.eclipse.org/JEE_Status_Meetings#Meeting_Minutes> Thanks - Chuck Rational Java EE Tooling Team Lead IBM Software Lab - Research Triangle Park, NC [EMAIL PROTECTED] Ph: 919-254-1848 (T/L: 444) From: "Raev, Kaloyan" <[EMAIL PROTECTED]> To: "General discussion of project-wide or architectural issues." <[email protected]> Date: 07/24/2008 07:03 AM Subject: RE: [wtp-dev] EJb 3.0 and Ejb client project ________________________________ Hi Neeraj, Please see related bug https://bugs.eclipse.org/220156 <https://bugs.eclipse.org/220156> that explains why having a EJB client project requires having ejb-jar.xml descriptor. It is not a restriction. It is requirement by the EJB spec to declare the client jar in the ejb-jar.xml - hence we need to generate ejb-jar.xml. There are absolutely no restrictions to have an ejb.jar.xml and all your EJB bean metadata to be in annotations. In this case, the only metadata in the ejb-jar.xml will be the ejb-client-jar tag, which does not have a Java annotation alternative. I don't understand your worry here. Greetings, Kaloyan ________________________________ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] On Behalf Of Neeraj Agrawal Sent: Wednesday, July 23, 2008 9:30 PM To: [email protected] Subject: [wtp-dev] EJb 3.0 and Ejb client project In WTP, for EJB 3.0 projects you can't create EJB client project unless you have deployment descriptor, and https://bugs.eclipse.org/bugs/show_bug.cgi?id=238830 <https://bugs.eclipse.org/bugs/show_bug.cgi?id=238830> , we are requiring deployment descriptor to be generated when you create a client project. I think that is a restriction we are imposing, it means we cannot create an EJB client view. Think of the case where you have EJb project with no deployment descriptor and just have annotated beans, and the clients of the beans are remote. Since you cannot have client view project, you wont be able to distribute interfaces easily. Thanks -Neeraj Agrawal Java EE Tooling IBM Rational Software _______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev <https://dev.eclipse.org/mailman/listinfo/wtp-dev>
_______________________________________________ wtp-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/wtp-dev
