Yes, take a look here. This is the serverdef file used for Geronimo
when it was using the Generic Server Framework.
https://svn.apache.org/repos/asf/geronimo/devtools/eclipse-plugin/
tags/1.0.0/plugins/org.apache.geronimo.devtools.eclipse.core/
serverdef/geronimo10.serverdef
"Start" as you can see is the configuration that is passed to the
generic framework in order to start the server. You need to add a
classpath entry that will be needed to start the sever. Notice in
the example how the start element references the start classpath.
For "stop", I'm not sure how openejb is implemented, but for now in
the stop method implementation of your ServerBehavior class (if you
choose to extend the generic one) you can simply kill the process
unless openejb has a specific way to stop the container.
I'll look over what you have in more detail later today and create a
JIRA with any patches or comments.
-sachin
On Feb 14, 2007, at 10:22 AM, Jeremy Whitlock wrote:
Sachin,
Excellent information. It would be nice if we didn't have to
create a
specific project type for OpenEJB but if we must, we'll do it. I
do see in
WTP 1.5.x that EJB 3.x is mentioned as an available option so I
wonder if
EE5 is available now. The facet idea is great as well because
beyond the
WTP server type, I really think the benefit of this plugin will be the
value-add stuff that will need to be enabled for OpenEJB projects.
(I use
the term project but I mean any WTP EJB project that has an OpenEJB
server
type as the project runtime.) Since this information is defined in
the
serverdef, do you have any insight as to the other portions as well?
(start, stop, classpath, launch and so on) I have some ideas but
the more
minds involved the better.
