Found the problem. Virtual host's files MUST be deployed in the deploy
directory. I simply put a symbolic link (on Linux) named with a .war suffix
For symbolic links on Windows, see
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3887963
Also, I removed the
appBase="c:\\domaindirector
I have the same issue - did you ever solve the problem?
I think this is because when you deploy something directly in tomcat, it's not
using jboss's JNDI context. So i would think you could simply define the
resource in the server.xml itself. But apparently that doesn't work either ...
still w
The problem still occur when the webapp is deployed as an exploded virtual
host. See above for server.xml .
Do we still have to specifiy a jboss-web.xml since only env-entry elements are
to be available via JNDI?
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic
Th problem doesn't occur when the webapp is deployed as a .war archive in the
/deploy directory.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935606#3935606
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3935606
---
Could it be related? We configured a virtual host this way (stacktrace below):
|
|
| www.domainname.com
|
|
2006-04-05 15:00:25,849 WARN [org.apache.struts.action.RequestProcessor]
Unhandled Exception thrown: class javax.naming.NameNotFoundExcept
We get a:
javax.naming.NameNotFoundException: env not bound
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935206#3935206
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3935206
-
The struts action has an incorrect context class loader, or has introduced a
jndi.properties that is corrupting the naming environment. Stacktrace is step 1.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3935215#3935215
Reply to the post :
http://www.jboss.c