• Post Reply Bookmark Topic Watch Topic
  • New Topic

What goal/purpose of EJB 3.0 ?

 
somkiat puisungnoen
Ranch Hand
Posts: 1312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
What goal/purpose of EJB 3.0 ?

I'm confusing in goal/purpose of EJB 3.0 because I'm studying with EJB 2.0.
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Copied from EJB 3.0 draft spec
1.2 Goals of this Release
The purpose of EJB 3.0 is to improve the EJB architecture by reducing its complexity from the enterprise
application developer�s point of view.
EJB 3.0 is focused on the following goals:
� Definition of the Java language metadata annotations that can be used to annotate EJB applications.
These metadata annotations are targeted at simplifying the developer�s task, at reducing
the number of program artifacts the developer is required to provide, and at eliminating theneed for the developer to provide an EJB deployment descriptor. Use of metadata annotations
can also be used to enable the generation of interfaces for an enterprise bean from the bean
class itself.
� Specification of programmatic defaults, including for metadata, to reduce the need for the
developer to specify common, expected behaviors, and requirements on the EJB container. A
�configuration by exception� approach is taken whenever possible.
� Encapsulation of environmental dependencies and JNDI access through the use of annotations,
dependency injection mechanisms, and simple lookup mechanisms.
� Simplification of the enterprise bean types. Enterprise beans are simplified to more closely
resemble plain Java objects (�POJOs�) or JavaBeans.
� Elimination of the requirement for EJB component interfaces for session beans and entity
beans. The required business interface for a session bean is an ordinary Java interface
(�POJI� or plain old Java interface), not an EJBObject, EJBLocalObject, or java.rmi.Remote
interface. No interfaces are required for entity beans.
� Elimination of the requirement for Home interfaces.
� Simplification of container-managed persistence.
� Support for light-weight domain modeling, including inheritance and polymorphism.
� Specification of Java language metadata annotations for the object/relational mapping of
entity beans with container-managed persistence.
� Enhancements to EJB QL to provide greater usability. Addition of projection, explicit inner
and outer join operations, bulk update and delete, subqueries, and group-by. Addition of a
dynamic query capability and support for native SQL queries.
� Reduction of the requirements for usage of checked exceptions.
� Elimination of the requirement for the implementation of callback interfaces.
� Improved ability for testing outside the container.
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
somkiat ,

EJB 3.0 is still in the draft stage, so need to get confused.
Sun is accepting comments/suggestions from the EJB community, so If you have any please download the spec and provide your valuable comments to Sun before 31 st July.

Experts feel that it is going to take more than a year before an implementation comes out.

 
Nicholas Cheung
Ranch Hand
Posts: 4982
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Seems EJB 3.0 is going to make Entity Bean becomes less complicated, by going back to the POJO.

Will EJB 3.0 also take the feature of Hibernate and Spring?

Nick
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
As I mentioned before in one of my posts, EJB 3.0 persistence is based on Hibernate.
 
Alexandru Popescu
Ranch Hand
Posts: 995
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
[...]EJB 3.0 persistence is based on Hibernate

philosophy, not Hibernate itself. Many guys are angry about this so we must keep the things clear.
 
somkiat puisungnoen
Ranch Hand
Posts: 1312
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Pradeep Bhat:
As I mentioned before in one of my posts, EJB 3.0 persistence is based on Hibernate.



I thing in EJB 3.0 persistence is base on JDO or not???

please comment..

 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I thing in EJB 3.0 persistence is base on JDO or not???

It is based on hibernate philosophy.
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Ali Pope:

philosophy, not Hibernate itself. Many guys are angry about this so we must keep the things clear.


If someone is angry, let them
 
Nicholas Cheung
Ranch Hand
Posts: 4982
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I guess someone maybe unhappy, as SUN starts eating their markets. Just like what SUN did for xerces, xalan, log4j, etc. SUN has already migrate those open source project features into its J2SE 1.4 platform.

Nick
 
Jeroen Wenting
Ranch Hand
Posts: 5093
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
mostly people are angry that Sun has basically turned over control of the EJB specification to JBoss.
 
Pradeep bhatt
Ranch Hand
Posts: 8933
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jeroen Wenting:
mostly people are angry that Sun has basically turned over control of the EJB specification to JBoss.


Yes but Hibernate is a good ORM framework. It is also not surprising that JBoss 4 app server has recently been certified as a J2EE 1.4 server. JBoss is receiving the certification for the first time.
 
Peter den Haan
author
Ranch Hand
Posts: 3252
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Jeroen Wenting:
mostly people are angry that Sun has basically turned over control of the EJB specification to JBoss.
Then mostly people have failed to read the most basic information available to them. Please explain how participation of just about every company that means something in the J2EE world constitutes "turning over control to JBoss".

- Peter
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!