The Apache Xang engine is currently implemented as a Java Servlet.
You must include xang.jar, xalan.jar, xerces.jar and fesi.zip in the
Servlet class path.
Consult your Servlet engine documentation for detailed instructions.
The Xang servlet needs to be registered with your Servlet engine.
The servlet class name is: org.apache.xang.net.http.object.impl.HTTPObjectServer
The servlet initialization parameters are: config=full-path/to/your/xang.cfg
For the Apache JServ servlet engine, this is the configuration information to place in zone.properties
to register the Xang servlet:
servlet.org.apache.xang.net.http.object.impl.HTTPObjectServer.initArgs=config=full-path/to/your/xang.cfg
In addition, the Web server or Servlet engine needs to be configured to pass requests to
files with a .XAP extension to the Xang servlet. Consult your Servlet engine documentation
for detailed instructions.
For the Apache JServ servlet engine, this is the configuration information to place in zone.properties
to register the Xang servlet:
servlet.org.apache.xang.net.http.object.impl.HTTPObjectServer.initArgs=config=D:\projects\apache\modules\xml-xang\java\src\org\apache\xang\xap\xang.cfg
For the Apache JServ servlet engine, this is the configuration information to place in the jserv.conf
for getting the Xang servlet to handle .xap files:
ApJServAction .xap /servlets/org.apache.xang.net.http.object.impl.HTTPObjectServer
To run XSLT extensions, include bsf.jar and bsfengines.jar.
All these JAR files are distributed with Xalan.
For extensions implemented in JavaScript or another scripting language,
see the Xalan extensions language requirements
to identify any additional JAR files you must place on the class path and where you can get them.
