Home

News: JBoss EJB 3.0 Preview Release

  1. JBoss EJB 3.0 Preview Release (20 messages)

    I'm proud to announce the EJB 3.0 Preview Release of the early draft of the EJB 3.0 specification. Special thanks goes out to the Hibernate team for putting out a great product in Hibernate 3.0. The EJB 3.0 container is pluggable with JBoss 4.0 and higher and takes some advantage of our AOP framework and some of the aspects we've written for it. For more information see the main JBoss EJB 3.0 website. We have written a detailed tutorial with examples you can build and run.

    http://www.jboss.org/ejb3

    Bill

    Threaded Messages (20)

  2. JBoss EJB 3.0 Preview Release[ Go to top ]

    Does this assume you're running jboss off of Java 1.5? I see the install step:

    * Copy jboss-aop-jdk50.deployer from the JBoss AOP RC2 distribution to the directory jboss-4.0.0/server/all/deploy
  3. JBoss EJB 3.0 Preview Release[ Go to top ]

    I'm just wondering the impact of future changes in JSR-220 ? It's maybe too soon to adopt EJB3.0 :-)

    Miguel
  4. EJB 3.0 requires JDK 5.0[ Go to top ]

    Some of the EJB 3.0 spec uses generics so we couldn't use our JDK 1.4 annotation compiler and have support for EJB 3.0 on JDK 1.4.

    Bill
  5. EJB 3.0 requires JDK 5.0[ Go to top ]

    That's fine. I just wanted to make sure. Great work!
  6. Congratulations![ Go to top ]

    your working is so quickly!
  7. JBoss EJB 3.0 Preview Release[ Go to top ]

    Its strange that when a spec is in a early draft review stage, a preview "supporting" it is already released.

    Customers have barely gotten from EJB 1.1 to 2.0 and 3.0 is still in the making. I wonder if the JBoss Group "gets it" that Enterprise Software is:

      - not about using fairly experimental technology
      - not about forcing customers to change enterprise programming models ever
        so often (maybe each iteration of the EJB 3.0 spec draft?)

    -krish
  8. JBoss EJB 3.0 Preview Release[ Go to top ]

    I think the EJB3.0 group had to answer the charges that "We won't see EJB3.0 til 2007" kind of statements that have cropped up. They've always taken a very aggressive timeline. I seriously doubt anyone is expecting to use EBJ3.0 in production systems just because of this release. But it allows the developers who are interested to check it out.

    Luckily for you, EJB1.1 and 2.0 aren't going away. Luckily for me, too. But for new projects, I am very interested to try out EJB3.0 as soon as it's stable.
  9. JBoss EJB 3.0 Preview Release[ Go to top ]

    I think the EJB3.0 group had to answer the charges that "We won't see EJB3.0 til 2007" kind of statements that have cropped up. They've always taken a very aggressive timeline. I seriously doubt anyone is expecting to use EBJ3.0 in production systems just because of this release. But it allows the developers who are interested to check it out.Luckily for you, EJB1.1 and 2.0 aren't going away. Luckily for me, too. But for new projects, I am very interested to try out EJB3.0 as soon as it's stable.
    Since Hibernate and JBoss are also on the EJB 3.0 Expert committee it also allows us to test the specification and to gather even more feedback from the community.

    Bill
  10. I wonder if the JBoss Group "gets it" that Enterprise Software is:  - not about using fairly experimental technology  - not about forcing customers to change enterprise programming models...
    That's not nice.
    If your bent is towards stable technologies, you have choices.

    However, from those of us who don't mind a little bleeding...
    ...congratulations, JBoss, on pushing the edge.
  11. Pre-Release implementations of in-draft specifications is fairly common, especially in and around J2EE. WebLogic was (in)famous for doing this with early EJB and J2EE specs.

    There is value in this in a couple of ways. First off, for the specification teams, this allows for a real-world test bed for their designs. I think we can all look at places in specifications where we scratch our heads and think "Who thought THIS was how I did business?" By getting these specs out in the field we reduce the likely hood of such muck ups.

    There is also value for the vendors, as being first to try to implement a spec gives you chances to fix bugs that always arise. Now, this isnt always true. I know during J2EE branding with a previous company I worked with, it meant early misinterpretations of the spec got deeply embeeded in our design, until the compatability test suites uncovered them.

    Which leads to the place where these early releases can do harm, and why I put WebLogic as (in)famous. The risk is that it cases vendor lockin when customers trust pre-spec early releases as gold, and build systems based on them. When the spec changes, and an API call or an approach is no longer portable, consumers are indeed harmed.

    As always, caveat emptor.

    Dave Wolf
    Cynergy Systems
  12. JBoss EJB 3.0 Preview Release[ Go to top ]

    Although I'm not a JBoss fan, I think they do "get it" when it comes to making this release at this time. I don't expect anyone from JBoss to tell you to deploy a mission critcal exterprise application on this release.

    But this allows JBoss two very important things to themselves and the community at large.

    1) JBoss gets to have a bunch of people test their implementation. As long as JBoss didn't make an unmitigated disaster of a release, developers will be helpful to find out the gaps that the JBoss group had in their initial release.

    2) JBoss will also be able to find out where there are gaps in the specification. User feedback will give JBoss the insight that they can take into the expert group and further massage the spec.

    Kudos to them and the community at large.

    John Murray
    Sobetech
  13. Geez, they are providing use with something to play with and provide feedback. I always want to know what is next so I don't design myself into a corner.

    -Pete

    PS Way to go JBoss Group!
    Its strange that when a spec is in a early draft review stage, a preview "supporting" it is already released.Customers have barely gotten from EJB 1.1 to 2.0 and 3.0 is still in the making. I wonder if the JBoss Group "gets it" that Enterprise Software is:  - not about using fairly experimental technology  - not about forcing customers to change enterprise programming models ever    so often (maybe each iteration of the EJB 3.0 spec draft?)-krish
  14. JBoss EJB 3.0 Preview Release[ Go to top ]

    I like the mechanism for dependency injection. It merges the world of JNDI and IoC very nicely.
  15. ... I wonder if the JBoss Group "gets it" that Enterprise Software is: - not about using fairly experimental technology - not about forcing customers to change enterprise programming models ever so often (maybe each iteration of the EJB 3.0 spec draft?)-krish
    How do you expect EJB 3.0 to get past the experimental stadium without anyone experimenting with it? Which is the best way to find flaws in the current spec. draft?

    If you think this release is a problem I advice you to do exactly what everyone else are going to; namely not implement it in a critical enterprise environment.
  16. Its strange that when a spec is in a early draft review stage, a preview "supporting" it is already released.Customers have barely gotten from EJB 1.1 to 2.0 and 3.0 is still in the making. I wonder if the JBoss Group "gets it" that Enterprise Software is: - not about using fairly experimental technology - not about forcing customers to change enterprise programming models ever so often (maybe each iteration of the EJB 3.0 spec draft?)-krish
    And if, instead, it should arrive 12 months later, people will complain the implementation has shipped after the standard has been set in stone.

    If JBoss is willing and able to to produce this, and keep refactoring until the final spec, that can only be a good thing. It will help people evaluate it, compare it to the alternatives, and harden the spec.

    Now if anyone is planning to use it for production, I'll be watching. From a distance. A very long distance.
  17. Its an early draft![ Go to top ]

    It is quite normal for a specification to undergo several revisions
    before it ends up anywhere close to a final draft stage.

    In fact, the EJB 3.0 early draft is quite radical in its (over)use(?)
    of experimental technology. Combined with the fact that the EJB & JDO
    specifications are uniting, I think it is fair to say that the dust
    has far from settled with respect to the EJB 3.0 specification.

    My entire point was that the current EJB 3.0 spec is an early draft
    (one of the first!). And one that could undergo major revisions if
    the theserverside.com news + other community postings are any indicator.
    And I believe it is dangerous & irresponsible of any J2EE/Enterprise
    Software vendor to expose the developer community to a preview
    implementation [at such an early stage].

    -krish
  18. Its an early draft![ Go to top ]

    My entire point was that the current EJB 3.0 spec is an early draft(one of the first!). And one that could undergo major revisions if the theserverside.com news + other community postings are any indicator.And I believe it is dangerous & irresponsible of any J2EE/EnterpriseSoftware vendor to expose the developer community to a preview implementation [at such an early stage].-krish
    It has already been well-stated by absolutely everybody else on this thread that releasing a preview of a spec is neither irresponsible nor damaging. On the contrary, it is very helpful for the community to be able to play around with the technology.

    Secondly, though, (and the reason why I am bothering to post on a thread that is on its last gasp :) is that a primary criticism of revolutionizing the EJB model has been that it will be a new and untried part of the J2EE spec. By offering this preview JBoss and others that offer previews (and the more the better) are providing some soak-time that will prove that this technology is absolutely ready (overdue, actually) for inclusion within J2EE. The EJB expert group is both supportive and appreciative of these vendors and hopes and expects more such previews to follow.

    -Mike
  19. sure krish[ Go to top ]

    It's about continuing to use something that's broken even though you know it's broken. At least ejb 3.0 is a step in the right direction. I for one are glad they are moving forward.

    --b
  20. Persistance[ Go to top ]

    So is the persistance in this version of JBOSS similiar to Hibernate ?.
    I believe the area of persistance is still being debated in EJB3.0. Am I correct in saying so ?
  21. Reference Implementation[ Go to top ]

    Does anyone know anything about the EJB 3.0 RI? Could JBoss be angling for this role? Not that I think that would necessarily be a bad thing, mind you. Just curious...