Table of Contents
Advertisement
Legacy Configuration Files
to
# a heavy peformance penalty
#
################################# rules
################################
/mytest1=tracker
/mytest2=demo1
Using Regular Expressions in rules.properties
Enterprise Server supports regular expressions in the
run a given servlet when the incoming URL matches with a regular expression.
However, the example given in the file header is incorrect:
# Example:
#
# /simple=SimpleServlet\n
# @.*\\.example=wasp
The
\\
example
/my/
subsequently changing the whole semantics. To get around this, specify the regular
expression without the
@.*[.]example$=wasp
For another way to direct files of a specific type to a specific servlet, see the
description of the
described in the Servlet 2.3 API specification:
http://java.sun.com/products/servlet/index.html
For a way to direct files of a specific type to a specific servlet in the
see "Init Directives in magnus.conf," on page 99.
contexts.properties
The
contexts.properties
exchange data and access each other's fields, for the default virtual server only.
Contexts are useful for defining virtual servers or for code isolation. If no contexts
are defined, the default global context is used for all servlets.
92
Netscape Enterprise Server Programmer's Guide to Servlets • April 2002 (Draft)
characters are supposed to escape the (
servlet whenever there is a request for URLs such as
wasp
xxx
. However, Enterprise Server replaces
.example
or
/
servlet-mapping
) extension. The intent is to run the
.
characters:
\
element in the
file defines contexts, which allow multiple servlets to
rules.properties
or
characters with
/
\
file, which is
web.xml
obj.conf
file to
,
/
file,
Advertisement
Table of Contents
