On Mon, Jul 20, 2009 at 05:35:46PM +0200, Alexander Klimetschek wrote:
>
> Of course, just use the JCR API in the esp. The post you mention
> already does it.
Indeed, I did not notice (I am in for the fun :). In fact,
# currentNode.checkin(); currentNode.checkout();
in an ESP does it all.
Thank
On Mon, Jul 20, 2009 at 12:51 PM, Peter Chiochetti wrote:
> There is a way to get the versions with ESP, see Bertrand Delacretaz' post
> here - http://markmail.org/message/dvr7kgvz5qhiqprm
>
> Is there also a way to create a revision with ESP, to call the jcr-api and
> do the checkin/checkout? (I'd
Thank you all,
There is a way to get the versions with ESP, see Bertrand Delacretaz'
post here - http://markmail.org/message/dvr7kgvz5qhiqprm
Is there also a way to create a revision with ESP, to call the jcr-api
and do the checkin/checkout? (I'd rather get by without writing a servlet.)
PS
In our case, we looked at something close to this and decided not to
do that for 2 reasons:
1. We wanted the save operation to appear in the http logs for audit
purposes.
2. The UI developers, who are the users in our case voted that *.save
was clearer than semantics within the POST paramet
hi,
i think the sling post servlet should leverage the content storage
metaphor as much as possible, i.e. controlling the versioning
operations with normal properties. eg: providing a
"jcr:isCheckedOut=true" ensures that the node is checked out,
providing a "jcr:isCheckedOut=false" ensures that th
I think this might be an excelent example project and could come along with
a detailed documentation to show several aspects of sling/JCR programming as
the mentioned use of selectors and versioning.
Best regards,
Dominik
On Sun, Jul 19, 2009 at 11:33 AM, Ian Boston wrote:
> We had the same use
We had the same use case, and so wrote a servlet to do this, using a
selector (*.save )
We also did *.versions to list versions ( with paging) and *.version
to get a specific version.
See [1]
Would be happy to bring this over to Sling *if* the team thought it
was a useful addition ?
Ian
On Fri, Jul 17, 2009 at 6:52 PM, Peter Chiochetti wrote:
> - If so, can I avoid replicating all of the used functionality
> of slingPostServlet?
>
> Is there a way to wrap it in ESP, so that it only has to
> "checkout(); processPostInServlet(); checkin()" or such?
It might make sense to add a c
On Tue, May 19, 2009 at 09:44:39PM +0100, Ian Boston wrote:
> AFACT, Sling by default does not perform check in's except in the
> content loader.
Its easy to add the versionable mixin with a POST:
$ curl -F"jcr:mixinTypes=mix:versionable" http://
and jackrabbit JCR seems to honor that (a node
