[nat101]

Please be aware, that since XDoclet supplies tags for ejb clients, half the work for ME folks are already done.
Please post your opinion.
Thank you;
-nat

[Scott Anderson]

Nat,

You might also list what specific features you’d specifically want in such support as each developer can now imagine whatever they want. 🙂

[nat101]

Well, actually that is the point. How many developers use -or would use- j2se clients, or rich clients, to talk to the ejb, regardless of specific functionality, if the choir would be lickety split.
Specifically we need a transparent way to talk to the ejb, without a jndi song and a dance, customized for each server platform.
-nat

[carniz]

I think it would be nice if ME could provide automated adding of the JAR:s required for a client to call an EJB. For example, the user could right-click on a project and choose My Eclipse->”Add EJB client libraries to project”. This would bring up a dialog where you could choose the target app server, as different app servers require different JAR:s. The only step required in order to use an EJB in a client project after that is to add a project reference in the client project to the EJB project containing the desired EJB(s) – this task could possibly be included as a second step when choosing “Add EJB client libraries to project”, eg;

“Do you want to add EJB project references to this project now?” [ ] yes [ ] no

where choosing “yes” brings up a list of known EJB projects to choose from.

If you have a Util class generated by xdoclet, you should only have to use the static getHome() or getLocalHome() method in the client after these steps to use the EJB – but I see little use in automating that (should be a right-click on class/in editor and choosing “add EJB lookup call” in that case, but that almost seems *too* picky…or what do others think?)

[nat101]

Regarding the util class already genned, yes, that is great, and the ME folks either aren’t aware of it, or just forgot to document it. (In the TraderX sample, they do NOT use the util class in the servlet that calls the ejb.)

The main thing we need is to automatically jar the client with appropiate jars for the servers, AND to package the server with special client jars. eg The Sun RI requires special client jars to be in the same ear as the ejb’s, and then its a simple jndi call from the client. Oh, along with the application.xml.

Please vote for the feature, if you want it. It should be real simple to implement.
Thanks;
-nat

[Author]

Posts