You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Woonsan Ko (Updated) (JIRA)" <ji...@apache.org> on 2012/04/10 07:19:27 UTC
[jira] [Updated] (CAMEL-5155) Support JCR Component as Consumer
[ https://issues.apache.org/jira/browse/CAMEL-5155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Woonsan Ko updated CAMEL-5155:
------------------------------
Description:
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 an contribute a patch.
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.
was:
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.
> Support JCR Component as Consumer
> ---------------------------------
>
> Key: CAMEL-5155
> URL: https://issues.apache.org/jira/browse/CAMEL-5155
> 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 an contribute a patch.
> 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: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira