What is the plan for EJB 3 support

JBoss is going to start bundling EJB 3 with their server. It might be
nice to be able to take advantage of the container.

8 comments
Comment actions Permalink

In article <d9f32n$r53$1@is.intellij.net>,
Norris Shelton <nunya@nunya.net> wrote:

JBoss is going to start bundling EJB 3 with their server. It might be
nice to be able to take advantage of the container.


On a spec that's not done yet??? Waste of time right now if you ask me.

R

0
Comment actions Permalink


Hell, Alain's already submitted requests for JUnit 4.0, and it's basically only available on Erich Gamma's laptop.

Seriously, I submitted a request a while back for automated EJB 2.0 -> 3.0 translation, and Maxim seemed to smile favorably on it for some post-Irida release. Make of that what you will.

--Dave Griffith

0
Comment actions Permalink

Dave

>Hell, Alain's already submitted requests for JUnit 4.0, and it's basically only available on Erich Gamma's laptop.
>

>

That's because I didn't trust my memory, and I also knew beforehand that
you would suggest to JIRA it for you to keep a trace...
so I just took a shortcut.

Alain

0
Comment actions Permalink

Like Alain said, putting it in Jira is one thing, it can sit there and
stew for a while, pushing it as a really important feature because JBoss
implemented it is another. My point was just because JBoss did it, it
doesn't mean the whole IDE industry should follow. And just because
JDeveloper 10g has EJB3 support, doesn't mean IDEA should have it right
now as well. There are enough instabilities and corners to be polished
in the current version, adding more code that's going to change every
time the spec changes is even worse for an IDE.

R

0
Comment actions Permalink

Robert S. Sfeir wrote:

Like Alain said, putting it in Jira is one thing, it can sit there and
stew for a while, pushing it as a really important feature because JBoss
implemented it is another. My point was just because JBoss did it, it
doesn't mean the whole IDE industry should follow. And just because
JDeveloper 10g has EJB3 support, doesn't mean IDEA should have it right
now as well. There are enough instabilities and corners to be polished
in the current version, adding more code that's going to change every
time the spec changes is even worse for an IDE.

R


But quite a few developers seem to like EJB3 support... me included.

Messi

0
Comment actions Permalink

But quite a few developers seem to like EJB3 support... me included.


That's nice... so do I... when the spec is done.

R

0
Comment actions Permalink

Nothing prevents me from using EJB3 right now with IDEA. It's Java with annotations afterall, yeah? So go do it already, do it and come back here and tell us what you think of it and what to do and what not to do.

0
Comment actions Permalink

Patrik Andersson wrote:

Nothing prevents me from using EJB3 right now with IDEA. It's Java with annotations afterall, yeah? So go do it already, do it and come back here and tell us what you think of it and what to do and what not to do.


I'm already using EJB3 that way for a few months... thus I'd be happy
for a bit more tool-support (just a bit, I suggested some things, esp.
being able to see the beans in the J2EE view (this is possible through a
"workaround", entering the EJB3 beans into the DD, but then there are
errors in the DD...)).
Do you mean "make suggestions" by "what you think of it and what to do
and what not to do"?

regards,

Messi

0

Please sign in to leave a comment.