I have just finished reading through the EJB 3 specification http://java.sun.com/products/ejb/docs.html and find it very interesting as it resembles the concept of X-Doclet (annotation or attribute based programming). Is MyEclipse team watching/working/implementing EJB 3.0? How soon can we expect this to be integrated with MyEclipse?

I wonder if this is end of X-Doclet (atleast for EJB)?

I don't believe we are explicitly working on EJB 3 support righ tnow, but if user demand is strong enough we will begin to address it.

Why not be into the market when the final draft of J2EE 3 spec. is finish. Look at what JBOSS is doing ! XDoclet will die when J2EE 3.0 comes out. The JVM 5.0 (1.5) is already here with meta tags ! And less xml documents we need to spesify ! I've already experience with .NET (c#) meta tags. It's a killer !

Tore Gard

What is the eta of j2ee 1.5 / ejb 3.0?

The JBoss IDE already has some support for this afaik, at least for AOP.

The EJB 3.0 Preview Release is already out and is been integrated in JBoss & Resin

http://www.jboss.org/ejb3
http://www.caucho.com/resin-3.0/features/resin-3.0.9.xtp

I filed this as an enhancement, lets see how it falls in our priority list.

Take a look at http://www.eclipse.org/jsr220orm/

Hasn't been much traction on this thread. According to the JBoss roadmap, the final release of 4.0.3 will be out tomorrow with the EJB3.0 integration to be finalized by 8/31. Of course these dates will likely slip but it's indicative of how far along the ejb3.0 spec has come.

The RC2 release of JBoss 4.0.3 has given me a glimpse of how ejb3.0 will work and I'm quite impressed. The custom annotations seem much simpler (and less spammier) than the equivalent xdoclet.

So any news on ejb3 support within myeclipse?

warpig,
We are looking at fleshing out the EJB support for the 5.0+ release series, the JBoss group does great work and we will likely pull in the parts that are a "must have".

I have been using JBoss with EJB3 support in a project. Early, I know but it is works reliably IMHO, we have just had to deal with various annotation updates as the spec evolves. But Boy, is it easier to work with that 2.x!As long as you name your myeclipse projects with a .par and .ejb3 extensions for persistence and session bean projects respectively, and add the ejb3 libraries to the eclipse build path, it pretty well works. The annotations aren't much once you get used to them. Would be great to have ME deal with the libraries etc, but not too bad without this.

We've also been working with EJB3, JBoss and MyEclipse for a while. It co-exists with no problems, that's one thing. It would still be great to add some extra feautures including:

- Help on project creation, picking up the up-to-date jars from JBoss EJB3. (can come from JBoss IDE)
- Help on project deployement. Automation of the packaging of the ejb3, par, war and ear. Having EJB3 recognized as deployable features would help. May be just a tool to help creating the Ant build file ?
- A wizard for reverse engineering from existing tables would be really magic. (Oracle has plans for that in JDeveloper)

EJB 3 is so much easier than EJB 2 or hibernate that not much is required... Some support would still help.

Bernard

What is the eta of j2ee 1.5 / ejb 3.0?

Any experience in installing http://www.eclipse.org/jsr220orm/ over myeclipse ? Can that two coexists ? jsr220orm is nice.

support-rkalla wrote:

I filed this as an enhancement, lets see how it falls in our priority list.

MyEclipse definitly needs EJB 3.0 support. All my projects are going EJB 3.0 from Hibernate. From what I've seen, the JBoss IDE is great, but it lacks features like being able to create a J2EE project that itself contains a web project and ejb 3 project and packages everything nicely together. The JBoss IDE trailblazers have users do all this deployment packaging configuration manually which is a bit of a pain.