sure. I created this ticket. https://issues.apache.org/activemq/browse/CAMEL-2603
Claus Ibsen-2 wrote: > > On Tue, Mar 30, 2010 at 3:25 PM, anandsk <[email protected]> wrote: >> >> yes, I have seen the consumer. it may be useful in some scenarios to have >> it >> as a consumer. Typlical use of cache is to read and do something as shown >> below. yes, there needs to be a get operation also. >> > > Could you create a ticket in JIRA for this new GET operation? > > >> ex: .process(new Processor() { >> public void process(Exchange exchange) throws >> Exception { >> String payload = >> exchange.getIn().getBody(String.class); >> // do something with the payload and/or >> exchange here >> >> // read cache >> //do something >> exchange.getIn().setBody(payload); >> }}) >> >> Claus Ibsen-2 wrote: >>> >>> Hi >>> >>> The cache read is from the consumer side, but it acts as an event >>> driven consumer. >>> I think we should have GET added as a new operation on the producer >>> side as well. >>> >>> Ashwin Karpe created this component maybe he can shed some lights as >>> well? >>> >>> If not then I think you should create a ticket in JIRA for this >>> improvement. >>> >>> >>> On Mon, Mar 29, 2010 at 7:56 PM, anandsk <[email protected]> wrote: >>>> >>>> I checked unit tests, I haven't seen any examples for getting or >>>> reading >>>> cached content. all I see is only these operations >>>> ADD/UPDATE/DELETE/DELETEALL , there is no get/read operation. is get >>>> not >>>> supported. >>>> >>>> Claus Ibsen-2 wrote: >>>>> >>>>> Hi >>>>> >>>>> Check the unit tests of camel-test to see some examples. >>>>> >>>>> There are special headers you can use to control the cache to DELETE >>>>> etc. >>>>> >>>>> On Mon, Mar 29, 2010 at 6:18 PM, anandsk <[email protected]> wrote: >>>>>> >>>>>> >>>>>> I have read the documentation of cache component. my requirement is >>>>>> to >>>>>> add a >>>>>> cache entry in a processor after I receive JMS message and >>>>>> access/read >>>>>> the >>>>>> cache in a seperate route and delete it. How do I do this with Camel >>>>>> cache. >>>>>> -- >>>>>> View this message in context: >>>>>> http://old.nabble.com/read-from-cache-component-tp28071593p28071593.html >>>>>> Sent from the Camel - Users mailing list archive at Nabble.com. >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> Claus Ibsen >>>>> Apache Camel Committer >>>>> >>>>> Author of Camel in Action: http://www.manning.com/ibsen/ >>>>> Open Source Integration: http://fusesource.com >>>>> Blog: http://davsclaus.blogspot.com/ >>>>> Twitter: http://twitter.com/davsclaus >>>>> >>>>> >>>> >>>> -- >>>> View this message in context: >>>> http://old.nabble.com/read-from-cache-component-tp28071593p28072821.html >>>> Sent from the Camel - Users mailing list archive at Nabble.com. >>>> >>>> >>> >>> >>> >>> -- >>> Claus Ibsen >>> Apache Camel Committer >>> >>> Author of Camel in Action: http://www.manning.com/ibsen/ >>> Open Source Integration: http://fusesource.com >>> Blog: http://davsclaus.blogspot.com/ >>> Twitter: http://twitter.com/davsclaus >>> >>> >> >> -- >> View this message in context: >> http://old.nabble.com/read-from-cache-component-tp28071593p28082500.html >> Sent from the Camel - Users mailing list archive at Nabble.com. >> >> > > > > -- > Claus Ibsen > Apache Camel Committer > > Author of Camel in Action: http://www.manning.com/ibsen/ > Open Source Integration: http://fusesource.com > Blog: http://davsclaus.blogspot.com/ > Twitter: http://twitter.com/davsclaus > > -- View this message in context: http://old.nabble.com/read-from-cache-component-tp28071593p28084991.html Sent from the Camel - Users mailing list archive at Nabble.com.
