I've been having a look at the patch (sorry for the delay), and it looks fine, but I was hoping to reproduce the problem before committing the patch. I'm having some problems doing this - I've started with a fresh download of Tomcat 5.5.27, and the released OpenEJB 3.1 WAR from the website.

I've extracted Tomcat to D:\Java\apache-tomcat-5.5.27, I extracted openejb.war to D:\Temp\openejb and created a new Tomcat base directory under D:\Temp\SRV, and added this to server.xml:

<Context docBase="D:\Temp\openejb" path="/openejb" reloadable="false"/>

And I don't see the exception you're getting. I've also set up a WTP Tomcat server in Eclipse 3.4, and have tried fiddling with the server location options, and again, not seen the exception.

I guess I'm missing something here, any ideas?

As David has looked over the patch, and is ok with it, I'm happy to check it in, but I was hoping to give it a bit of a test first.

Cheers

Jon



David Blevins wrote:
FYI, I looked at this and all looked fine.

If you can file an "Improvement" jira so it shows up in the release notes that'd be fantastic. I won't be able to get this in myself right now, hopefully someone can get this checked in.

Thank you very much!  Sorry it took so long to look it over!

-David


On Nov 13, 2008, at 12:52 AM, Jean-Sébastien Scrève wrote:


Oups sorry....

Hope this will be fine. I'm not used to do so.

I based it on the 3.1-SNAPSHOT version.

Best regards,

Jean-Sébastien Scrève.

http://www.nabble.com/file/p20476893/OpenEJBListenerPatch.txt
OpenEJBListenerPatch.txt


Alex Grönholm-2 wrote:

Jean-Sébastien Scrève kirjoitti:
Hi,

I've been working with OpenEJB, Tomcat 5.5 and WTP for some time and I
have
a question regarding the OpenEJB deployment in Tomcat.

By default, OpenEJB is installed into Tomcat itself and everything works
fine.
With WTP, we have the possibility to let the Tomcat installation
unchanged
and define a Context that points to our web application. (The context is
defined in the server.xml configuration file). Doing that allows us to
put
our web application wherever we want.
Currently, defining OpenEJB as a context in Tomcat fails : an exception
is
launched at startup.
By defining OpenEJB as a context, I mean adding something like that in
the
server.xml :
<Context docBase="D:\tempWebApp\openejb-tomcat-webapp-3.1.0" path=""
reloadable="false"/>

I've made a small change in OpenEJBListener.java to make it work in my
environment. I've made only simple basic tests for now.

Is there any restriction for such kind of deployment ? Do you think you
could take this modification into account ?

Best regards,

Jean-Sébastien Scrève

Ps : attached file :
http://www.nabble.com/file/p20377766/OpenEJBListener.java
OpenEJBListener.java

In the future, please send patches instead of modified files. It'll be
much easier to figure out what you changed.



--
View this message in context: http://www.nabble.com/OpenEJB-in-Tomcat-and-WTP-tp20377766p20476893.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.




Reply via email to