I would presume that a servlet mapping of the following kind:
<servlet-mapping>
<servlet-name>site</servlet-name>
<url-pattern>/site</url-pattern>
</servlet-mapping>
<servlet-mapping>
<servlet-name>admin</servlet-name>
<url-pattern>/admin</url-pattern>
</servlet-mapping>
would do. Let me know if it does. Additionally, the web deployment
descriptor (web.xml) is described in the spec ;-).
>To make life a bit more manageable, I'd like to have the ability to 'munge'
>the URL such that a path points to a servlet which picks up the rest of the
>URL via getPathInfo() or whatever and gather useful information as a
>precursor to actually running the JSP page.
>
>For example:
>
> http://blah.blah.com.au/site/this/that.jsp
>and http://blah.blah.com.au/admin/a/bit/deeper.jsp
>
>
>Where 'site' and 'admin' are the servlets and 'this/that.jsp' and
>'a/bit/deeper.jsp' are the 'actual' pages that get actioned by the
>respective servlet. The 'admin' servlet for example could request a
seperate
>structured secure login process, while the 'site' servlet simply gathers
>cookies, DSNs etc and runs the JSP. I know this is possible, but be damned
>if I can figure out how to set it up in Orion. I've read books, sites and
>fiddled around till I'm blue and I'm obviously missing something very
>obvious.
