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.
I have to call EJB from standalone java application. EJB is developed in Websphere 5.1 J2EE 1.3 and is deployed on the server. (AIX Websphere, on remote machine) When I call it from 'Client Application project' developed in WASAD, it works fine (with unacceptable response time). But when I try to run the same project from command prompt it dosent work, and gives lot of issues. (like IBM java vs Sun java etc)
So finally I decided to write servlet to serve the same purpose and call it from standalone application, instead of calling EJB.
My question is: Is this a correct design? What are pros and cons? Is there discussion on the comparision of these 2 approaches?
(I just dont want to do it cause I am not able to call EJB from standalone, but also want to know which way is better to do. )
Instead of writing servlet, u can use "launchClient" executable of WebSphere to invoke your application which calls EJB. This will work without the need for writing separate servlet.
Joined: Nov 17, 2002
Thanks Sweet, I know little about launchclient. I will read more about it and get back if have any queries. I have another question: Is there any portability issue with this kind of EJB client? We are planning to use this as local client on number of user's machines and we can not control their configuration (if they have IBM java or SUN java) Thanks, Manoj
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com