I have finally(!!!) made this example run. 
Server wasn't deploying jars from its webapps folder because in server
settings, selected option was "Use workspace metadata (does not modify
Tomcat installation)". After selecting option "Use Tomcat installation
(takes control of Tomcat installation)" this project is being deployed on
server startup. Also, now I can see log messages in Console window about
deploying this project, and registering EJB components from deployed jar.
This video <http://www.youtube.com/watch?v=xmcajUixCaw>   helped me a lot.

About TomEE and OpenEJB integration:
The guy from the video, says that he has downloaded and added openejb.jar
file to tomee/webapps folder. And then he goes to localhost:8080/openejb
(OpenEJB and Tomcat integration page), which is I suppose openejb webapp. I
like the option JNDI Browser he uses. 

I thought that OpenEJB is EJB container that comes prebundled with TomEE. Do
I need to download OpenEJB jar, and put it to TomEE/webapps folder? I'm not
quite sure now is it usual when setting TomEE server, that OpenEJB should be
downloaded separately and added to tomee/webapps folder?



--
View this message in context: 
http://openejb.979440.n4.nabble.com/JNDI-LOOKUP-error-Cannot-open-input-stream-to-server-tp4665304p4665367.html
Sent from the OpenEJB User mailing list archive at Nabble.com.

Reply via email to