camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Woonsan Ko (Commented) (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5155) Support JCR Component as Consumer
Date Tue, 10 Apr 2012 05:17:39 GMT


Woonsan Ko commented on CAMEL-5155:

Claus Ibsen:
This sounds like a really good idea.

We love contributions, and would look very much forward to your help
with this component.

I like the fact if the uri can be the same / almost the same.

Also when registering listeners in JCR, then remember to cleanup when
the JcrConsumer stops, in the doStop method.
There should be some API in JCR to unregister the listener as well.

"Thank you very much for the valuable input!
Yes, JCR has an API to unregister listener, so I will need to do proper clean ups.
I'll keep you updated."
> Support JCR Component as Consumer
> ---------------------------------
>                 Key: CAMEL-5155
>                 URL:
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-jcr
>    Affects Versions: 2.9.1
>            Reporter: Woonsan Ko
>             Fix For: 2.10.0, 2.9.2
> I tried to use jcr component as consumer, expecting jcr observation event listener like
behavior, but I realized that it's not supported yet. The current jcr component supports producer
only. So, I'm considering to implement JcrConsumer and possibly contribute it in a new CAMEL
JIRA issue later. 
> My idea is as follows:
> i) the uri format is the same. e.g. 'jcr://user:password@repository/absolute/path/from/node';
the node path is used for javax.jcr.observation.ObservationManager#addEventListener(..., absPath,
> ii) additionally, we need parameters for eventTypes, isDeep, uuid[], nodeTypeName[],
noLocal parameters (See #addEventListener() for detail).
>     For example, we may probably use somethings like 'jcr://user:password@repository/absolute/path/from/node?nodeTypeName=demo:news&eventTypes=3&isDeep=true.
> iii) JcrConsumer registers JCR observation event listener from the specified uri information.
> iv) When events notified, I think it can simply return a list of javax.jcr.observation.Event
objects in IN message.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message