And why is it that a servlet filter is outside the application? I
consider it to be part of the application; it is simply a matter that
those services are not provided directly by the framework used to
implement the logic.
Otherwise each framework would have to provide that capability.
I
My filter handle the rewrite and parameter parsing, and dispatch to
according controller/action with a wrapped http request.
1. user hit the url: /user/1354
2. filter knows that user request the
UserController/UserServlet/UserAction/view-user.jsp with a param value 1354
(corresponding param
you can use express-wind to build rest url like /user/1234
http://code.google.com/p/express-me/wiki/ExpressWind
It uses Filter or Servlet to handle all requests and match your rest url like:
@Mapping(/user/$1)
public void displayUser(int id) {
...
}
If you already have a struts / spring mvc
I've read the description of ExpressWind, it seems really nice.
Thanks.
Michael Liao wrote:
you can use express-wind to build rest url like /user/1234
http://code.google.com/p/express-me/wiki/ExpressWind
It uses Filter or Servlet to handle all requests and match your rest url like:
Hello
I didn't have yet the opportunity to work with search engine friendly
urls with resin (I did it with apache/php). I suppose that there must be
a set of servlet-mapping and rewrite-dispatch in conf and some
url-dedicated servlets in the application.
I wonder if there is any kind of good
You may use http://tuckey.org/urlrewrite/ UrlRewriteFilter.
I wrote a similar filter doing the same thing which loads rewrite config
from database.
2009/10/30 Riccardo Cohen r...@architectedulogiciel.fr
Hello
I didn't have yet the opportunity to work with search engine friendly
urls with
Thanks Wesley I'll try to use filter.
Now in term of performance, isn't it better to integrate the url
processing directly into the controller servlet ?
Wesley Wu wrote:
You may use http://tuckey.org/urlrewrite/ UrlRewriteFilter.
I wrote a similar filter doing the same thing which loads
I understand your point of view : separate url management and
application logic. It seems a good practice.
In the same time this probably comes from the idea that search engine
friendly urls are added to the application, which basically does not
need it.
On one hand it is true. The url
