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.
hai all, In RMI we call a Remote Method using our server programme and serve our client.why cannot the same be done in EJB. why do we need a Home interface to get an object for Remote interface. why can't it be done directly. thanks siva.
What I know abt Home object is that : Home Objects are introduced in EJB to have location transperency. Home Objetcs are the factories of Remote objects, so that you can initialise a the beans in a different ways.
The EJB Home objects are not for location transparency, but rather a Factory for EJB Remote and Local Interfaces. This factory is implemented by the EJB container when returns the interface. The real beauty of the Home object is that the EJB container now controls the interception of client requests to the EJB and offers the client implicit middleware functionality (instance pooling, security, clustering, transactions, etc.) So if choose not to use EJB's, you will need to provide all middleware services yourself. EJB's open standard and large vendor adoption makes it ideal for distributed systems.
-Ahmad<br />Sun Certified Java Developer (SCJD)<br />Sun Certified Java Programmer (SCJP)<p>"You got to be careful if you don't know where you're going, because you might not get there." -Yogi Berra
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