On Tue, 30 Mar 1999, James Duncan Davidson wrote:
[snip]
> Actually, right now all path mappings are optional in the spec -- this
> is something that we will be looking to tighten in the next version of
> the spec.
>
> .duncan
>
Hi Duncan,
Perhaps there should be ways for the servlet developer
(through api) to specify what rules wants/needs to be used for a particular
servlet.
Few examples to be more explicit:
- Someone is writing a servlet wich relies heavely on
PathInfo to perform actions (not only on request parameters).
Thus we don't want such a servlet to be used within
any .type (file-extention) mapping, in wich getPathInfo() makes
no sense to this kind of servlets.
The problem may be reversed, e.g. someone is writing a servlet
specifically to deal with certain ".types".
A good example: a servlet capable to convert .xls
files to .html ... or other "format converters" implemented as servlets.
Mabe some sort of "INeedPathPrefixMapping",
"INeedTypeExtentionMapping" empty interfaces will be usefull -
to let the servlet developer tell the servlet engine / deployer,
how *he* expects/want to be used.
Other means than empty interfaces may be considered.. like
an "Servlet.getServletSpecificRequirements()" call.
- The servlet developer's capability to deny
sub-path mapping to other servlets - to tell wich
servlets need to "be in charge" for their servlet-path
prefix, overriding any other longest-prefix-match sub-dir servlets..
- Similar needs that a servlet might request
from its servlet-environment:
a. "I need a non-empty return from getRemoteUser()"
So the servlet-runner alerts the administrator, at installation
time to enable identification/authorisation for some servlets.
b. "I need access to local file system" - so administrator is
aware of that and is able to deny or grant access to some specific
directories/files.
Whole idea is to get more user-friendly with administrators
consistently across servlet-engines..
- <servlet ..> tags or other form of includes, server-side internal
redirects... like the new RequestDispatcher.
What the url semantics are in these cases? - talking about
getServletPath(), getPathInfo() calls.
Probably some extra calls to make distinction betwen the paths used
within http request and the paths used to trigger a servlet
by an RequestDispatcher are usefull.
---------------------------------------------------------------------
I mention other issues too, not being related to path mapping:
- developer should be able to group/deploy servlets within applications
(or other name, "package" is used) instead of individual servlets.
Now, after installing few servlet-based "applications" adminitrators
lose the count on wich servlet belong to wich application, or
which the meaning of configuration parameters is.
How servlet-based applications are uninstalled?
- Means for some servlets to tell their envoironment
they require some specific configuration parameters.
e.g a mail servlet needs to know SMTP and POP/IMAP server addresses,
so the developer wants to tell the servlet engine what configuration
parameters should be requested from a local administrator.
(JWS's approach with bean servlets is interesting..)
- a servlet being able to say "I want to be loaded as soon as
engine starts" vs. let the administrators to do that.
(So we-ll be able to have a guaranteed initialisation/configuration
for a group of servlets, if a "first-started" servlet takes care of
all necessary configurations).
------------------------------------------------------
Thanks,
Cezar
Cezar Totth email: [EMAIL PROTECTED]
Fax: (401) 220 33 95
Genesys Software Romania Phone: (401) 638 49 44
Stefan Furtuna 169, sect.6
cod 77171, Bucharest
Romania
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
