Another solution is to not rely on the Sling post servlet but write
special post scripts for the resource types you want to support.
Btw, I still think that we need something in this area - along with
better validation. I started a prototype long time ago, but never got
it to a point to share it.
Bhathiya,
Think of Sling as an HTTP interface to the underlying JCR store (jackrabbit).
It is possible to manipulate nodes inside the JCR outside of the HTTP
request cycle (outside of servlets).
At that point you're just coding OSGi classes.
Sling runs in an OSGi container so you'd most likely ma
Hi,
On Jun 11, 2012, at 1:04 PM, Felix Meschberger wrote:
> Hi,
>
> Am 11.06.2012 um 09:03 schrieb Davide:
>
>> (please note the quotes around securing).
>>
>> I really love the SlingPostServlet and the fact that I can create JCR
>> structure starting from a JSON stream. It really ease the pr
Hi,
Am 11.06.2012 um 09:03 schrieb Davide:
> (please note the quotes around securing).
>
> I really love the SlingPostServlet and the fact that I can create JCR
> structure starting from a JSON stream. It really ease the process for
> creating (and updating?) content.
>
> Now if I'd go for the
(please note the quotes around securing).
I really love the SlingPostServlet and the fact that I can create JCR
structure starting from a JSON stream. It really ease the process for
creating (and updating?) content.
Now if I'd go for the usage of it, I'd like to prevent some malicious
teenager to
