How about this for the feature request:
The chain will continue if the response is not committed, and the
Sling servlet is allowed to continue processing the POST. But if I
commit the response, the chain breaks, and processing stops.
Does this make sense? Basically, I want an ability to make changes to
my files before they are stored (and with this paradigm, I could
technically change anything).
Thoughts?
-Josh
On Oct 6, 2008, at 11:56 PM, Joshua Oransky wrote:
Because I want to keep all of my development inside of Sling.
Besides, I only want to process this on certain resourceTypes;
something that is already done by the whole Sling framework. In
fact, if storing files from a form was as easy as storing text info,
I wouldn't even need this... feature request?
-Josh
On Oct 6, 2008, at 1:29 PM, Dominique Jäggi wrote:
On Mon, Oct 6, 2008 at 8:27 PM, Joshua Oransky <[EMAIL PROTECTED]>
wrote:
Is this possible? Kind of like the Servlet Filter concept, where I
can
process some of the request than then pass it along.
why don't you just use filtering then? take a look at the
org.apache.sling.sample.filter.ZipFilter sample.
greetings,
dom.
-Josh
