Ah, ok. That makes sense.
thanks,
Rob
On Jul 22, 2012, at 3:26 PM, Sarwar Bhuiyan wrote:
> There should be a sling event already fired after your node is created.
> That is the application event they are referring to.
>
> Sarwar
>
> On Sunday, 22 July 2012, Robert A. Decker wrote:
>
>> Would
Hi Robert,
Once you save the Session, the saved nodes should be visible to other
Sessions. Is your job processor using a long-lived session? If so, try
calling refresh on the Session. This is especially true if you are using
some kind of clustering.
Regards,
Justin
On Jul 22, 2012 1:14 PM, "Robert
There should be a sling event already fired after your node is created.
That is the application event they are referring to.
Sarwar
On Sunday, 22 July 2012, Robert A. Decker wrote:
> Would that break the 'basic principles' as written here:
> http://sling.apache.org/site/eventing-and-jobs.html
>
Would that break the 'basic principles' as written here:
http://sling.apache.org/site/eventing-and-jobs.html
"The application should try to use application events instead of low level JCR
events whereever possible."
Is there a way to only receive node created events of a certain
sling:resourceT
Hi Robert,
You should also be able to setup a listener for the newly saved node and
use it to fire the job event.
-james.
On Sun, Jul 22, 2012 at 12:30 PM, Robert A. Decker wrote:
> Or should I fire off the job again?
>
> R
>
> On Jul 22, 2012, at 1:14 PM, Robert A. Decker wrote:
>
> > Hi,
> >
Or should I fire off the job again?
R
On Jul 22, 2012, at 1:14 PM, Robert A. Decker wrote:
> Hi,
>
> I create a node and save it, then fire off an event that starts a process
> that begins updating the node.
>
> However, there are times when the node hasn't been written by the first save
> y
