Hi Afryer,
Thanks, I tried the META-INF/resources.xml approach, but no luck there
either. I still can't get the datasource recognised except via openejb.xml
so far.
Also when I browse JNDI with the openejb app, I can't see the JNDI resource
defined in context.xml or resources.xml, or the
think the jndi page only show EJBs.
it is inherited from JEE5 where jndi was contextual that's probably the
reason.
- Romain
2012/3/6 Neale Rudd ne...@metawerx.net
Hi Afryer,
Thanks, I tried the META-INF/resources.xml approach, but no luck there
either. I still can't get the datasource
Hi Romain,
3. if your database if not correct, can't be created or is not found a
default one (the one you found in default openejb conf) will be used.
Normally we read context.xml in your-webapp/META-INF/context.xml. If you
manage to reproduce it in a simple test please create a jira here
Hi Guys,
Just joined the list, nice to meet you all.
We host a series of Tomcat and JBoss VMs and that's our key business area.
We're planning on starting hosting for TomEE within the next week, and have
had a couple of minor issues getting started so I thought I'd mention them.
As our
Hu,
1. it is to be spec compliant that dev is not the default mode
2. you can customize it, personally i like the default behavior since it
stays easy in dev mode and is often ok in prod mode
3. if your database if not correct, can't be created or is not found a
default one (the one you found in
I had an issue with JSPs failing to recompile with 4.0.0-beta1 described
http://openejb.979440.n4.nabble.com/openejb-overwrites-tomcat-conf-web-xml-JspServlet-lt-development-gt-parameter-value-td4213081.html#a4216277
here . The issue was caused by openejb overwriting the web.xml file with
its
