The following comment has been added to this issue:
Author: Gr�gory Joseph
Created: Tue, 27 Jan 2004 3:41 PM
Body:
Just a side note: with xdoclet2's and xdoclet-plugins's web-plugin, you have this
feature. (I am the author of that plugin)
Xdoclet2 should be released soon, but the plugins are still beta. You might want to
try it, though, and give us some feedback. I actually don't have much time to test the
plugin in real life environments for now, so that would help much, actually.
Cheers
---------------------------------------------------------------------
View the issue:
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-783
Here is an overview of the issue:
---------------------------------------------------------------------
Key: XDT-783
Summary: filter order
Type: New Feature
Status: Open
Priority: Minor
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: XDoclet
Assignee: xdoclet-devel (Use for new issues)
Reporter: Tim Chen
Created: Tue, 27 Jan 2004 10:26 AM
Updated: Tue, 27 Jan 2004 3:41 PM
Description:
According the Servlet 2.3 specs:
The order the container uses in building the chain of filters to be applied for a
particular request URI is
1. The url-pattern matching filter-mappings in the same order that these elements
appear in the deployment descriptor, and then
2. The servlet-name matching filter-mappings in the same order that these elements
appear in the deployment descriptor.
This requirement means that the container, when receiving an incoming
request:
� Identifies the target web resource according to the rules of SRV.11.2.
� If there are filters matched by servlet name and the web resource has a
servlet-name, the container builds the chain of filters matching in the order declared
in the deployment descriptor. The last filter in this chain corresponds to the last
servlet-name matching filter and is the filter that invokes the target web resource.
� If there are filters using url-pattern matching and the url-pattern matches the
request URI according to the rules of SRV.11.2, the container builds the chain of
url-pattern matched filters in the same order as declared in the deployment
descriptor. The last filter in this chain is the last url-pattern matching filter in
the deployment descriptor for this request URI. The last filter in this chain is the
filter that invokes the first filter in the servlet-name macthing chain, or invokes
the target web resource if there are none.
-End quote
But if you use web.filter tag there is no way to declare which tag you want written
first.
It would be nice to have a way to order these. Probably impossible to do but nice to
have ;)
Only marked as an improvement cause it seems that this is more a spec issue. There
really should be a load type param that can be used to specify order or priority of a
filter.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://opensource.atlassian.com/projects/xdoclet/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
