[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Fw: [wtp-dev] EJb 3.0 and Ejb client project


Also as you pointed out

"The ejb-client JAR file is specified in the deployment descriptor of the
ejb-jar file using the optional ejb-client-jar element. The value of the
ejb-client-jar element is the path name specifying the location of the
ejb-client JAR file in the containing Java EE Enterprise Application Archive
(.ear) file. The path name is relative to the location of the referencing
ejb-jar file.
"


If a client can resolve a client view by just having a manifest entry, I think so can EJb jar too ?

-Neeraj Agrawal


----- Forwarded by Neeraj Agrawal/New Haven/IBM on 07/24/2008 10:07 AM -----
From: Neeraj Agrawal/New Haven/IBM
To: "General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
Cc: "General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>, wtp-dev-bounces@xxxxxxxxxxx
Date: 07/24/2008 10:05 AM
Subject: RE: [wtp-dev] EJb 3.0  and Ejb client project




Hi Kaloyan,

The spec says
"In EJB 3.0, a remote client accesses a session bean through the beanâs remote business interface. For a
session bean client and component written to the EJB 2.1 and earlier APIs, the remote client accesses
the session bean through the session beanâs remote home and remote component interfaces. "

So in the case where you are 3.0 bean developer without EJb client view, you  will package your bean and its interfaces in a jar corresponding to the project.. Now a different user wants to access the beans by just using your bean interfaces, would you like to provide him bean interface or the  bean  interfaces along with the implementation too?.  (The client adds a manifest entry for this jar) Separating the client provides you flexibility of just exporting the client view project as jar and distributing to the clients.


-Neeraj Agarwal






From: "Raev, Kaloyan" <kaloyan.raev@xxxxxxx>
To: "General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
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 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: wtp-dev-bounces@xxxxxxxxxxx [mailto:wtp-dev-bounces@xxxxxxxxxxx] On Behalf Of Neeraj Agrawal
Sent:
Wednesday, July 23, 2008 9:30 PM
To:
wtp-dev@xxxxxxxxxxx
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,  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
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev