Regarding IDEA 5 "wow factor"... how about (beginning) EJB3 support?

I know that EJB3 is currently only EDR2 and will probably be changed a
bit... still, there are already a few EJB3 implementations (Oracle OC4J,
JBoss and both Hibernate & TopLink suppoer EJB3 Entities in other
Application Servers), both JDeveloper and Eclipse are going to support
EJB3 quite soon, very probably before IDEA 5.5 or 6.0.
Thus, wouldn't it be a good idea to support EJB3 in IDEA 5, at least
"beginning support"?
Most of it is already there (Annotations), a starting point would be to
show EJB3 beans in EJB Modules (i.e. classes annotated @Stateless,
@Stateful, @MessageDriven and @Entity), other things like working with
their interfaces is already mostly supported by IDEA's standard tools.
Of course, support could go further and there will be changes, but it
should mostly be a thing of templates and, as said, showing them in EJB3
modules as EJBs - or is this already possible somehow (other than
writing a plugin)? This should be rather easy to accomplish and the next
version of IDEA could then quickly support the new specs. This could
probably be made available as an updateable plugin.
I just think this would be cool from my very own perspective: I love
IDEA and its features, but when JDeveloiper would support EJB3 I'd be
very tempted to switch...

kind regards,

Messi

2 comments
Comment actions Permalink


I've already submitted an issue for (semi-) automated translation of EJB2.0 (interface+deployment descriptor) -based configuration to EJB3.0 annotation-based configuration. It's in the backlog with a "Major" importance, so I wouldn't be surprised to see it in the release post-Irida. I suppose it would also be handy to see the existing interface-based EJB icons for annotation-based EJB's as well, and some other polishing like automated entry-point detection for appropriately annotated methods. Templates corresponding to EJB3.0 syntax would be trivial to add, paralleling the existing templates. Beyond that though, I thought the whole point of EJB 3.0 is to make it so that less intensive tool support is needed, not more.

--Dave Griffith

0
Comment actions Permalink

Dave Griffith wrote:

I've already submitted an issue for (semi-) automated translation of EJB2.0 (interface+deployment descriptor) -based configuration to EJB3.0 annotation-based configuration. It's in the backlog with a "Major" importance, so I wouldn't be surprised to see it in the release post-Irida. I suppose it would also be handy to see the existing interface-based EJB icons for annotation-based EJB's as well, and some other polishing like automated entry-point detection for appropriately annotated methods. Templates corresponding to EJB3.0 syntax would be trivial to add, paralleling the existing templates. Beyond that though, I thought the whole point of EJB 3.0 is to make it so that less intensive tool support is needed, not more.

--Dave Griffith


Sure, EJB3 needs less tool support, but a bit of it is always good, even
for standard Java ;)
Currently I use EJB3 by rudimentarily entering the session beans into
ejb-jar.xml (which I don't need at the moment) so they show up in the
J2EE view. I also changed the J2EE patterns so they produce EJB3s.
This works quite well, the beans show up in J2EE view and get the
correct icons (though ejb-jar.xml is now invalid :-).
It was quite easy to "extend" IDEA this way, so I thought this could be
done by JB so I don't need to "hack" IDEA (and only get half of the
support). You could maybe introduce a "hidden" DD to manage EJB3
beans... for now.

kind regards,

Messi

0

Please sign in to leave a comment.