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:resourceType? Or will all node creation events come to my handler?

R


On Jul 22, 2012, at 1:59 PM, James Stansell wrote:

> 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,
>>> 
>>> 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 yet, and so my job processor has nothing to work on.
>>> 
>>> Is the correct strategy to have the job processor wait a few
>> milliseconds and try again? and again and again…?
>>> 
>>> 
>>> Rob
>> 
>> 

Reply via email to