[
https://issues.jboss.org/browse/SEAMSERVLET-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Allen updated SEAMSERVLET-17:
---------------------------------
Fix Version/s: 3.0.1.Beta1
(was: 3.0.0.Final)
> Utility for resolving Servlet for path
> --------------------------------------
>
> Key: SEAMSERVLET-17
> URL: https://issues.jboss.org/browse/SEAMSERVLET-17
> Project: Seam Servlet
> Issue Type: Feature Request
> Components: Utilities
> Affects Versions: 3.0.0.Alpha1
> Reporter: Dan Allen
> Priority: Minor
> Fix For: 3.0.1.Beta1
>
>
> One area where the Servlet API is very stingy about information is
> determining which Servlet is going to handle a servlet path. This mapping is
> calculated countless times inside of Servlet containers, yet the utility is
> not exposed. Let's expose the logic of mapping requests to Servlets. See
> chapter 12 of the Servlet specification
> (http://jcp.org/aboutJava/communityprocess/final/jsr315/index.html)
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
