No, what I need is a way of processing those files before they are
written. My use case is that I want users to upload a single large
image, and process it with an image lib to generate thumbnails, etc.
But I don't want to have to write all the code to ALSO persist the
text data, like image description, etc...
So what I want, is a way to handle storing of the files separately,
but leave the text data to the Sling servlet. Of course, one could
also intercept some of the text data as well. The point is how do I
write code to only worry about the stuff I need, and let Sling persist
anything else normally.
-Josh
On Oct 13, 2008, at 1:52 AM, Bertrand Delacretaz wrote:
On Tue, Oct 7, 2008 at 8:56 AM, Joshua Oransky <[EMAIL PROTECTED]>
wrote:
...In fact, if storing files from a
form was as easy as storing text info, I wouldn't even need this...
feature
request?...
I'm not sure if I understand the problem - if you use a form like
<form action="/content/foo/*" method="POST" enctype="multipart/form-
data">
<input type="file" name="attachments/*"/>
<input type="submit"/>
</form>
the data is uploaded as a file under an "attachments" child node of
the created node. Isn't that what you need?
The SLING-673 blog sample uses this.
-Bertrand
