Logo 
Search:

Java Forum

Ask Question   UnAnswered
Home » Forum » Java       RSS Feeds

JBoss configuration

  Asked By: Kaua    Date: Dec 31    Category: Java    Views: 683
  

I've been trying to change my deploy path in JBoss
My ejb container deployer and my tomcat servlet container deployer path don't change.

i've tried to change my ejb deployer path according to this way :

1: /jboss-4.2.1.GA/server/default/conf/jboss-service.xml

default :
<attribute name="URLs">
deploy/
</attribute>

i've changed it to
<attribute name="URLs">
~/Public/myejbfile/
</attribute>

also for my servlet container Tomcat

2: /opt/jboss-4.2.1.GA/server/default/deploy/jboss-web.deployer/server.xml

i've added this tag

<context path="localhost" docBase"~/Public/myweb" debug="0"></context>

but i encounter to many exceptions from JBOSSSSSSSSS
some body helps me.

Share: 

 

2 Answers Found

 
Answer #1    Answered By: Percy Morgan     Answered On: Dec 31

you can use this code for change  your TomcatDeployer Directory in jboss-service.xml

<attribute name="URLs">
file:/c:/deploymentPath/
</attribute>

If the URL ends in "/" it is considered a collection and scanned.URLs may be local (file:) or remote (http:). Scanning is supported for remote URLs but unpacked deployment units are not.

 
Answer #2    Answered By: Aaron Kennedy     Answered On: Dec 31

You change  yor deploy  path only from DeploymentScanner service in conf/jboss-service.xml, it's no different between ejb  and servlets, both can be deployed in same deploy path.

This is from documentation:

<!-- URLs are comma separated and resolve relative to the server home URL
unless the given path  is absolute. If the URL ends in "/" it is
considered a collection and scanned, otherwise it is simply deployed;
this follows RFC2518 convention and allows discrimination between
collections and directories that are simply unpacked archives.
URLs may be local (file:) or remote (http:). Scanning is supported
for remote URLs but unpacked deployment units are not.
Example URLs:
deploy/
scans ${jboss.server.url}/deploy/, which is local or remote
depending on the URL used to boot the server
${jboss.server.home}/deploy/
scans ${jboss.server.home)/deploy, which is always local
file:/var/opt/myapp.ear
deploy myapp.ear from a local location
file:/var/opt/apps/
scans the specified directory
http://www.test.com/netboot/myapp.ear
deploys myapp.ear from a remote location
http://www.test.com/netboot/apps/
scans the specified WebDAV location
-->

 
Didn't find what you were looking for? Find more on JBoss configuration Or get search suggestion and latest updates.




Tagged: