If you are using Tomcat+OpenEJB, you can use the Tomcat plugin built into every IDE to develop JEE application!

I gave a demo of using out-of-the-box intellij to develop an app with Servlets+JPA+WS+EJB at ApacheCon. The demo took about 10 minutes :D

-dain

On Dec 9, 2007, at 3:12 AM, Jacek Laskowski wrote:

On Dec 8, 2007 10:44 PM, David Blevins <[EMAIL PROTECTED]> wrote:

I understand what you mean about IDE tools beyond running applications
that extend into assisting in writing the code itself.  We have that
tool Jonathan is working on that will take an ejb 2.1 app or lower and
add the required annotations to your source code so that you won't
need the xml anymore -- a reverse XDoclet.  No one else is doing
anything like that and when they see it they'll all rush to copy it.

That's one of the reason such a plugin might be very helpful. You
could run mvn openejb:telcodx (the word 'xdoclet' reversed) and have
it done.

I don't understand what you mean by "a m2 plugin for developing ejb3
and running unit tests without much trouble." Unit testing EJBs in an
embedded EJB container that runs without much trouble is our claim to
fame.  We've been doing it since EJB 1.1 and do it so well we don't
need tools.  There's a whole directory of examples that run in m2 or
ant with no plugin at all.  Running the same tests from your IDE is
just as easy and can be done with the same setup.  Meaning you don't
need an OpenEJB-Maven plugin to run the unit tests in your build and
another OpenEJB-Netbeans plugin to run the same unit test in your IDE.

I've been thinking about it today and I must admit you helped me a lot
to figure out what I was after. You mentioned that out junit tests do
all the nifty stuff right away at no cost. Just add appropriate
setUp() to your tests and you're ready to go. That's the point.
There're teams where introducing new tools are *not* an option. What I
figured out is to let people execute openejb with their m2 ejb/ear
projects right from a project with no changes at all (so others in the
team don't complain it could break a project). So, no openejb code
(even the initial context factory in setUp) and running mvn
openejb:validate would run validation of a ejb project or mvn
openejb:run that would execute openejb with the ejbs. Is it available
now? I don't think so.

Jacek

--
Jacek Laskowski
http://www.JacekLaskowski.pl

Reply via email to