mmjose26 wrote: > > It works, but is an ugly loop code and maybe I'm ignoring the right way to > solve this. >
Depending on what you're trying to do a JCR Observer may help. You can register one as an async operation after a node has been created. If you do end up having to use that loop I would put in a Thread.sleep(100) or something. -- View this message in context: http://jackrabbit.510166.n4.nabble.com/Remote-Access-by-DavEx-tp3811610p3813881.html Sent from the Jackrabbit - Users mailing list archive at Nabble.com.
