Indeed, this looks good.
On 29.12.2007, at 20:59, Felix Meschberger wrote:
Hi all,
Scriptable Filters may be implemented based on my recent "Everything
is
a Resource" proposal. See [1]
Regards
Felix
[1]
http://cwiki.apache.org/SLING/everything-is-a-resource.html#Everythingi
Hi all,
Scriptable Filters may be implemented based on my recent "Everything is
a Resource" proposal. See [1]
Regards
Felix
[1]
http://cwiki.apache.org/SLING/everything-is-a-resource.html#EverythingisaResource-4.3Filters
Am Freitag, den 21.12.2007, 14:49 +0100 schrieb Lars Trieloff:
I think a servlet filter is more flexible than this proposed solution.
In a servlet filter you can modify the request and response before
calling the next component in the filter change, you can decide to call
the next in the chain and you can clean up or do some interesting stuff
when the next com
Hi Lars,
Am Freitag, den 21.12.2007, 16:26 +0100 schrieb Lars Trieloff:
> A typical servlet filter has following structure:
>
> - do something with the request
> - call doFilter(request, response);
> - do something with the response
I fear this does not work The request object has no setters
A typical servlet filter has following structure:
- do something with the request
- call doFilter(request, response);
- do something with the response
In most of these filters only the request or the response is modified.
With the separation of request.js and response.js I eliminate the
nece
Hi Lars,
Sounds simple and usefull.
Just one question: What is the difference betwen the Request filter and
the Response filter ?
And a clarification the script must/may wrap the request and response
objects to inject new data, or do you think that only parameters would
be "overwritten" ?
Regar
Lars,
good suggestion IMO.
re the resource filter scripts:
If the filter scripts reside in a different location than render scripts
anyway, why not apply the same naming schema as for render scripts? (
html.esp, POST.esp, etc)
re the default:
can we just call it "default.esp"?
Michael
--
Michae
Here is my proposal for scriptable filtering:
== Goal ==
We want to allow users with limited knowledge and interest in OSGi,
Maven and Java to create filters in a similar fashion to creating
scripts for request handling.
== Current Situation ==
Filters are OSGI components, implementing the
