...but I breaked your deployment descriptorz.
Seriously, I have bee playing around with PostReplaceFilter and added two new
ways to specify the replacement method, either as a form parameter _method in
the body of the post, or as an URI parameter of the same name. If the replacement
method is GET, form parameters in the body are appended to the URI (im I correct
in assuming that I don't have to do anything special to @QueryParam processing
here?), and a text/plain body is appended as further components to the request
path (this seems to be the behaviour for _method described by Richardson and Ruby).
This may also fix bug #166.
PostReplaceFilter became abstract along the way, so people using it must change
theitr deployment descriptors to use PostReplaceHeaderFilter instead.
Does the code look OK? I have thrown some test cases at it but not really done
anything serious with it yet.
- Florian.