Wrapping Session Beans with Web Services - A good approach?
Hi,
I always had this concern about accessing session beans located in a remote app server.
EJB uses rmi-iiop for networking and as such the end user cannot have precise control over the ports opened to communicate with the remote beans.
Yes, with patterns like business delegate and session facade, we can have effectively control remote communication over network.
But does wrapping the session beans with web services provide a tight control over port usage?
What are the advantages/disadvantages with this approach?
Can we write a highly performant application by employing this model?
Kindly provide your valuable suggestions.
# 1
> EJB uses rmi-iiop for networking and as such the end
> user cannot have precise control over the ports
> opened to communicate with the remote beans.
> But does wrapping the session beans with web services
> provide a tight control over port usage?
>
> Can we write a highly performant application by
> employing this model?
Using a Session EJB to implement a web service is a design decision. Exposing the business functionality of a Session EJB as a web service is good, depending upon the requirements.
It is unclear what you mean by "highly performant". If my application will only have two hundred users, and I have the application in a clustered environment with 10 nodes, my performance metrics should be easily met. It depends upon the application's specific performance metrics, to be able to accurately determine whether a design is "highly perfromant".
Why are you concerned about "tight control over port usage"? Client applications should be accessing the EJB via JNDI trees.
