camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bilgin Ibryam (JIRA)" <>
Subject [jira] [Commented] (CAMEL-5155) Support JCR Component as Consumer
Date Wed, 25 Apr 2012 10:00:02 GMT


Bilgin Ibryam commented on CAMEL-5155:

You documented pretty well the java classes, I will add them to the wiki. The latest jcr code
is in trunk, have a look here

I was thinking how this jcr consumer would be helpful, and once you got a list of jcr Event,
and for example if it is an update/add operation, the next thing user wants to do would be
to retrieve this node from jcr in order to do some action with it. So I think extending the
jcr producer with ability to read nodes by a given id/path from the event might be helpful.

Also are you using currently the Consumer, I wonder what is your use case to listen only for
events, w/o retrieving the actual nodes?
> Support JCR Component as Consumer
> ---------------------------------
>                 Key: CAMEL-5155
>                 URL:
>             Project: Camel
>          Issue Type: New Feature
>          Components: camel-jcr
>    Affects Versions: 2.9.1
>            Reporter: Woonsan Ko
>            Assignee: Bilgin Ibryam
>             Fix For: 2.10.0
>         Attachments: jcr-consumer-patch-2.txt, jcr-consumer-patch.txt
> 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:!default.jspa
For more information on JIRA, see:


View raw message