rmvprasad
asked on
What does this mean(EJB VS Webservices)
Component architecture enhances reusability at a finer grain level.
SOA(Service oriented architecture) can enhance reusability at a Coarser grained level.
SOA(Service oriented architecture) can enhance reusability at a Coarser grained level.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Glad to help, but any reason for a B? You can ask for more clarification if you want.
An EJB is like a remote and reusable Java component, which is available to clients and to which clients can make calls for executing some business-logic and receive the response. However, it internally uses RMI and that requires the client to be a Java client. It requires an EJB container to run.
Web services can be developed using any language (Java, .NET, etc) and can be called from any client (Java, .NET, etc) because they use HTTP and SOAP standards and are deployed on web-servers (just like you can have a browser developed in any language deployed on any platform talking to a web-site developed using any technology). So they are like services available on the Web which can be used. They are generally used as means of doing interop between different kinds of technologies. Microsoft has come up with a concept of WSE where you can deploy a web-service without having a web-server but essentially that would require you to install WSE (which will do what a web-server would do - implement SOAP and HTTP protocols for handling web-requests and send web-responses).