• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

WHY EJB 3.0

 
Greenhorn
Posts: 6
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Why do we need EJB 3.0 when we have EJB 2.0.what are the Limitations encountered in EJB 2.0.
I fyou could let us know so that we can think of shifting our application from EJB 2.0 to 3.0.As i have heard its diffrent from EJB 2.0 altogether.
 
Sheriff
Posts: 14691
16
Eclipse IDE VI Editor Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
EJB2.X need lots of configuration, lots of interfaces. They also suffered because of Entity Beans. The persistence model is not cool.
The new version improves all of this, easing the pain of ejb developpers.
(I think that it doesn't make sense to explain in detail if you don't already know 2.X)
 
Ranch Hand
Posts: 342
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

If you don't find any limition in ejb 2.0, don't migrate it.

btw, check this link:
http://java.sun.com/javaee/overview/faq/javaee_faq.jsp#whymove

cheers
 
Ranch Hand
Posts: 1847
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Maybe a more pragmatic question would be whether it's possible to have an application that is a mix of 2.x and 3.x EJBs, and what the implications of this would be.

In other words, can I in an existing EJB 2.x application (once it's running in an application server that supports EJB 3.x) deploy EJB 3.x compliant EJBs or will they have to exist in an application of their own.
 
Ranch Hand
Posts: 8945
Firefox Browser Spring Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Mixing EJB 2.x with EJB 3.0 is possible as said by the author.
 
Christophe Verré
Sheriff
Posts: 14691
16
Eclipse IDE VI Editor Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
This would make migrating easier. No need to upgrade the existings beans. I wonder if we really can do that.
 
author
Posts: 304
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

In other words, can I in an existing EJB 2.x application (once it's running in an application server that supports EJB 3.x) deploy EJB 3.x compliant EJBs or will they have to exist in an application of their own.

You cn write 2.x beans and 3.0 beans in the same application. They would be in different EJB modules though.

This would make migrating easier. No need to upgrade the existings beans. I wonder if we really can do that.


I never lie.
 
The City calls upon her steadfast protectors. Now for a tiny ad:
a bit of art, as a gift, the permaculture playing cards
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic