To prove this, modify the jboss-service.xml deployment
descriptor in the C:\jboss-3.0.6\server\all\deploy\http-
invoker.sar to start as follows:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE server>
<!-- $Id: jboss-service.xml,v 1.1.4.6 2003/01/03 21:39:21
starksm Exp $ -->
<server>
<local-directory path="invoker.war"/>
<!-- The HTTP invoker service configration
-->
<mbean
code="org.jboss.invocation.http.server.HttpInvoker"
...
When SARDeployer processed local-directory elements,
it assumed that it was dealing with a compressed sar/jar
file. In the case of an expanded SAR this caused a
ZipFile exception.
To fix, an if-else was added to SARDeployer's init
method. If the SARDeployer is dealing with an
expanded SAR when processing local-directory
elements, it calls a new method, copyLocalDirectories.
The copyLocalDirectories method recursively copies the
contents of the local-directory to the data directory.
SARDeployer