Sorry, my server crapped out for a moment. It is now back. And no, you don't need to declare the EJB beans in the <Context>. You only need to do this if you want to lookup beans via Tomcat's JNDI.
Regards,
Lajos
Philip Chan wrote:
I basically followed the steps in lajos instructions.. Hmm.. I can't seem to get to them anymore.. (If anybody knows or as a copy, could they email it to me, as I didn't get a copy on file)
biggest question is still.. do I need to declare the EJB beans in the tomcat context, like that in your instructions for the pre-version 1
The steps I followed were:
download steps, build steps, etc.. but skipped the standalone and tomcat wide steps, adn went directly to the per webapps steps.
Phil C.
Jacek Laskowski wrote:
Philip Chan wrote:
I placed simpletest.jar into my webapps lib, as placing it in common/lib would defeat the purpose of having a per wepapp installatioin
but still have problems in the look up.
I am wondering if the problem is that in this scenario and in your instructions there was nothing about adding the Bean declaration in the webapps context.
Do we still need to do this, as this was one of the key differences between your instructions for OpenEjb1 and Jacek instructions for OpenEjb?
Hmm, I'm lost. Could you describe the steps to do in order to reproduce the issue? I'd be happy to update the docs to avoid any future roadblocks others may have.
It's definitely true to not put the beans in common/lib as doing so would pollute Tomcat installation. Also, as Dave pointed out, it would violate the principle of being able to update your own webapp nor Tomcat installation that's most likely read-only. Think of a scenario where two people have the same bean deployed and both would have to place the beans to common/lib.
Phil C.
Jacek
--
