Saxon:Webapp

From EXPath

(Difference between revisions)
Jump to: navigation, search
Line 2: Line 2:
==Configuration==
==Configuration==
 +
 +
Servlex can be downloaded from its [http://code.google.com/p/servlex/downloads/list Google Code project].
Servlex is a typical Java EE web application, relying only on the Servlet specification.  It uses an EXPath repository on the disk.  The exact location of the repository is read via the system property <code>org.expath.servlex.repo</code> (this is the directory at the root of the repository).  For Tomcat, you can set the property by adding the following to the global <code>catalina.properties</code> file:
Servlex is a typical Java EE web application, relying only on the Servlet specification.  It uses an EXPath repository on the disk.  The exact location of the repository is read via the system property <code>org.expath.servlex.repo</code> (this is the directory at the root of the repository).  For Tomcat, you can set the property by adding the following to the global <code>catalina.properties</code> file:
Line 24: Line 26:
};
};
</pre>
</pre>
 +
 +
Once you've deployed the WAR in your application server, you can see if everything is fine by accessing the application page.  For instance, if you use Tomcat locally on http://localhost:8080/, just navigate to http://localhost:8080/servlex/.

Revision as of 20:38, 1 August 2010

Servlex is the implementation of the EXPath Webapp module using Java Servlet technology for the server part, and Saxon and Calabash for the XSLT, XQuery and XProc processing.

Configuration

Servlex can be downloaded from its Google Code project.

Servlex is a typical Java EE web application, relying only on the Servlet specification. It uses an EXPath repository on the disk. The exact location of the repository is read via the system property org.expath.servlex.repo (this is the directory at the root of the repository). For Tomcat, you can set the property by adding the following to the global catalina.properties file:

org.expath.servlex.repo=/some/path/to/servlex/repo

For Tomcat on a server, the following security permissions should also be set (in the policy file):

grant codeBase "file:${catalina.base}/webapps/servlex/-" {
    // the repository dir
    permission java.io.FilePermission "/some/path/to/servlex/repo/-", "read";
    // commons xml resolver does read those properties
    permission java.util.PropertyPermission "xml.catalog.*", "read";
    permission java.util.PropertyPermission "user.dir", "read";
    // if you use the http client module within the stylesheets
    permission java.util.PropertyPermission "org.expath.hc.http.version", "read";
    permission java.net.NetPermission "getProxySelector";
    permission java.net.SocketPermission "site-accessed.com", "resolve,connect";
};

Once you've deployed the WAR in your application server, you can see if everything is fine by accessing the application page. For instance, if you use Tomcat locally on http://localhost:8080/, just navigate to http://localhost:8080/servlex/.

Personal tools