• Post Reply Bookmark Topic Watch Topic
  • New Topic

Why EJB

 
Adela Popescu
Greenhorn
Posts: 18
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hello,

Suppose I have a client-server architecture with service oriented interfaces. In this case, the client can access the functionality that is exposed in the soi commands. Can somebody tell me if there are any advantages of EJB architecture in comparation with the soi architecture besides the threading and security?

Many thanks in advance
Adela
 
Valentin Tanase
Ranch Hand
Posts: 704
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Can somebody tell me if there are any advantages of EJB architecture in comparation with the soi architecture besides the threading and security?

More generally speaking EJB provides implicit middleware architecture; developers will focus on coding application logic and not care about security, multithreading, transactions, persistence, resource pooling, etc. So why to reinvent the wheel though? However there are other advantages that�s worth to be mentioned:
  • Client server applications usually don�t scale very well. EJB containers provide clustering services that improve the application�s scalability and reliability.
  • EJB allows you to have different type of clients: HTML web-based clients, RMI clients, IIOP clients, etc.
  • EJB provides a standard, portable component-based architecture.
  • The EJB promise, which unfortunately failed lamentably, was to provide rapid application development. However EJB 3.0 is coming and couple of years down the road and this won�t be only a promise...


  • Regards.
     
    Adela Popescu
    Greenhorn
    Posts: 18
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Hi Valentin,

    Thank you for your answer, but I am still not sure that will be a good decision to change to EJB in my company. We have a good server framework that do all the staffs like security, multithreading etc and we use TopLink for persistence. With soi it is also possible to have different type of clients. We have now a web client.
    In this case, is really better to change to EJB ?

    Regards,
    Adela
     
    Valentin Tanase
    Ranch Hand
    Posts: 704
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    I personally don't think so. You might also read this article to get a very professional advice.
    http://www-106.ibm.com/developerworks/library/ibm-ejb/
    Regards.
     
    Adela Popescu
    Greenhorn
    Posts: 18
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Hello Valentin,

    Many thanks. The article is very good.
    Daca vorbiti romaneste scrieti-mi pe heidipopa@aol.com.

    Regards,
    Adela
     
    Bhanu
    Ranch Hand
    Posts: 48
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    Using EJB can be fancy if it is really not required. Truely.
     
    Robert Hayes
    Ranch Hand
    Posts: 116
    • Mark post as helpful
    • send pies
    • Quote
    • Report post to moderator
    If you want to stick with TopLink, you should still be able to use it with BMP Entity Beans if you went EJB. Check out the preview version of JDeveloper 10.1.3 to see what interesting things you can do with TopLink + EJB.

    If you require TopLink to provide data to a web-tier, you can still use POJOs and servlets to pass data to your web-page. I'm currently doing this for a fairly small app: TopLink->DAO layer->App Services->Servlet->JSP/JSTL.

    Also, using the term EJB without qualifying what you're using in EJB (ie: entity beans, sessions beans, or message driven beans) usually gets a bad response because entity beans have a bad reputation. But stateless session beans and message driven beans seem to be fairly straight-forward.
     
    Don't get me started about those stupid light bulbs.
    • Post Reply Bookmark Topic Watch Topic
    • New Topic
    Boost this thread!