env-entry elements not bound with virtual hosts (external di

[dduchaine]

JBoss 4.0.2 and 4.0.3

env-entry elements specified in web.xml are not put in JNDI when a virtual host is deployed with an external directory.

I have this server.xml config:

appBase element c:\\domaindirectory has the .war structure

<Engine name="jboss.web" defaultHost="localhost">
<Host name="domainname.com" appBase="c:\\domaindirectory" autoDeploy="false" deployXML="false">
 <DefaultContext allowLinking="true" useNaming="true" override="true"/>
 <Context docBase="." path=""/>
 <Alias>www.domainname.com</Alias>
 <Valve className="org.apache.catalina.valves.AccessLogValve" prefix="domainname_com-" suffix=".log" pattern="common" directory="${jboss.server.home.dir}/log"/>

</Host>
</Engine>

Am I missing something here?

[dduchaine]

Simpler question here:

Is it possible to deploy an exploded directory which has the .war structure outside the jboss deploy/ directory?

Part of the answer is yes because we currently have a working webapp (jsp compilation, execution and reloading) deployed this way BUT services provided by JBoss such as JNDI and JAAS are not visible to the application.

Where should we look?

[j2ee_junkie]

Are these JNDI and JAAS services available to your application if you deploy in $JBOSS_SERVER/deploy directory?

Also, I am not sure, but I think setting up JNDI references is a two step process. The web.xml elements specify how to map resources from names that are deployment specific to names used by application. Then you must also map from the server environment name to your deployment environment name. See http://tomcat.apache.org/tomcat-5.5-doc/jndi-resources-howto.html for more details.

Finally, I would try to look at TRACE logging of the Deployer and JNDI actions to see how things are getting bound(or not bound).

hope this is helpful, cgriffith[/url]

[j2ee_junkie]

I am sorry if I am miss-leading. I am not sure what exactly your application is not able to access. My post before assumes that you are having trouble setting a resource reference. However, after reading your post again, as well as the other thread (http://www.jboss.com/index.html?module=bb&op=viewtopic&t=80616), I am sure I am way off base.

That said, I would still look at TRACE logging to see what is happening when war is deployed.

If you have any other info, let us know so we can help,
cgriffith

[dduchaine]

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:\\domaindirectory"
autoDeploy="false"
deployXML="false"

attributes found in the Host element in server.xml
(which was used to specify the webapp's root directory)

Now the webapp is hooked into JBoss and JNDI, datasources, JAAS are accessible as expected.

thanks for your time