i've managed to integrate ldap with AEM and am able to sync individual
users using the syncUser call in the com.adobe.granite.ldap (Tools) jmx
page. I would like to make use of the syncUserList call to sync more
than one user lists. Whats the format of the input i should give in for
this? Form the error.log it looks like it's expecting a json input,
however i'm not sure what's the exact format. I couldn't find any
documentation for this as well.Also i went thorugh the post @
Hi Jörg,The below are the sample queries that we make use of:SQL -
SELECT * FROM CUSTOMNODETYPE WHERE jcr:path like
'/content/foo/bar/%/level1/level2/%' and cq:propName='val'SQL2 - SELECT
* FROM [CUSTOMNODETYPE] as t where
t.isModified=CAST('true' AS BOOLEAN)I went through your post and for our
large repository and for the use cases where the data needs to be
obtained from a considerable large subtree, i believe we should be using
jcr search us...
i went through the jira page, but wasn't this fixed in the 2.3.0 version
of apache jackrabbit? Looking at my system/console/bundles page, CQ
5.6.1 uses 2.6.2 version of apache jakrabbit api.Also i tried the
equivalent query with the SQL version (using jcr:path LIKE constraint)
and that too took about the same time.
We have a pretty big repository and i'm trying to perform the following
SQL2 query which takes around 30 seconds to execute.Query -SELECT * FROM
[CUSTOMNODETYPE] as t where
t.isModified=CAST('true' AS BOOLEAN)I enabled the debug logs for the
package org.apache.jackrabbit.core.query and am attaching the log
messages..Going through the logs the below message seems
suspicious:17.10.2014 01:43:18.049 *DEBUG* [10.239.60.171
I figured this issue out after banging my head for hours. I did not give
the DELETE permissions (to the /etc/workflow/instances) for the user
with which i started the workflow and moved the workflow to the next
step. Once i gave this it started workingThanks for your help on this.
I'm also looking at using the workflow java API's to move/start the
workflows. However using the API's i'm facing some strange behaviour.
Please find attached the WorkflowManager class that i make use of.I'm
using a 5 participant step workflow model. I first start the workflow
using the startWorkflow method there.This start the workflow and creates
the node at etc/workflow/instances/ folder, something like
/etc/workflow/instances/2014-01-13/model_459346895847903. Under this i
get the workitems, ...
Thanks for you reply.Are you suggesting to clone the node or the ACP's?
I did try copying the source node but that didnt carry over the ACP's.
Basically they sit under the node rep:policy and while debugging those
nodes were protected i think (sourceNode.getDefinition().isProtected())
and hence dont copy overIs there a way i can create freshly create the
policies, i basically want to give READ, WRITE, MODIFY, CREATE to the
specific targetNode, this needs to be give to all the groups the user