Nabble - Camel - Users

Re: Accessing exchange from producer template

2009-12-08T21:57:04Z

On Wed, Dec 9, 2009 at 4:07 AM, trivedi kumar b
<Trivedi.Bodlapati@...> wrote:
>
> Hi,
>
> I have a bean that is being invoked from a route and this bean has got
> producer template.. and I want the access to exchange object to retrieve
> properties that is being set before in the route. So I have written a small
> piece of code (method) that returns me the exchange object.. pls let me know
> if there is a better to get the exchange object.
>

Hi

You want to get those properties in the bean, and before you use the
producer template?

You can use bean parameter binding
http://camel.apache.org/parameter-binding-annotations.html

public void myMethod(String body, @Properties Map properties);

Or just add Exchange as a parameter to your bean.

public void myMethod(String body, Exchange exchange);

PS: Chapter 4 in Camel in Action covers using beans in great details

> private Exchange getExchange() {
> Exchange exchange = template.send(new Processor() {
> public void process(Exchange arg0) throws Exception { }
> });
> return exchange;
> }
> --
> View this message in context: http://old.nabble.com/Accessing-exchange-from-producer-template-tp26704478p26704478.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

Re: handled exception in sub-route

2009-12-08T21:44:21Z

On Mon, Dec 7, 2009 at 1:19 PM, trivedi kumar b
<Trivedi.Bodlapati@...> wrote:

>
> Hi,
>
> Eventhough I use doTry().. doCatch() blocks to handle the issue that Jens
> explained before, the problem is still exists, this is how my route looks
> like in which the call never goes to "direct:C" when there is an exception
> in sub-route "B":
> from("direct:A")
> .to("direct:B")
> .to("direct:C");
>
> from("direct:B")
> .doTry()
> .transacted().end()
> .code goes that throws an exception
> .doCatch(Exception.class)
> .handled(true)
> .markRollbackOnly()
> .end();
>
> from("direct:C")
> .....
>

Hi

I have just added an unit test to Camel trunk
http://svn.apache.org/viewvc?rev=888706&view=rev

And try .. catch works as expected where it continues to route.
Can you at try with Camel 2.1 as it have many improvements and fixes over 2.0.

>
> Claus Ibsen-2 wrote:
>>
>> On Sun, Dec 6, 2009 at 11:25 PM, trivedi kumar b
>> <Trivedi.Bodlapati@...> wrote:
>>>
>>> Hi,
>>>
>>> If I use doTry.. doCatch, with similar route that includes transactions,
>>> will that work as expected? I mean, markRollbackOnly() option inside
>>> doCatch() will rollback the transaction? Pls let me know the behaviour.
>>>
>>
>> Yes markRollbackOnly() is only for transactions and will issue a
>> status.setRollbackOnly() on the Spring Transaction underneath.
>> That should render the transaction outcome as rollback only.
>>
>> It will not tamper with the Exchange by setting an exception as
>> rollback() does by setting a RollbackException on the Exchange.
>>
>>
>>
>>
>>
>>> Thanks,
>>> Trivedi
>>>
>>>
>>> Claus Ibsen-2 wrote:
>>>>
>>>> On Thu, Dec 3, 2009 at 10:45 AM, kyt <kythary@...> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> I need some advice on how to handle an exception in a sub-route and how
>>>>> the
>>>>> calling route can continue processing. It is easier to explain this
>>>>> with
>>>>> a
>>>>> bit of code:
>>>>>
>>>>> from("direct:A")
>>>>> .to("direct:B")
>>>>> .to("direct:C");
>>>>>
>>>>> from("direct:B")
>>>>> .onException(Exception.class).handled(true).end()
>>>>> . code that throws an exception
>>>>>
>>>>> from("direct:C")
>>>>> ...
>>>>>
>>>>> Now, if there is an exception in direct:B, direct:C never gets called.
>>>>> Through debugging I found out that the pipeline in direct:A stops
>>>>> processing
>>>>> because it checks an exchange property (Exchange.ERRORHANDLER_HANDLED).
>>>>> I'm
>>>>> using Camel 2.0. Is there a way that the processing in direct:A
>>>>> continues
>>>>> after the exception was handled in direct:B?
>>>>>
>>>>
>>>> Unfortunately the logic for error handling got a bit complex.
>>>> Something to improve in 2.2. I am currently making the TX based
>>>> simpler in internal logic.
>>>>
>>>> Back to your use case.
>>>> The doTry .. doCatch will work as regular try .. catch and thus what
>>>> you would expect so route A will continue
>>>>
>>>> In terms on onException we should improve this over time, adding some
>>>> flag to indicate what you want. As some want to use onException to
>>>> catch that error and create a custom error messages as reply and thus
>>>> not process and further. And others as you want a kinda try .. catch
>>>> logic and just ignore the damn exception.
>>>>
>>>>
>>>>> Thanks,
>>>>> Jens
>>>>> --
>>>>> View this message in context:
>>>>> http://old.nabble.com/handled-exception-in-sub-route-tp26623326p26623326.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/handled-exception-in-sub-route-tp26623326p26669550.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/handled-exception-in-sub-route-tp26623326p26676468.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>

Re: Implementing Publish Subscribe Channel

2009-12-08T21:27:23Z

Hi Hendry

I am a bit busy over the next week or so, due to new book deadline and
a other engagements.

However I haven't forgotten about this use-case and I think we can
improve the seda component
to let it support multiple consumers by sending a copy of the exchange
to each recipient.

Then you should be able to use it as a event broadcaster kinda thingy.

Fell free to create a ticket in JIRA

On Sun, Dec 6, 2009 at 6:50 PM, Hendy Irawan <hendy@...> wrote:

>
> Hi Claus,
>
>
> Claus Ibsen-2 wrote:
>>
>> No seda does *not* support multiple consumers. Its meant to be used
>> with a single consumer only.
>> In 2.1 this is even enforced. Often end users had copy paste mistakes
>> and didnt want multiple consumers to the same seda endpoint.
>> Hence why we enforced this now in 2.1.
>>
>> What is your use case sine you need this? I am interesting in what you
>> are trying to solve?
>>
>>
>> What you could do is to extend seda, and have support multiple
>> consumers and have the Exchange being copied before its handed out to
>> every
>> consumers.
>>
>> Mind that when you copy the Exchange / Message if the body is not a
>> simple type such as String then you may only copy a reference to it
>> and thus have multiple consumers work on it concurrently, and thus you
>> need to be aware of thread safety issues.
>>
>> And there is a new interface in Camel 2.1, MultipleConsumersSupport,
>> which indicates whether an endpoint supports multiple consumers or
>> not.
>> You need to implement this and return true in your own component.
>>
>
> I'm not sure if a separate component is needed for this, because from my
> experience the <multicast> element works fine. And that's what I'm trying to
> get, using the <multicast> functionality in a @Consume'r.
>
> Maybe something like this (proposal):
>
> @Consume(uri="someuri", multicast=true)
>
> My use case is using Camel as event publisher. Exactly like Spring
> Application Events.
>
> @EndpointInject(uri="seda:events.form")
> ProducerTemplate formEvents;
>
> ...
> formEvents.sendBody(new FormEvent(...));
> ...
>
> then there are one or more event Listeners like this:
>
> @Consume(uri="seda:events.form")
> public void handleFormEvent(FormEvent event) { ... }
>
> BTW, the producer and consumer URI may not be the same. i.e. the publisher
> of the event may route it in some way and there may be multiple producers.
> However as far as consumers are concerned, they have this inbox URI (e.g.
> "seda:events.form") that all events will come together. Then multiple
> consumers can process the messages (it's InOnly, no need to reply).
>
> I can do this with <multicast>, but my "problem" is that I want it to be
> "dynamic" i.e. just @Consume annotation is needed, no change in routes.
> Because the consumers can be created and disposed dynamically.
> --
> View this message in context: http://old.nabble.com/Implementing-Publish-Subscribe-Channel-tp26654086p26667205.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>

Re: Is camel the right choice for me?

2009-12-08T19:59:29Z

I'm a very new user of Camel, so take that for what it is worth. I
started off using Mule and became disenchanted by it very quickly
(especially when trying to troubleshoot an issue I had with it). It
felt like overkill for what I needed. I was quite pleased by my
attempts with a few test cases in Camel. It was cleaner, more
lightweight and really felt like it was working with me, rather than
trying to push me into its idioms. I've been very happy with it so
far.

Let me throw in one other *huge* plus for using Camel. I have rarely
worked with a more helpful community than the Camel folks. Claus and
Willem and Charles have been hugely helpful for me and I'm pretty sure
they are not real people, but teams of developers answering questions
24/7/364 (they can have New Year's Day off). I'm feeling very
comfortable with my choice to use Camel.

To your specific issues, I'll let Clauemles answer.

--Tim

On Tue, Dec 8, 2009 at 6:22 PM, pangea <yaravind@...> wrote:

>
> Helo all -
>
> we have a home grown communication framework (based on other open source
> components like apache commons, axis etc) that we have been using so far. It
> works great but
>
> - It has many limitations like no connection pooling,
> - only supports tcp/ip, http(s), soap (Axis 1.4 only), and JDBC (hibernate
> 2.1.8)
> - we doesnt want to maintain it anymore
>
> I am looking into replacing it with open source framework. I like the DSL
> based approach of Camel and seems like its lightweight unlike Mule and
> others. Appreciate if someone can let me know if camel supports the below
> usecases. Thank you in advance
>
> MUST
>
> 1) I should be able to configure/set all the protocol level properties (for
> e.g. in case of http custom headers, keep-alive, GET or POST etc, for tcp-ip
> - so_linger etc) thru configuration and also runtime from code.
>
> 2) Ability to pool the connections
>
> 3) Ability to configure multiple URLs for a given endpoint. Our partners
> expose multiple URLs each for DEV, TEST, QA, PROD etc. Idea is to configure
> all the URLs for these different regions during development and choose which
> one to use while deployment.
>
> 4) Ability to expose all the protocol aspects so that we can modify if
> required
>
> 5) Support for REST
>
> 6) Support for SOAP (ability to choose Axis or CXF or others)
>
> 7) Proxy configuration, NTLM auth for HTTP
>
> 8) Re-try strategies
>
> 9) Performant
>
> NICE TO HAVE
>
> 1) Support for polling
>
> 2) Client certs (keystore) support
> --
> View this message in context: http://old.nabble.com/Is-camel-the-right-choice-for-me--tp26704160p26704160.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>

Accessing exchange from producer template

2009-12-08T19:07:20Z

Hi,

I have a bean that is being invoked from a route and this bean has got producer template.. and I want the access to exchange object to retrieve properties that is being set before in the route. So I have written a small piece of code (method) that returns me the exchange object.. pls let me know if there is a better to get the exchange object.

private Exchange getExchange() {
Exchange exchange = template.send(new Processor() {
public void process(Exchange arg0) throws Exception { }
});
return exchange;
}

Is camel the right choice for me?

2009-12-08T18:22:39Z

Helo all -

we have a home grown communication framework (based on other open source components like apache commons, axis etc) that we have been using so far. It works great but

- It has many limitations like no connection pooling,
- only supports tcp/ip, http(s), soap (Axis 1.4 only), and JDBC (hibernate 2.1.8)
- we doesnt want to maintain it anymore

I am looking into replacing it with open source framework. I like the DSL based approach of Camel and seems like its lightweight unlike Mule and others. Appreciate if someone can let me know if camel supports the below usecases. Thank you in advance

MUST

1) I should be able to configure/set all the protocol level properties (for e.g. in case of http custom headers, keep-alive, GET or POST etc, for tcp-ip - so_linger etc) thru configuration and also runtime from code.

2) Ability to pool the connections

3) Ability to configure multiple URLs for a given endpoint. Our partners expose multiple URLs each for DEV, TEST, QA, PROD etc. Idea is to configure all the URLs for these different regions during development and choose which one to use while deployment.

4) Ability to expose all the protocol aspects so that we can modify if required

5) Support for REST

6) Support for SOAP (ability to choose Axis or CXF or others)

7) Proxy configuration, NTLM auth for HTTP

8) Re-try strategies

9) Performant

NICE TO HAVE

1) Support for polling

2) Client certs (keystore) support

camel-bam (Hibernate vs Openjpa)

2009-12-08T08:30:49Z

JPA implementation is radically different between Hibernate and openjpa.

Here is a snapshot of what happens in the transaction who will save the
ProcessDefinition

protected ProcessDefinition findOrCreateProcessDefinition() {
Map<String, Object> params = new HashMap<String, Object>(1);
params.put("name", processName);

List<ProcessDefinition> list =
CastUtils.cast(jpaTemplate.findByNamedParams("select x from "
+ ProcessDefinition.class.getName() + " x where x.name = :name",
params));
if (!list.isEmpty()) {
LOG.info(">> list not empty - Definition : " +
list.get(0).toString() + ", name : " + list.get(0).getName() + ", id : " +
list.get(0).getId());
return list.get(0);
} else {
ProcessDefinition answer = new ProcessDefinition();
answer.setName(processName);
LOG.info(">> before persist Definition : " + answer.toString() +
", name : " + answer.getName() + ", id : " + answer.getId());
jpaTemplate.persist(answer);

list = CastUtils.cast(jpaTemplate.find("select p from " +
ProcessDefinition.class.getName() +" p "));
LOG.info(">> Definition name : " + list.get(0).getName() + ", id
: " + list.get(0).getId());
LOG.info(">> after persist Definition : ");
return answer;
}
}

1) openjpa

2009-12-08 17:24:43,168 [main ] INFO
ProcessBuilder - >> before persist Definition :
org.apache.camel.bam.model.ProcessDefinition[null], name : Process-1, id :
null
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
JpaTransactionManager - Initiating transaction commit
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
JpaTransactionManager - Committing JPA transaction on EntityManager
[org.apache.openjpa.persistence.EntityManagerImpl@6ffd79]
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
JpaTransactionManager - Closing JPA EntityManager
[org.apache.openjpa.persistence.EntityManagerImpl@6ffd79] after transaction
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
EntityManagerFactoryUtils - Closing JPA EntityManager
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
JpaTransactionManager - Creating new transaction with name [null]:
PROPAGATION_REQUIRED,ISOLATION_DEFAULT
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
JpaTransactionManager - Opened new EntityManager
[org.apache.openjpa.persistence.EntityManagerImpl@f38cf0] for JPA
transaction
2009-12-08 17:24:43,184 [tyMonitorEngine] TRACE
SQL - <t 15040737, conn 23149395> executing
prepstmnt 31361704 SELECT t0.id, t0.ACTIVITYDEFINITION_ID,
t0.escalationLevel, t0.PROCESSINSTANCE_CORRELATIONKEY,
t0.receivedMessageCount, t0.timeExpected, t0.timeOverdue FROM
CAMEL_ACTIVITYSTATE t0 WHERE (t0.timeOverdue < ?) [params=(Time) 17:24:43]
2009-12-08 17:24:43,184 [tyMonitorEngine] TRACE
SQL - <t 15040737, conn 23149395> [0 ms] spent
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
JpaTransactionManager - Initiating transaction commit
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
JpaTransactionManager - Committing JPA transaction on EntityManager
[org.apache.openjpa.persistence.EntityManagerImpl@f38cf0]
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
JpaTransactionManager - Closing JPA EntityManager
[org.apache.openjpa.persistence.EntityManagerImpl@f38cf0] after transaction
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
EntityManagerFactoryUtils - Closing JPA EntityManager
2009-12-08 17:24:43,184 [tyMonitorEngine] DEBUG
ActivityMonitorEngine - Sleeping for 1000 millis
2009-12-08 17:24:43,246 [main ] TRACE
Runtime - Updating sequence values.
2009-12-08 17:24:43,246 [main ] TRACE
Runtime - Getting current sequence values.
2009-12-08 17:24:43,246 [main ] TRACE
SQL - <t 14043096, conn 16703414> executing
prepstmnt 4123674 SELECT SEQUENCE_VALUE FROM OPENJPA_SEQUENCE_TABLE WHERE ID
= ? [params=(int) 0]
2009-12-08 17:24:43,246 [main ] TRACE
SQL - <t 14043096, conn 16703414> [0 ms] spent
2009-12-08 17:24:43,246 [main ] TRACE
Runtime - Inserting row for this mapping into
sequence table.
2009-12-08 17:24:43,246 [main ] TRACE
SQL - <t 14043096, conn 32633742> executing
prepstmnt 17912146 INSERT INTO OPENJPA_SEQUENCE_TABLE (ID, SEQUENCE_VALUE)
VALUES (?, ?) [params=(int) 0, (int) 1]
2009-12-08 17:24:43,246 [main ] TRACE
SQL - <t 14043096, conn 32633742> [0 ms] spent
2009-12-08 17:24:43,246 [main ] TRACE
Runtime - Updating sequence values.
2009-12-08 17:24:43,246 [main ] TRACE
Runtime - Getting current sequence values.
2009-12-08 17:24:43,246 [main ] TRACE
SQL - <t 14043096, conn 16183734> executing
prepstmnt 28117049 SELECT SEQUENCE_VALUE FROM OPENJPA_SEQUENCE_TABLE WHERE
ID = ? [params=(int) 0]
2009-12-08 17:24:43,246 [main ] TRACE
SQL - <t 14043096, conn 16183734> [0 ms] spent
2009-12-08 17:24:43,246 [main ] TRACE
SQL - <t 14043096, conn 16183734> executing
prepstmnt 7806641 UPDATE OPENJPA_SEQUENCE_TABLE SET SEQUENCE_VALUE = ? WHERE
ID = ? AND SEQUENCE_VALUE = ? [params=(long) 51, (int) 0, (long) 1]
2009-12-08 17:24:43,262 [main ] TRACE
SQL - <t 14043096, conn 16183734> [16 ms] spent
2009-12-08 17:24:43,278 [main ] TRACE
SQL - <t 14043096, conn 31352855> executing
prepstmnt 1732792 INSERT INTO CAMEL_PROCESSDEFINITION (id, name) VALUES (?,
?) [params=(long) 1, (null) null]
2009-12-08 17:24:43,278 [main ] TRACE
SQL - <t 14043096, conn 31352855> [0 ms] spent
2009-12-08 17:24:43,278 [main ] TRACE
SQL - <t 14043096, conn 31352855> executing
prepstmnt 13969258 SELECT t0.id, t0.name FROM CAMEL_PROCESSDEFINITION t0
2009-12-08 17:24:43,278 [main ] TRACE
SQL - <t 14043096, conn 31352855> [0 ms] spent
2009-12-08 17:24:43,278 [main ] DEBUG
TransactionTemplate - Initiating transaction rollback on
application exception
java.lang.NullPointerException
at
org.apache.openjpa.kernel.StateManagerImpl.beforeRead(StateManagerImpl.java:939)
at
org.apache.openjpa.kernel.StateManagerImpl.accessingField(StateManagerImpl.java:1479)
at
org.apache.camel.bam.model.ProcessDefinition.getName(ProcessDefinition.java)
at
org.apache.camel.bam.ProcessBuilder.findOrCreateProcessDefinition(ProcessBuilder.java:216)
at
org.apache.camel.bam.ProcessBuilder.getProcessDefinition(ProcessBuilder.java:145)
at
org.apache.camel.bam.ProcessBuilder$1.doInTransactionWithoutResult(ProcessBuilder.java:103)
at
org.springframework.transaction.support.TransactionCallbackWithoutResult.doInTransaction(TransactionCallbackWithoutResult.java:33)
at
org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:128)

2) Hibernate

2009-12-08 17:19:18,496 [main ] INFO
ProcessBuilder - >> before persist Definition :
org.apache.camel.bam.model.ProcessDefinition[null], name : Process-1, id :
null
2009-12-08 17:19:18,496 [tyMonitorEngine] DEBUG
JpaTransactionManager - Creating new transaction with name [null]:
PROPAGATION_REQUIRED,ISOLATION_DEFAULT
2009-12-08 17:19:18,496 [tyMonitorEngine] DEBUG
JpaTransactionManager - Opened new EntityManager
[org.hibernate.ejb.EntityManagerImpl@120cb3] for JPA transaction
2009-12-08 17:19:18,512 [tyMonitorEngine] DEBUG
JpaTransactionManager - Initiating transaction commit
2009-12-08 17:19:18,512 [tyMonitorEngine] DEBUG
JpaTransactionManager - Committing JPA transaction on EntityManager
[org.hibernate.ejb.EntityManagerImpl@120cb3]
2009-12-08 17:19:18,512 [tyMonitorEngine] DEBUG
JpaTransactionManager - Closing JPA EntityManager
[org.hibernate.ejb.EntityManagerImpl@120cb3] after transaction
2009-12-08 17:19:18,512 [tyMonitorEngine] DEBUG
EntityManagerFactoryUtils - Closing JPA EntityManager
2009-12-08 17:19:18,512 [tyMonitorEngine] DEBUG
ActivityMonitorEngine - Sleeping for 984 millis
2009-12-08 17:19:18,684 [main ] INFO
ProcessBuilder - >> after persist Definition :

2009-12-08 17:22:22,293 [main ] INFO
ProcessBuilder - >> before persist Definition :
org.apache.camel.bam.model.ProcessDefinition[null], name : Process-1, id :
null
2009-12-08 17:22:22,293 [tyMonitorEngine] DEBUG
JpaTransactionManager - Initiating transaction commit
2009-12-08 17:22:22,293 [tyMonitorEngine] DEBUG
JpaTransactionManager - Committing JPA transaction on EntityManager
[org.hibernate.ejb.EntityManagerImpl@6fdca5]
2009-12-08 17:22:22,293 [tyMonitorEngine] DEBUG
JpaTransactionManager - Closing JPA EntityManager
[org.hibernate.ejb.EntityManagerImpl@6fdca5] after transaction
2009-12-08 17:22:22,293 [tyMonitorEngine] DEBUG
EntityManagerFactoryUtils - Closing JPA EntityManager
2009-12-08 17:22:22,309 [tyMonitorEngine] DEBUG
JpaTransactionManager - Creating new transaction with name [null]:
PROPAGATION_REQUIRED,ISOLATION_DEFAULT
2009-12-08 17:22:22,325 [tyMonitorEngine] DEBUG
JpaTransactionManager - Opened new EntityManager
[org.hibernate.ejb.EntityManagerImpl@10699ea] for JPA transaction
2009-12-08 17:22:22,325 [tyMonitorEngine] DEBUG
JpaTransactionManager - Initiating transaction commit
2009-12-08 17:22:22,325 [tyMonitorEngine] DEBUG
JpaTransactionManager - Committing JPA transaction on EntityManager
[org.hibernate.ejb.EntityManagerImpl@10699ea]
2009-12-08 17:22:22,325 [tyMonitorEngine] DEBUG
JpaTransactionManager - Closing JPA EntityManager
[org.hibernate.ejb.EntityManagerImpl@10699ea] after transaction
2009-12-08 17:22:22,325 [tyMonitorEngine] DEBUG
EntityManagerFactoryUtils - Closing JPA EntityManager
2009-12-08 17:22:22,325 [tyMonitorEngine] DEBUG
ActivityMonitorEngine - Sleeping for 984 millis
2009-12-08 17:22:22,528 [main ] INFO
ProcessBuilder - >> Definition name : Process-1, id : 1
2009-12-08 17:22:22,528 [main ] INFO
ProcessBuilder - >> after persist Definition :

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard

Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm

Charles Moulliard
SOA Architect

My Blog : http://cmoulliard.blogspot.com/

Re: Apache Felix Karaf - Equinox - TypeConverter not loaded

2009-12-08T03:19:32Z

In debug mode, we have this classloading issue :

12:13:50,043 | DEBUG | ExtenderThread-4 | OsgiPackageScanClassResolver |
.DefaultPackageScanClassResolver 418 | Cannot find class
'org/apache/camel/converter/jaxb/JaxbConverter.class' in classloader:
BundleDelegatingClassLoader for [camel-core (org.apache.camel.camel-core)].
Reason: java.lang.ClassNotFoundException:
org.apache.camel.converter.jaxb.JaxbConverter not found from bundle
[org.apache.camel.camel-core]
java.lang.ClassNotFoundException:
org.apache.camel.converter.jaxb.JaxbConverter not found from bundle
[org.apache.camel.camel-core]
at
org.springframework.osgi.util.BundleDelegatingClassLoader.findClass(BundleDelegatingClassLoader.java:103)
at
org.springframework.osgi.util.BundleDelegatingClassLoader.loadClass(BundleDelegatingClassLoader.java:156)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at
org.apache.camel.impl.DefaultPackageScanClassResolver.addIfMatching(DefaultPackageScanClassResolver.java:405)
at
org.apache.camel.osgi.OsgiPackageScanClassResolver.loadImplementationsInBundle(OsgiPackageScanClassResolver.java:121)
at
org.apache.camel.osgi.OsgiPackageScanClassResolver.findInOsgiClassLoader(OsgiPackageScanClassResolver.java:81)
at
org.apache.camel.osgi.OsgiPackageScanClassResolver.find(OsgiPackageScanClassResolver.java:60)
at
org.apache.camel.impl.DefaultPackageScanClassResolver.findAnnotated(DefaultPackageScanClassResolver.java:100)
at
org.apache.camel.osgi.OsgiAnnotationTypeConverterLoader.load(OsgiAnnotationTypeConverterLoader.java:42)
at
org.apache.camel.impl.converter.DefaultTypeConverter.checkLoaded(DefaultTypeConverter.java:379)
at
org.apache.camel.impl.converter.DefaultTypeConverter.doConvertTo(DefaultTypeConverter.java:160)
at
org.apache.camel.impl.converter.DefaultTypeConverter.mandatoryConvertTo(DefaultTypeConverter.java:120)
at
org.apache.camel.impl.converter.DefaultTypeConverter.mandatoryConvertTo(DefaultTypeConverter.java:113)
at
org.apache.camel.util.IntrospectionSupport.convert(IntrospectionSupport.java:277)
at
org.apache.camel.util.IntrospectionSupport.setProperty(IntrospectionSupport.java:233)
at
org.apache.camel.util.IntrospectionSupport.setProperties(IntrospectionSupport.java:200)
at
org.apache.camel.util.EndpointHelper.setProperties(EndpointHelper.java:156)
at
org.apache.camel.impl.DefaultComponent.setProperties(DefaultComponent.java:231)
at
org.apache.camel.component.file.GenericFileComponent.createEndpoint(GenericFileComponent.java:65)
at
org.apache.camel.component.file.GenericFileComponent.createEndpoint(GenericFileComponent.java:36)
at
org.apache.camel.impl.DefaultComponent.createEndpoint(DefaultComponent.java:80)
at
org.apache.camel.impl.DefaultCamelContext.getEndpoint(DefaultCamelContext.java:416)
at
org.apache.camel.util.CamelContextHelper.getMandatoryEndpoint(CamelContextHelper.java:46)
at
org.apache.camel.model.RouteDefinition.resolveEndpoint(RouteDefinition.java:154)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:109)
at
org.apache.camel.impl.DefaultRouteContext.resolveEndpoint(DefaultRouteContext.java:115)
at
org.apache.camel.model.FromDefinition.resolveEndpoint(FromDefinition.java:72)
at
org.apache.camel.impl.DefaultRouteContext.getEndpoint(DefaultRouteContext.java:84)
at
org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:630)
at
org.apache.camel.model.RouteDefinition.addRoutes(RouteDefinition.java:136)
at
org.apache.camel.impl.DefaultCamelContext.startRoute(DefaultCamelContext.java:601)
at
org.apache.camel.impl.DefaultCamelContext.startRouteDefinitions(DefaultCamelContext.java:1156)
at
org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:1073)
at
org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:1009)
at
org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:158)
at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:55)
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:884)
at
org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:197)
at
org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:101)
at
org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:562)
at
org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78)
at
org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49)
at
org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76)
at
org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274)
at
org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736)
at
org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235)
at
org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
at
org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
at
org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320)
at
org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.ClassNotFoundException:
org.apache.camel.converter.jaxb.JaxbConverter
at
org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:494)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:410)
at
org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:398)
at
org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:105)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at
org.eclipse.osgi.internal.loader.BundleLoader.loadClass(BundleLoader.java:326)
at
org.eclipse.osgi.framework.internal.core.BundleHost.loadClass(BundleHost.java:231)
at
org.eclipse.osgi.framework.internal.core.AbstractBundle.loadClass(AbstractBundle.java:1193)
at
org.springframework.osgi.util.BundleDelegatingClassLoader.findClass(BundleDelegatingClassLoader.java:99)
... 50 more

REMARKS :
- The bundle camel-jaxb is deployed on karaf/equinox
- The manifest file of the project imports the packages :
org.apache.camel.converter.jaxb and validated by checking imports of karaf
--> camel-jaxb (82): org.apache.camel.converter.jaxb;
version="2.2.0.SNAPSHOT"

It seems to only look in camel-core bundle and not camel-jaxb !!!!!!

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard

Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm

On Tue, Dec 8, 2009 at 12:03 PM, Charles Moulliard <cmoulliard@...>wrote:

> It seems that Apache Felxi Karaf 1.1.SNAPSHOT + Equinox
> (osgi-3.5.1.v20090827.jar) does not load a TypeConverter defined in
> META-INF/services/org/apache/camel directory
>
> from("file:src/data?noop=true")
> .convertBodyTo(PersonDocument.class)
> .to("jpa:org.apache.camel.example.etl.CustomerEntity");
>
> // the following will dump the database to files
>
> from("jpa:org.apache.camel.example.etl.CustomerEntity?consumeDelete=false&delay=3000&consumeLockEntity=false")
> .setHeader(Exchange.FILE_NAME, el("${in.body.userName}.xml"))
> .to("file:target/customers");
>
>
> 11:39:49,934 | INFO | 1: FileComponent | Tracer
> | rg.apache.camel.processor.Logger 88 |
> 5e0daace-f84c-4b28-bfee-33347488e91a >>> (route1) -->
> jpa://org.apache.camel.example.etl.CustomerEntity <<< Pattern:InOnly,
> Headers:{CamelFileNameOnly=row2.xml,
> CamelFileAbsolutePath=D:\Temp\tutorial\camel-example-etl\apache-felix-karaf-1.1.0-SNAPSHOT\src\data\row2.xml,
> CamelFileLastModified=Tue Jul 14 10:37:40 CEST 2009,
> CamelFileAbsolute=false, CamelFileParent=src\data,
> CamelFileRelativePath=row2.xml, CamelFileName=row2.xml,
> CamelFilePath=src\data\row2.xml, CamelFileLength=982},
> BodyType:org.apache.camel.example.etl.PersonDocument, Body:<person
> user="hiram"><firstName>Hiram</firstName><lastName>Chirino</lastName><city>Tampa</city></person>
> 11:39:49,950 | ERROR | 1: FileComponent | GenericFileOnCompletion
> | rg.apache.camel.processor.Logger 248 | No body available of type:
> org.apache.camel.example.etl.CustomerEntity but has value: Person[user:
> hiram] of type: org.apache.camel.example.etl.PersonDocument on:
> GenericFileMessage with body: Person[user: hiram] on the exchange:
> Exchange[GenericFileMessage with body: Person[user: hiram]]
> org.apache.camel.InvalidPayloadRuntimeException: No body available of type:
> org.apache.camel.example.etl.CustomerEntity but has value: Person[user:
> hiram] of type: org.apache.camel.example.etl.PersonDocument on:
> GenericFileMessage with body: Person[user: hiram] on the exchange:
> Exchange[GenericFileMessage with body: Person[user: hiram]]
> at
> org.apache.camel.component.jpa.JpaEndpoint$1.evaluate(JpaEndpoint.java:268)
>
> Any idea is welcome ?
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>

Charles Moulliard
SOA Architect

My Blog : http://cmoulliard.blogspot.com/

Apache Felix Karaf - Equinox - TypeConverter not loaded

2009-12-08T03:03:59Z

It seems that Apache Felxi Karaf 1.1.SNAPSHOT + Equinox
(osgi-3.5.1.v20090827.jar) does not load a TypeConverter defined in
META-INF/services/org/apache/camel directory

from("file:src/data?noop=true")
.convertBodyTo(PersonDocument.class)
.to("jpa:org.apache.camel.example.etl.CustomerEntity");

// the following will dump the database to files

from("jpa:org.apache.camel.example.etl.CustomerEntity?consumeDelete=false&delay=3000&consumeLockEntity=false")
.setHeader(Exchange.FILE_NAME, el("${in.body.userName}.xml"))
.to("file:target/customers");

11:39:49,934 | INFO | 1: FileComponent | Tracer |
rg.apache.camel.processor.Logger 88 | 5e0daace-f84c-4b28-bfee-33347488e91a
>>> (route1) --> jpa://org.apache.camel.example.etl.CustomerEntity <<<
Pattern:InOnly, Headers:{CamelFileNameOnly=row2.xml,
CamelFileAbsolutePath=D:\Temp\tutorial\camel-example-etl\apache-felix-karaf-1.1.0-SNAPSHOT\src\data\row2.xml,
CamelFileLastModified=Tue Jul 14 10:37:40 CEST 2009,
CamelFileAbsolute=false, CamelFileParent=src\data,
CamelFileRelativePath=row2.xml, CamelFileName=row2.xml,
CamelFilePath=src\data\row2.xml, CamelFileLength=982},
BodyType:org.apache.camel.example.etl.PersonDocument, Body:<person
user="hiram"><firstName>Hiram</firstName><lastName>Chirino</lastName><city>Tampa</city></person>
11:39:49,950 | ERROR | 1: FileComponent | GenericFileOnCompletion |
rg.apache.camel.processor.Logger 248 | No body available of type:
org.apache.camel.example.etl.CustomerEntity but has value: Person[user:
hiram] of type: org.apache.camel.example.etl.PersonDocument on:
GenericFileMessage with body: Person[user: hiram] on the exchange:
Exchange[GenericFileMessage with body: Person[user: hiram]]
org.apache.camel.InvalidPayloadRuntimeException: No body available of type:
org.apache.camel.example.etl.CustomerEntity but has value: Person[user:
hiram] of type: org.apache.camel.example.etl.PersonDocument on:
GenericFileMessage with body: Person[user: hiram] on the exchange:
Exchange[GenericFileMessage with body: Person[user: hiram]]
at
org.apache.camel.component.jpa.JpaEndpoint$1.evaluate(JpaEndpoint.java:268)

Any idea is welcome ?

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard

Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm

Charles Moulliard
SOA Architect

My Blog : http://cmoulliard.blogspot.com/

Re: camel-example-etl & openJPA (If this is a new instance, make sure any version and/or auto-generated primary key fields are null/default when persisting)

2009-12-08T00:30:08Z

This line does not make sense as the instance CustomerEntity is send next to
the JPA endpoint (consuler) who will persist the information in the DB
through Spring Transaction handling and DB connection.

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard

Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm

On Tue, Dec 8, 2009 at 9:19 AM, Claus Ibsen <claus.ibsen@...> wrote:

> On Tue, Dec 8, 2009 at 9:11 AM, Charles Moulliard <cmoulliard@...>
> wrote:
> > Hi Claus,
> >
> > By removing the line template.persist(answer), I have been able to solve
> the
> > issue and to run the project with openJPA.
> >
>
> Then it doesn't save the user into the database? Or how do you store
> users in the database?
> I thought there was some detach or the likes you could call after the
> persist so the enttiy can be used outside JPA.
>
>
> > Willem will now adapt the example and will provide different profiles to
> > allow to run etl with Hibernate, OpenJPA and Derby. By the way, we have
> also
> > test it on OSGI server.
> >
> > Regards,
> >
> > Charles Moulliard
> > Senior Enterprise Architect
> > Apache Camel Committer
> >
> > *****************************
> > blog : http://cmoulliard.blogspot.com
> > twitter : http://twitter.com/cmoulliard
> > Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> >
> > Apache Camel Group :
> > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
> >
> >
> > On Mon, Dec 7, 2009 at 8:20 PM, Claus Ibsen <claus.ibsen@...>
> wrote:
> >
> >> On Mon, Dec 7, 2009 at 2:00 PM, Charles Moulliard <cmoulliard@...
> >
> >> wrote:
> >> > I have understand why we have this error :
> >> >
> >> > In fact, within the CustomerTransformer class, the method
> >> findCustomerByName
> >> > (which is called) uses 'template.persist(answer);' who will inform
> Spring
> >> to
> >> > insert in the DB a customerEntity object if it not find from the SQL
> >> query.
> >> > Next, the same object is send to the JPA endpoint who will detect that
> >> the
> >> > object has not been detached.
> >> >
> >> > That means that attachment/detachment of objects does not occur in the
> >> same
> >> > way using Hibernate, JPA, ... as the code works for Hibernate
> >> >
> >> > Does anybody knows what was the intend to use this code in the
> transform
> >> > class ?
> >> >
> >>
> >> No I guess many of those "standards" are still problematic to use as
> >> some impl. do X and others do Y.
> >> I guess maybe some detach or whatever needs to be added when it
> >> inserts the customer.
> >>
> >> Can you not try looking into this as you are messing with it already?
> >>
> >>
> >> > **
> >> > * Finds a customer for the given username, or creates and inserts a
> new
> >> one
> >> > */
> >> > protected CustomerEntity findCustomerByName(JpaTemplate template,
> String
> >> > user) {
> >> > List<CustomerEntity> list = CastUtils.cast(template.find("select x
> from "
> >> +
> >> > CustomerEntity.class.getName() + " x where x.userName = ?1", user));
> >> > if (list.isEmpty()) {
> >> > CustomerEntity answer = new CustomerEntity();
> >> > answer.setUserName(user);
> >> > template.persist(answer);
> >> > return answer;
> >> > } else {
> >> > return list.get(0);
> >> > }
> >> > }
> >> >
> >> > Regards,
> >> >
> >> > Charles Moulliard
> >> > Senior Enterprise Architect
> >> > Apache Camel Committer
> >> >
> >> > *****************************
> >> > blog : http://cmoulliard.blogspot.com
> >> > twitter : http://twitter.com/cmoulliard
> >> > Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> >> >
> >> > Apache Camel Group :
> >> > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
> >> >
> >> >
> >> > On Mon, Dec 7, 2009 at 1:11 PM, Charles Moulliard <
> cmoulliard@...
> >> >wrote:
> >> >
> >> >> When I try to use the example camel-example-etl with openJPA, here is
> >> the
> >> >> error that I receive
> >> >>
> >> >> [ Camel thread 0: FileComponent] Tracer INFO
> >> >> be7ae591-e2ea-4021-8179-d6bdd5f5398c >>> (route1) -->
> >> >> jpa://org.apache.camel.ex
> >> >> ample.etl.CustomerEntity?consumeLockEntity=true <<< Pattern:InOnly,
> >> >> Headers:{CamelFileNameOnly=row2.xml,
> >> >> CamelFileAbsolutePath=D:\Dvlpt\Java\workspace
> >> >> \apache-camel-source\examples\camel-example-etl\src\data\row2.xml,
> >> >> CamelFileRelativePath=row2.xml, CamelFileName=row2.xml,
> >> >> CamelFilePath=src\data\row2
> >> >> .xml, CamelFileParent=src\data, CamelFileAbsolute=false,
> >> >> CamelFileLength=982, CamelFileLastModified=Tue Jul 14 10:37:40 CEST
> >> 2009},
> >> >> BodyType:org.apach
> >> >> e.camel.example.etl.PersonDocument, Body:<person
> >> >>
> >>
> user="hiram"><firstName>Hiram</firstName><lastName>Chirino</lastName><city>Tampa</city></person>
> >> >> 16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL
> -
> >> <t
> >> >> 12662763, conn 1634627> executing prepstmnt 585058
> >> >> SELECT t0.id, t0.city, t0.firstName, t0.phone, t0.street,
> t0.surname,
> >> >> t0.userName, t0.zip
> >> >> FROM Customer t0
> >> >> WHERE (t0.userName = ?)
> >> >> [params=(String) hiram]
> >> >> 16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL
> -
> >> <t
> >> >> 12662763, conn 1634627> [0 ms] spent
> >> >> [ Camel thread 0: FileComponent] CustomerTransformer DEBUG
> >> >> Created customer: Customer[userName: hiram firstName: Hiram surname:
> >> >> Chirino]
> >> >> 16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL
> -
> >> <t
> >> >> 12662763, conn 21035203> executing prepstmnt 19041450
> >> >> SELECT t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
> >> >> t0.userName, t0.zip
> >> >> FROM Customer t0
> >> >> WHERE t0.id = ?
> >> >> [params=(long) 0]
> >> >> 16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL
> -
> >> <t
> >> >> 12662763, conn 21035203> [0 ms] spent
> >> >> [ Camel thread 0: FileComponent] DefaultErrorHandler DEBUG
> >> >> Failed delivery for exchangeId: be7ae591-e2ea-4021-8179-d6bdd5f5398c.
> On
> >> >> deliver
> >> >> y attempt: 0 caught:
> >> >> org.springframework.dao.DataIntegrityViolationException: Attempt to
> >> persist
> >> >> detached object "org.apache.camel.example.etl.Custome
> >> >> rEntity@8bfa09". If this is a new instance, make sure any version
> >> and/or
> >> >> auto-generated primary key fields are null/default when persisting.;
> >> nested
> >> >> exception is <openjpa-1.3.0-SNAPSHOT-r422266:881892 nonfatal store
> >> error>
> >> >> org.apache.openjpa.persistence.EntityExistsException: Attempt to
> persist
> >> det
> >> >> ached object "org.apache.camel.example.etl.CustomerEntity@8bfa09".
> If
> >> >> this is a new instance, make sure any version and/or auto-generated
> >> primary
> >> >> key
> >> >> fields are null/default when persisting.
> >> >>
> >> >> Anybody has an idea to avoid this ?
> >> >>
> >> >> Regards,
> >> >>
> >> >> Charles Moulliard
> >> >> Senior Enterprise Architect
> >> >> Apache Camel Committer
> >> >>
> >> >> *****************************
> >> >> blog : http://cmoulliard.blogspot.com
> >> >> twitter : http://twitter.com/cmoulliard
> >> >> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> >> >>
> >> >> Apache Camel Group :
> >> >> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
> >> >>
> >> >
> >>
> >>
> >>
> >> --
> >> 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
> >>
> >
>
>
>
> --
> 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
>

Charles Moulliard
SOA Architect

My Blog : http://cmoulliard.blogspot.com/

Re: camel-example-etl & openJPA (If this is a new instance, make sure any version and/or auto-generated primary key fields are null/default when persisting)

2009-12-08T00:19:21Z

On Tue, Dec 8, 2009 at 9:11 AM, Charles Moulliard <cmoulliard@...> wrote:
> Hi Claus,
>
> By removing the line template.persist(answer), I have been able to solve the
> issue and to run the project with openJPA.
>

Then it doesn't save the user into the database? Or how do you store
users in the database?
I thought there was some detach or the likes you could call after the
persist so the enttiy can be used outside JPA.

> Willem will now adapt the example and will provide different profiles to
> allow to run etl with Hibernate, OpenJPA and Derby. By the way, we have also
> test it on OSGI server.
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>
>
> On Mon, Dec 7, 2009 at 8:20 PM, Claus Ibsen <claus.ibsen@...> wrote:
>
>> On Mon, Dec 7, 2009 at 2:00 PM, Charles Moulliard <cmoulliard@...>
>> wrote:
>> > I have understand why we have this error :
>> >
>> > In fact, within the CustomerTransformer class, the method
>> findCustomerByName
>> > (which is called) uses 'template.persist(answer);' who will inform Spring
>> to
>> > insert in the DB a customerEntity object if it not find from the SQL
>> query.
>> > Next, the same object is send to the JPA endpoint who will detect that
>> the
>> > object has not been detached.
>> >
>> > That means that attachment/detachment of objects does not occur in the
>> same
>> > way using Hibernate, JPA, ... as the code works for Hibernate
>> >
>> > Does anybody knows what was the intend to use this code in the transform
>> > class ?
>> >
>>
>> No I guess many of those "standards" are still problematic to use as
>> some impl. do X and others do Y.
>> I guess maybe some detach or whatever needs to be added when it
>> inserts the customer.
>>
>> Can you not try looking into this as you are messing with it already?
>>
>>
>> > **
>> > * Finds a customer for the given username, or creates and inserts a new
>> one
>> > */
>> > protected CustomerEntity findCustomerByName(JpaTemplate template, String
>> > user) {
>> > List<CustomerEntity> list = CastUtils.cast(template.find("select x from "
>> +
>> > CustomerEntity.class.getName() + " x where x.userName = ?1", user));
>> > if (list.isEmpty()) {
>> > CustomerEntity answer = new CustomerEntity();
>> > answer.setUserName(user);
>> > template.persist(answer);
>> > return answer;
>> > } else {
>> > return list.get(0);
>> > }
>> > }
>> >
>> > Regards,
>> >
>> > Charles Moulliard
>> > Senior Enterprise Architect
>> > Apache Camel Committer
>> >
>> > *****************************
>> > blog : http://cmoulliard.blogspot.com
>> > twitter : http://twitter.com/cmoulliard
>> > Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>> >
>> > Apache Camel Group :
>> > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>> >
>> >
>> > On Mon, Dec 7, 2009 at 1:11 PM, Charles Moulliard <cmoulliard@...
>> >wrote:
>> >
>> >> When I try to use the example camel-example-etl with openJPA, here is
>> the
>> >> error that I receive
>> >>
>> >> [ Camel thread 0: FileComponent] Tracer INFO
>> >> be7ae591-e2ea-4021-8179-d6bdd5f5398c >>> (route1) -->
>> >> jpa://org.apache.camel.ex
>> >> ample.etl.CustomerEntity?consumeLockEntity=true <<< Pattern:InOnly,
>> >> Headers:{CamelFileNameOnly=row2.xml,
>> >> CamelFileAbsolutePath=D:\Dvlpt\Java\workspace
>> >> \apache-camel-source\examples\camel-example-etl\src\data\row2.xml,
>> >> CamelFileRelativePath=row2.xml, CamelFileName=row2.xml,
>> >> CamelFilePath=src\data\row2
>> >> .xml, CamelFileParent=src\data, CamelFileAbsolute=false,
>> >> CamelFileLength=982, CamelFileLastModified=Tue Jul 14 10:37:40 CEST
>> 2009},
>> >> BodyType:org.apach
>> >> e.camel.example.etl.PersonDocument, Body:<person
>> >>
>> user="hiram"><firstName>Hiram</firstName><lastName>Chirino</lastName><city>Tampa</city></person>
>> >> 16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL -
>> <t
>> >> 12662763, conn 1634627> executing prepstmnt 585058
>> >> SELECT t0.id, t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
>> >> t0.userName, t0.zip
>> >> FROM Customer t0
>> >> WHERE (t0.userName = ?)
>> >> [params=(String) hiram]
>> >> 16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL -
>> <t
>> >> 12662763, conn 1634627> [0 ms] spent
>> >> [ Camel thread 0: FileComponent] CustomerTransformer DEBUG
>> >> Created customer: Customer[userName: hiram firstName: Hiram surname:
>> >> Chirino]
>> >> 16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL -
>> <t
>> >> 12662763, conn 21035203> executing prepstmnt 19041450
>> >> SELECT t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
>> >> t0.userName, t0.zip
>> >> FROM Customer t0
>> >> WHERE t0.id = ?
>> >> [params=(long) 0]
>> >> 16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL -
>> <t
>> >> 12662763, conn 21035203> [0 ms] spent
>> >> [ Camel thread 0: FileComponent] DefaultErrorHandler DEBUG
>> >> Failed delivery for exchangeId: be7ae591-e2ea-4021-8179-d6bdd5f5398c. On
>> >> deliver
>> >> y attempt: 0 caught:
>> >> org.springframework.dao.DataIntegrityViolationException: Attempt to
>> persist
>> >> detached object "org.apache.camel.example.etl.Custome
>> >> rEntity@8bfa09". If this is a new instance, make sure any version
>> and/or
>> >> auto-generated primary key fields are null/default when persisting.;
>> nested
>> >> exception is <openjpa-1.3.0-SNAPSHOT-r422266:881892 nonfatal store
>> error>
>> >> org.apache.openjpa.persistence.EntityExistsException: Attempt to persist
>> det
>> >> ached object "org.apache.camel.example.etl.CustomerEntity@8bfa09". If
>> >> this is a new instance, make sure any version and/or auto-generated
>> primary
>> >> key
>> >> fields are null/default when persisting.
>> >>
>> >> Anybody has an idea to avoid this ?
>> >>
>> >> Regards,
>> >>
>> >> Charles Moulliard
>> >> Senior Enterprise Architect
>> >> Apache Camel Committer
>> >>
>> >> *****************************
>> >> blog : http://cmoulliard.blogspot.com
>> >> twitter : http://twitter.com/cmoulliard
>> >> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>> >>
>> >> Apache Camel Group :
>> >> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>> >>
>> >
>>
>>
>>
>> --
>> 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
>>
>

Re: camel-example-etl & openJPA (If this is a new instance, make sure any version and/or auto-generated primary key fields are null/default when persisting)

2009-12-08T00:11:22Z

Hi Claus,

By removing the line template.persist(answer), I have been able to solve the
issue and to run the project with openJPA.

Willem will now adapt the example and will provide different profiles to
allow to run etl with Hibernate, OpenJPA and Derby. By the way, we have also
test it on OSGI server.

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard

Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm

On Mon, Dec 7, 2009 at 8:20 PM, Claus Ibsen <claus.ibsen@...> wrote:

> On Mon, Dec 7, 2009 at 2:00 PM, Charles Moulliard <cmoulliard@...>
> wrote:
> > I have understand why we have this error :
> >
> > In fact, within the CustomerTransformer class, the method
> findCustomerByName
> > (which is called) uses 'template.persist(answer);' who will inform Spring
> to
> > insert in the DB a customerEntity object if it not find from the SQL
> query.
> > Next, the same object is send to the JPA endpoint who will detect that
> the
> > object has not been detached.
> >
> > That means that attachment/detachment of objects does not occur in the
> same
> > way using Hibernate, JPA, ... as the code works for Hibernate
> >
> > Does anybody knows what was the intend to use this code in the transform
> > class ?
> >
>
> No I guess many of those "standards" are still problematic to use as
> some impl. do X and others do Y.
> I guess maybe some detach or whatever needs to be added when it
> inserts the customer.
>
> Can you not try looking into this as you are messing with it already?
>
>
> > **
> > * Finds a customer for the given username, or creates and inserts a new
> one
> > */
> > protected CustomerEntity findCustomerByName(JpaTemplate template, String
> > user) {
> > List<CustomerEntity> list = CastUtils.cast(template.find("select x from "
> +
> > CustomerEntity.class.getName() + " x where x.userName = ?1", user));
> > if (list.isEmpty()) {
> > CustomerEntity answer = new CustomerEntity();
> > answer.setUserName(user);
> > template.persist(answer);
> > return answer;
> > } else {
> > return list.get(0);
> > }
> > }
> >
> > Regards,
> >
> > Charles Moulliard
> > Senior Enterprise Architect
> > Apache Camel Committer
> >
> > *****************************
> > blog : http://cmoulliard.blogspot.com
> > twitter : http://twitter.com/cmoulliard
> > Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> >
> > Apache Camel Group :
> > http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
> >
> >
> > On Mon, Dec 7, 2009 at 1:11 PM, Charles Moulliard <cmoulliard@...
> >wrote:
> >
> >> When I try to use the example camel-example-etl with openJPA, here is
> the
> >> error that I receive
> >>
> >> [ Camel thread 0: FileComponent] Tracer INFO
> >> be7ae591-e2ea-4021-8179-d6bdd5f5398c >>> (route1) -->
> >> jpa://org.apache.camel.ex
> >> ample.etl.CustomerEntity?consumeLockEntity=true <<< Pattern:InOnly,
> >> Headers:{CamelFileNameOnly=row2.xml,
> >> CamelFileAbsolutePath=D:\Dvlpt\Java\workspace
> >> \apache-camel-source\examples\camel-example-etl\src\data\row2.xml,
> >> CamelFileRelativePath=row2.xml, CamelFileName=row2.xml,
> >> CamelFilePath=src\data\row2
> >> .xml, CamelFileParent=src\data, CamelFileAbsolute=false,
> >> CamelFileLength=982, CamelFileLastModified=Tue Jul 14 10:37:40 CEST
> 2009},
> >> BodyType:org.apach
> >> e.camel.example.etl.PersonDocument, Body:<person
> >>
> user="hiram"><firstName>Hiram</firstName><lastName>Chirino</lastName><city>Tampa</city></person>
> >> 16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL -
> <t
> >> 12662763, conn 1634627> executing prepstmnt 585058
> >> SELECT t0.id, t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
> >> t0.userName, t0.zip
> >> FROM Customer t0
> >> WHERE (t0.userName = ?)
> >> [params=(String) hiram]
> >> 16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL -
> <t
> >> 12662763, conn 1634627> [0 ms] spent
> >> [ Camel thread 0: FileComponent] CustomerTransformer DEBUG
> >> Created customer: Customer[userName: hiram firstName: Hiram surname:
> >> Chirino]
> >> 16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL -
> <t
> >> 12662763, conn 21035203> executing prepstmnt 19041450
> >> SELECT t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
> >> t0.userName, t0.zip
> >> FROM Customer t0
> >> WHERE t0.id = ?
> >> [params=(long) 0]
> >> 16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL -
> <t
> >> 12662763, conn 21035203> [0 ms] spent
> >> [ Camel thread 0: FileComponent] DefaultErrorHandler DEBUG
> >> Failed delivery for exchangeId: be7ae591-e2ea-4021-8179-d6bdd5f5398c. On
> >> deliver
> >> y attempt: 0 caught:
> >> org.springframework.dao.DataIntegrityViolationException: Attempt to
> persist
> >> detached object "org.apache.camel.example.etl.Custome
> >> rEntity@8bfa09". If this is a new instance, make sure any version
> and/or
> >> auto-generated primary key fields are null/default when persisting.;
> nested
> >> exception is <openjpa-1.3.0-SNAPSHOT-r422266:881892 nonfatal store
> error>
> >> org.apache.openjpa.persistence.EntityExistsException: Attempt to persist
> det
> >> ached object "org.apache.camel.example.etl.CustomerEntity@8bfa09". If
> >> this is a new instance, make sure any version and/or auto-generated
> primary
> >> key
> >> fields are null/default when persisting.
> >>
> >> Anybody has an idea to avoid this ?
> >>
> >> Regards,
> >>
> >> Charles Moulliard
> >> Senior Enterprise Architect
> >> Apache Camel Committer
> >>
> >> *****************************
> >> blog : http://cmoulliard.blogspot.com
> >> twitter : http://twitter.com/cmoulliard
> >> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
> >>
> >> Apache Camel Group :
> >> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
> >>
> >
>
>
>
> --
> 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
>

Charles Moulliard
SOA Architect

My Blog : http://cmoulliard.blogspot.com/

Re: Camel & MINA Compont

2009-12-07T22:35:53Z

Hi there,

I recommend first going to the Apache Mina project: there's a pretty good tutorial there on the use of Mina. Then, take a look at the page on the camel mina component at camel.apache.org.

/Ade

----- Original Message -----
From: GilbertLin <6555tw.gilbert@...>
To: users@... <users@...>
Sent: Tue Dec 08 01:32:24 2009
Subject: Camel & MINA Compont

Hi,
I am a student, and want research Camel for implement banking payment
gateway currently.

I already study Content Based Router, Splitter, Message Transformation
example from Fuse's Webinar

is there any exmaple about using MINA Compont, I don't know how to start
config or coding?
is Mina like ActiveMQ need before Camel start?

http://old.nabble.com/file/p26689336/TCP.jpg
--
View this message in context: http://old.nabble.com/Camel---MINA-Compont-tp26689336p26689336.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Camel & MINA Compont

2009-12-07T22:32:22Z

Hi,
I am a student, and want research Camel for implement banking payment gateway currently.

I already study Content Based Router, Splitter, Message Transformation example from Fuse's Webinar

is there any exmaple about using MINA Compont, I don't know how to start config or coding?
is Mina like ActiveMQ need before Camel start?

Re: Request-Response with Producer/Consumer Templates

2009-12-07T21:31:20Z

Hi

What JMS Broker are you using?

I do think brokers can mess with the correlation id so its not always
as strait forward as people think with JMS.
And what version of Camel are you using?

On Tue, Dec 8, 2009 at 6:29 AM, Claus Ibsen <claus.ibsen@...> wrote:

> Hi
>
> If you create a route on the server side, then Camel should take care
> of it all. As it can detect the JMSReplyTo header and know where to
> send the reply with the correlation id etc.
>
>
>
> On Tue, Dec 8, 2009 at 1:39 AM, FCasale <fallfollower@...> wrote:
>>
>>
>> Thanks, I am much closer now... I'm just not sure how to set the
>> correlationId for the reply message.
>>
>> It is coming back correlationId=null and is therefore ignored.
>>
>> On the server side I am trying this:
>>
>> --------------
>>
>> Exchange exch = consumer.receive("test-jms:queue:test.queue");
>> Message msg = exch.getIn();
>>
>> producer.sendBodyAndHeader(msg.getHeader("JMSReplyTo").toString(), "Ho Ho",
>> "JMSCorrelationId", msg.getHeader("JMSCorrelationId").toString());
>>
>> --------------
>>
>> So the message is replying on the correct temporary queue... but with no
>> correlationId so the response message is being ignored....
>>
>> How do I set the correlationId on the response message?
>>
>> --
>> View this message in context: http://old.nabble.com/Request-Response-with-Producer-Consumer-Templates-tp26635175p26686915.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
>

Re: Request-Response with Producer/Consumer Templates

2009-12-07T21:29:51Z

Hi

If you create a route on the server side, then Camel should take care
of it all. As it can detect the JMSReplyTo header and know where to
send the reply with the correlation id etc.

On Tue, Dec 8, 2009 at 1:39 AM, FCasale <fallfollower@...> wrote:

>
>
> Thanks, I am much closer now... I'm just not sure how to set the
> correlationId for the reply message.
>
> It is coming back correlationId=null and is therefore ignored.
>
> On the server side I am trying this:
>
> --------------
>
> Exchange exch = consumer.receive("test-jms:queue:test.queue");
> Message msg = exch.getIn();
>
> producer.sendBodyAndHeader(msg.getHeader("JMSReplyTo").toString(), "Ho Ho",
> "JMSCorrelationId", msg.getHeader("JMSCorrelationId").toString());
>
> --------------
>
> So the message is replying on the correct temporary queue... but with no
> correlationId so the response message is being ignored....
>
> How do I set the correlationId on the response message?
>
> --
> View this message in context: http://old.nabble.com/Request-Response-with-Producer-Consumer-Templates-tp26635175p26686915.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>

Re: Request-Response with Producer/Consumer Templates

2009-12-07T16:39:02Z

Thanks, I am much closer now... I'm just not sure how to set the correlationId for the reply message.

It is coming back correlationId=null and is therefore ignored.

On the server side I am trying this:

--------------

Exchange exch = consumer.receive("test-jms:queue:test.queue");
Message msg = exch.getIn();

producer.sendBodyAndHeader(msg.getHeader("JMSReplyTo").toString(), "Ho Ho", "JMSCorrelationId", msg.getHeader("JMSCorrelationId").toString());

--------------

So the message is replying on the correct temporary queue... but with no correlationId so the response message is being ignored....

How do I set the correlationId on the response message?

Re: camel-example-etl & openJPA (If this is a new instance, make sure any version and/or auto-generated primary key fields are null/default when persisting)

2009-12-07T11:20:58Z

On Mon, Dec 7, 2009 at 2:00 PM, Charles Moulliard <cmoulliard@...> wrote:

> I have understand why we have this error :
>
> In fact, within the CustomerTransformer class, the method findCustomerByName
> (which is called) uses 'template.persist(answer);' who will inform Spring to
> insert in the DB a customerEntity object if it not find from the SQL query.
> Next, the same object is send to the JPA endpoint who will detect that the
> object has not been detached.
>
> That means that attachment/detachment of objects does not occur in the same
> way using Hibernate, JPA, ... as the code works for Hibernate
>
> Does anybody knows what was the intend to use this code in the transform
> class ?
>

No I guess many of those "standards" are still problematic to use as
some impl. do X and others do Y.
I guess maybe some detach or whatever needs to be added when it
inserts the customer.

Can you not try looking into this as you are messing with it already?

> **
> * Finds a customer for the given username, or creates and inserts a new one
> */
> protected CustomerEntity findCustomerByName(JpaTemplate template, String
> user) {
> List<CustomerEntity> list = CastUtils.cast(template.find("select x from " +
> CustomerEntity.class.getName() + " x where x.userName = ?1", user));
> if (list.isEmpty()) {
> CustomerEntity answer = new CustomerEntity();
> answer.setUserName(user);
> template.persist(answer);
> return answer;
> } else {
> return list.get(0);
> }
> }
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>
>
> On Mon, Dec 7, 2009 at 1:11 PM, Charles Moulliard <cmoulliard@...>wrote:
>
>> When I try to use the example camel-example-etl with openJPA, here is the
>> error that I receive
>>
>> [ Camel thread 0: FileComponent] Tracer INFO
>> be7ae591-e2ea-4021-8179-d6bdd5f5398c >>> (route1) -->
>> jpa://org.apache.camel.ex
>> ample.etl.CustomerEntity?consumeLockEntity=true <<< Pattern:InOnly,
>> Headers:{CamelFileNameOnly=row2.xml,
>> CamelFileAbsolutePath=D:\Dvlpt\Java\workspace
>> \apache-camel-source\examples\camel-example-etl\src\data\row2.xml,
>> CamelFileRelativePath=row2.xml, CamelFileName=row2.xml,
>> CamelFilePath=src\data\row2
>> .xml, CamelFileParent=src\data, CamelFileAbsolute=false,
>> CamelFileLength=982, CamelFileLastModified=Tue Jul 14 10:37:40 CEST 2009},
>> BodyType:org.apach
>> e.camel.example.etl.PersonDocument, Body:<person
>> user="hiram"><firstName>Hiram</firstName><lastName>Chirino</lastName><city>Tampa</city></person>
>> 16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
>> 12662763, conn 1634627> executing prepstmnt 585058
>> SELECT t0.id, t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
>> t0.userName, t0.zip
>> FROM Customer t0
>> WHERE (t0.userName = ?)
>> [params=(String) hiram]
>> 16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
>> 12662763, conn 1634627> [0 ms] spent
>> [ Camel thread 0: FileComponent] CustomerTransformer DEBUG
>> Created customer: Customer[userName: hiram firstName: Hiram surname:
>> Chirino]
>> 16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
>> 12662763, conn 21035203> executing prepstmnt 19041450
>> SELECT t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
>> t0.userName, t0.zip
>> FROM Customer t0
>> WHERE t0.id = ?
>> [params=(long) 0]
>> 16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
>> 12662763, conn 21035203> [0 ms] spent
>> [ Camel thread 0: FileComponent] DefaultErrorHandler DEBUG
>> Failed delivery for exchangeId: be7ae591-e2ea-4021-8179-d6bdd5f5398c. On
>> deliver
>> y attempt: 0 caught:
>> org.springframework.dao.DataIntegrityViolationException: Attempt to persist
>> detached object "org.apache.camel.example.etl.Custome
>> rEntity@8bfa09". If this is a new instance, make sure any version and/or
>> auto-generated primary key fields are null/default when persisting.; nested
>> exception is <openjpa-1.3.0-SNAPSHOT-r422266:881892 nonfatal store error>
>> org.apache.openjpa.persistence.EntityExistsException: Attempt to persist det
>> ached object "org.apache.camel.example.etl.CustomerEntity@8bfa09". If
>> this is a new instance, make sure any version and/or auto-generated primary
>> key
>> fields are null/default when persisting.
>>
>> Anybody has an idea to avoid this ?
>>
>> Regards,
>>
>> Charles Moulliard
>> Senior Enterprise Architect
>> Apache Camel Committer
>>
>> *****************************
>> blog : http://cmoulliard.blogspot.com
>> twitter : http://twitter.com/cmoulliard
>> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>>
>> Apache Camel Group :
>> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>>
>

Re: Can't return null with Camel remoting

2009-12-07T11:18:36Z

Hi

Could you please use more time to report this issue?

Create a JIRA ticket and attach a sample with the problem if possible.
At least post the stacktrace and you route and remote service
interfaces and whatnot, so we have something to use to track the
issue.

On Mon, Dec 7, 2009 at 7:52 PM, Ming Fang <mingfang@...> wrote:
> Camel v2.1 no longer allow remote service to return null value.
> I'm getting a InvalidPayloadException in CamelInvocationHandler.invoke().
>
> This is a bug since it is legal to return null values.
>

> --Ming
>

--
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

Can't return null with Camel remoting

2009-12-07T10:52:06Z

Camel v2.1 no longer allow remote service to return null value.
I'm getting a InvalidPayloadException in CamelInvocationHandler.invoke
().

This is a bug since it is legal to return null values.

--Ming

Re: camel-example-etl & openJPA (If this is a new instance, make sure any version and/or auto-generated primary key fields are null/default when persisting)

2009-12-07T05:00:59Z

I have understand why we have this error :

In fact, within the CustomerTransformer class, the method findCustomerByName
(which is called) uses 'template.persist(answer);' who will inform Spring to
insert in the DB a customerEntity object if it not find from the SQL query.
Next, the same object is send to the JPA endpoint who will detect that the
object has not been detached.

That means that attachment/detachment of objects does not occur in the same
way using Hibernate, JPA, ... as the code works for Hibernate

Does anybody knows what was the intend to use this code in the transform
class ?

**
* Finds a customer for the given username, or creates and inserts a new one
*/
protected CustomerEntity findCustomerByName(JpaTemplate template, String
user) {
List<CustomerEntity> list = CastUtils.cast(template.find("select x from " +
CustomerEntity.class.getName() + " x where x.userName = ?1", user));
if (list.isEmpty()) {
CustomerEntity answer = new CustomerEntity();
answer.setUserName(user);
template.persist(answer);
return answer;
} else {
return list.get(0);
}
}

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard

Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm

On Mon, Dec 7, 2009 at 1:11 PM, Charles Moulliard <cmoulliard@...>wrote:

> When I try to use the example camel-example-etl with openJPA, here is the
> error that I receive
>
> [ Camel thread 0: FileComponent] Tracer INFO
> be7ae591-e2ea-4021-8179-d6bdd5f5398c >>> (route1) -->
> jpa://org.apache.camel.ex
> ample.etl.CustomerEntity?consumeLockEntity=true <<< Pattern:InOnly,
> Headers:{CamelFileNameOnly=row2.xml,
> CamelFileAbsolutePath=D:\Dvlpt\Java\workspace
> \apache-camel-source\examples\camel-example-etl\src\data\row2.xml,
> CamelFileRelativePath=row2.xml, CamelFileName=row2.xml,
> CamelFilePath=src\data\row2
> .xml, CamelFileParent=src\data, CamelFileAbsolute=false,
> CamelFileLength=982, CamelFileLastModified=Tue Jul 14 10:37:40 CEST 2009},
> BodyType:org.apach
> e.camel.example.etl.PersonDocument, Body:<person
> user="hiram"><firstName>Hiram</firstName><lastName>Chirino</lastName><city>Tampa</city></person>
> 16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
> 12662763, conn 1634627> executing prepstmnt 585058
> SELECT t0.id, t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
> t0.userName, t0.zip
> FROM Customer t0
> WHERE (t0.userName = ?)
> [params=(String) hiram]
> 16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
> 12662763, conn 1634627> [0 ms] spent
> [ Camel thread 0: FileComponent] CustomerTransformer DEBUG
> Created customer: Customer[userName: hiram firstName: Hiram surname:
> Chirino]
> 16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
> 12662763, conn 21035203> executing prepstmnt 19041450
> SELECT t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
> t0.userName, t0.zip
> FROM Customer t0
> WHERE t0.id = ?
> [params=(long) 0]
> 16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
> 12662763, conn 21035203> [0 ms] spent
> [ Camel thread 0: FileComponent] DefaultErrorHandler DEBUG
> Failed delivery for exchangeId: be7ae591-e2ea-4021-8179-d6bdd5f5398c. On
> deliver
> y attempt: 0 caught:
> org.springframework.dao.DataIntegrityViolationException: Attempt to persist
> detached object "org.apache.camel.example.etl.Custome
> rEntity@8bfa09". If this is a new instance, make sure any version and/or
> auto-generated primary key fields are null/default when persisting.; nested
> exception is <openjpa-1.3.0-SNAPSHOT-r422266:881892 nonfatal store error>
> org.apache.openjpa.persistence.EntityExistsException: Attempt to persist det
> ached object "org.apache.camel.example.etl.CustomerEntity@8bfa09". If
> this is a new instance, make sure any version and/or auto-generated primary
> key
> fields are null/default when persisting.
>
> Anybody has an idea to avoid this ?
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****************************
> blog : http://cmoulliard.blogspot.com
> twitter : http://twitter.com/cmoulliard
> Linkedlin : http://www.linkedin.com/in/charlesmoulliard
>
> Apache Camel Group :
> http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm
>

Charles Moulliard
SOA Architect

My Blog : http://cmoulliard.blogspot.com/

Re: handled exception in sub-route

2009-12-07T04:21:24Z

On Mon, Dec 7, 2009 at 1:19 PM, trivedi kumar b
<Trivedi.Bodlapati@...> wrote:

Yeah the original ticket is not resolved

Re: handled exception in sub-route

2009-12-07T04:19:20Z

Hi,

Eventhough I use doTry().. doCatch() blocks to handle the issue that Jens explained before, the problem is still exists, this is how my route looks like in which the call never goes to "direct:C" when there is an exception in sub-route "B":
from("direct:A")
.to("direct:B")
.to("direct:C");

from("direct:B")
.doTry()
.transacted().end()
.code goes that throws an exception
.doCatch(Exception.class)
.handled(true)
.markRollbackOnly()
.end();

from("direct:C")
.....

Claus Ibsen-2 wrote:

On Sun, Dec 6, 2009 at 11:25 PM, trivedi kumar b
<Trivedi.Bodlapati@ge.com> wrote:
>
> Hi,
>
> If I use doTry.. doCatch, with similar route that includes transactions,
> will that work as expected? I mean, markRollbackOnly() option inside
> doCatch() will rollback the transaction? Pls let me know the behaviour.
>

Yes markRollbackOnly() is only for transactions and will issue a
status.setRollbackOnly() on the Spring Transaction underneath.
That should render the transaction outcome as rollback only.

It will not tamper with the Exchange by setting an exception as
rollback() does by setting a RollbackException on the Exchange.

> Thanks,
> Trivedi
>
>
> Claus Ibsen-2 wrote:
>>
>> On Thu, Dec 3, 2009 at 10:45 AM, kyt <kythary@t-online.de> wrote:
>>>
>>> Hi,
>>>
>>> I need some advice on how to handle an exception in a sub-route and how
>>> the
>>> calling route can continue processing. It is easier to explain this with
>>> a
>>> bit of code:
>>>
>>> from("direct:A")
>>> .to("direct:B")
>>> .to("direct:C");
>>>
>>> from("direct:B")
>>> .onException(Exception.class).handled(true).end()
>>> . code that throws an exception
>>>
>>> from("direct:C")
>>> ...
>>>
>>> Now, if there is an exception in direct:B, direct:C never gets called.
>>> Through debugging I found out that the pipeline in direct:A stops
>>> processing
>>> because it checks an exchange property (Exchange.ERRORHANDLER_HANDLED).
>>> I'm
>>> using Camel 2.0. Is there a way that the processing in direct:A continues
>>> after the exception was handled in direct:B?
>>>
>>
>> Unfortunately the logic for error handling got a bit complex.
>> Something to improve in 2.2. I am currently making the TX based
>> simpler in internal logic.
>>
>> Back to your use case.
>> The doTry .. doCatch will work as regular try .. catch and thus what
>> you would expect so route A will continue
>>
>> In terms on onException we should improve this over time, adding some
>> flag to indicate what you want. As some want to use onException to
>> catch that error and create a custom error messages as reply and thus
>> not process and further. And others as you want a kinda try .. catch
>> logic and just ignore the damn exception.
>>
>>
>>> Thanks,
>>> Jens
>>> --
>>> View this message in context:
>>> http://old.nabble.com/handled-exception-in-sub-route-tp26623326p26623326.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/handled-exception-in-sub-route-tp26623326p26669550.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

camel-example-etl & openJPA (If this is a new instance, make sure any version and/or auto-generated primary key fields are null/default when persisting)

2009-12-07T04:11:19Z

When I try to use the example camel-example-etl with openJPA, here is the
error that I receive

[ Camel thread 0: FileComponent] Tracer INFO
be7ae591-e2ea-4021-8179-d6bdd5f5398c >>> (route1) -->
jpa://org.apache.camel.ex
ample.etl.CustomerEntity?consumeLockEntity=true <<< Pattern:InOnly,
Headers:{CamelFileNameOnly=row2.xml,
CamelFileAbsolutePath=D:\Dvlpt\Java\workspace
\apache-camel-source\examples\camel-example-etl\src\data\row2.xml,
CamelFileRelativePath=row2.xml, CamelFileName=row2.xml,
CamelFilePath=src\data\row2
.xml, CamelFileParent=src\data, CamelFileAbsolute=false,
CamelFileLength=982, CamelFileLastModified=Tue Jul 14 10:37:40 CEST 2009},
BodyType:org.apach
e.camel.example.etl.PersonDocument, Body:<person
user="hiram"><firstName>Hiram</firstName><lastName>Chirino</lastName><city>Tampa</city></person>
16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
12662763, conn 1634627> executing prepstmnt 585058
SELECT t0.id, t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
t0.userName, t0.zip
FROM Customer t0
WHERE (t0.userName = ?)
[params=(String) hiram]
16094 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
12662763, conn 1634627> [0 ms] spent
[ Camel thread 0: FileComponent] CustomerTransformer DEBUG
Created customer: Customer[userName: hiram firstName: Hiram surname:
Chirino]
16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
12662763, conn 21035203> executing prepstmnt 19041450
SELECT t0.city, t0.firstName, t0.phone, t0.street, t0.surname,
t0.userName, t0.zip
FROM Customer t0
WHERE t0.id = ?
[params=(long) 0]
16110 camel TRACE [Camel thread 0: FileComponent] openjpa.jdbc.SQL - <t
12662763, conn 21035203> [0 ms] spent
[ Camel thread 0: FileComponent] DefaultErrorHandler DEBUG Failed
delivery for exchangeId: be7ae591-e2ea-4021-8179-d6bdd5f5398c. On deliver
y attempt: 0 caught:
org.springframework.dao.DataIntegrityViolationException: Attempt to persist
detached object "org.apache.camel.example.etl.Custome
rEntity@8bfa09". If this is a new instance, make sure any version and/or
auto-generated primary key fields are null/default when persisting.; nested
exception is <openjpa-1.3.0-SNAPSHOT-r422266:881892 nonfatal store error>
org.apache.openjpa.persistence.EntityExistsException: Attempt to persist det
ached object "org.apache.camel.example.etl.CustomerEntity@8bfa09". If this
is a new instance, make sure any version and/or auto-generated primary key
fields are null/default when persisting.

Anybody has an idea to avoid this ?

Regards,

Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer

*****************************
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www.linkedin.com/in/charlesmoulliard

Apache Camel Group :
http://www.linkedin.com/groups?home=&gid=2447439&trk=anet_ug_hm

Charles Moulliard
SOA Architect

My Blog : http://cmoulliard.blogspot.com/

Re: cometd client connector for Camel

2009-12-07T01:12:01Z

Hi Claus,

Claus Ibsen-2 wrote:

I have no idea. But we love contributions so if you think you can
improved the camel-cometd component then that would be great.

I tried making my own camel-comet component. The reason I didn't improve cometd because they're technically different (comet-cometd is a server while camel-comet is a client) and I believe cometd uses an older version of cometd/Bayeux, that's not compatible with the new bayeux I'm using.

I need some help though, Claus. The Producer test runs alright, however the Consumer test is not working.

The logs said that the CometConsumer received the messages correctly, however doing processor.process(exchange) seem to do "nothing". I configured the test to route from the comet endpoint to "mock:received", however upon asserts, nothing is received by "mock:received".

Could somebody help me?

The project is here:

http://github.com/ceefour/camel-comet

In order to run the tests, a local cometd server is needed.

Get the `cometd-demo` project here:

http://github.com/ceefour/cometd-demo

Deploy it or install the resulting WAR on your container under `/cometd-demo` context so it's accesible by:

http://localhost:8080/cometd-demo

Run `mvn test` from the `camel-cometd` project to run the tests.

Thank you in advance.

Re: handled exception in sub-route

2009-12-06T23:58:59Z

On Sun, Dec 6, 2009 at 11:25 PM, trivedi kumar b
<Trivedi.Bodlapati@...> wrote:
>
> Hi,
>
> If I use doTry.. doCatch, with similar route that includes transactions,
> will that work as expected? I mean, markRollbackOnly() option inside
> doCatch() will rollback the transaction? Pls let me know the behaviour.
>

Yes markRollbackOnly() is only for transactions and will issue a
status.setRollbackOnly() on the Spring Transaction underneath.
That should render the transaction outcome as rollback only.

It will not tamper with the Exchange by setting an exception as
rollback() does by setting a RollbackException on the Exchange.

> Thanks,
> Trivedi
>
>
> Claus Ibsen-2 wrote:
>>
>> On Thu, Dec 3, 2009 at 10:45 AM, kyt <kythary@...> wrote:
>>>
>>> Hi,
>>>
>>> I need some advice on how to handle an exception in a sub-route and how
>>> the
>>> calling route can continue processing. It is easier to explain this with
>>> a
>>> bit of code:
>>>
>>> from("direct:A")
>>> .to("direct:B")
>>> .to("direct:C");
>>>
>>> from("direct:B")
>>> .onException(Exception.class).handled(true).end()
>>> . code that throws an exception
>>>
>>> from("direct:C")
>>> ...
>>>
>>> Now, if there is an exception in direct:B, direct:C never gets called.
>>> Through debugging I found out that the pipeline in direct:A stops
>>> processing
>>> because it checks an exchange property (Exchange.ERRORHANDLER_HANDLED).
>>> I'm
>>> using Camel 2.0. Is there a way that the processing in direct:A continues
>>> after the exception was handled in direct:B?
>>>
>>
>> Unfortunately the logic for error handling got a bit complex.
>> Something to improve in 2.2. I am currently making the TX based
>> simpler in internal logic.
>>
>> Back to your use case.
>> The doTry .. doCatch will work as regular try .. catch and thus what
>> you would expect so route A will continue
>>
>> In terms on onException we should improve this over time, adding some
>> flag to indicate what you want. As some want to use onException to
>> catch that error and create a custom error messages as reply and thus
>> not process and further. And others as you want a kinda try .. catch
>> logic and just ignore the damn exception.
>>
>>
>>> Thanks,
>>> Jens
>>> --
>>> View this message in context:
>>> http://old.nabble.com/handled-exception-in-sub-route-tp26623326p26623326.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/handled-exception-in-sub-route-tp26623326p26669550.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>

Re: Group of routes and Synchronization on outputs of the group after a split

2009-12-06T23:56:53Z

On Sun, Dec 6, 2009 at 9:03 PM, Seb- <seba.public@...> wrote:

>
> I think there is a small problem with this solution that will make it
> unusable as-is for the case when RecipientList returns dynamic recipient
> list.
> AggregationStrategy uses a predefined static messagecount while
> RecipientList may return a dynamic recipient list at runtime (ie in my
> example a certain message might flow out only through o2 and not o1).
> So the AggregationStrategy would need to update messagecount for certain
> message through all their life in the flow (possibly incrementing when a
> RecipientList throws 2 entries or keep as-is when only 1 entry).
>

No AggregationStrategy does not use a predefined static message count.

If your recipient list returns 1 endpoint, the aggregation will only
be invoked once, to aggregate o1 with the input message.

If your recipient list returns 2 endpoints, the aggregation will be
invoked twice, to aggregate o1 with input message, and then o2 with
the "result from last aggregation".

>
> Seb- wrote:
>>
>> Sounds interesting.
>> I'll have a look at this.
>> Thanks,
>> Sébastien.
>>
>>
>> Claus Ibsen-2 wrote:
>>>
>>> On Sun, Dec 6, 2009 at 6:53 PM, Seb- <seba.public@...> wrote:
>>>>
>>>> Hi,
>>>> Let's say I have 3 components, Component1 is a RecipientList sending the
>>>> message to both Component2 and Component3.
>>>> Is there an easy configuration way for Camel to do a synchronization on
>>>> outputs (o2 & o3) of Component2 & Component3 with the original message
>>>> coming from Component1.
>>>>
>>>> /----[]----- o2
>>>> i1 --[]--/
>>>> \
>>>> \-----[]---- o3
>>>>
>>>
>>> Yes its possible unfortunately we didnt make that possible easily out
>>> of the box until Camel 2.2. You may say that slipped our minds.
>>> The recipient list in 2.2 supports AggregationStrategy so you can
>>> combine the response from o2 and o3 as you like.
>>>
>>> Ticket about it
>>> https://issues.apache.org/activemq/browse/CAMEL-2223
>>>
>>>
>>> See more at, section Using custom AggregationStrategy
>>> http://camel.apache.org/recipient-list.html
>>>
>>> See this thread for how you may work around and with some custom
>>> coding do that in 2.1 or older
>>> http://old.nabble.com/recipientList-multithreading-td26635868.html
>>>
>>>
>>>
>>>
>>>
>>>> Thanks,
>>>> Regards,
>>>> Sébastien.
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/Group-of-routes-and-Synchronization-on-outputs-of-the-group-after-a-split-tp26667241p26667241.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/Group-of-routes-and-Synchronization-on-outputs-of-the-group-after-a-split-tp26667241p26668433.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>

Re: handled exception in sub-route

2009-12-06T14:25:53Z

Hi,

If I use doTry.. doCatch, with similar route that includes transactions, will that work as expected? I mean, markRollbackOnly() option inside doCatch() will rollback the transaction? Pls let me know the behaviour.

Thanks,
Trivedi

Claus Ibsen-2 wrote:

On Thu, Dec 3, 2009 at 10:45 AM, kyt <kythary@t-online.de> wrote:
>
> Hi,
>
> I need some advice on how to handle an exception in a sub-route and how the
> calling route can continue processing. It is easier to explain this with a
> bit of code:
>
> from("direct:A")
> .to("direct:B")
> .to("direct:C");
>
> from("direct:B")
> .onException(Exception.class).handled(true).end()
> . code that throws an exception
>
> from("direct:C")
> ...
>
> Now, if there is an exception in direct:B, direct:C never gets called.
> Through debugging I found out that the pipeline in direct:A stops processing
> because it checks an exchange property (Exchange.ERRORHANDLER_HANDLED). I'm
> using Camel 2.0. Is there a way that the processing in direct:A continues
> after the exception was handled in direct:B?
>

Unfortunately the logic for error handling got a bit complex.
Something to improve in 2.2. I am currently making the TX based
simpler in internal logic.

Back to your use case.
The doTry .. doCatch will work as regular try .. catch and thus what
you would expect so route A will continue

In terms on onException we should improve this over time, adding some
flag to indicate what you want. As some want to use onException to
catch that error and create a custom error messages as reply and thus
not process and further. And others as you want a kinda try .. catch
logic and just ignore the damn exception.

> Thanks,
> Jens
> --
> View this message in context: http://old.nabble.com/handled-exception-in-sub-route-tp26623326p26623326.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

Re: Group of routes and Synchronization on outputs of the group after a split

2009-12-06T12:03:17Z

I think there is a small problem with this solution that will make it unusable as-is for the case when RecipientList returns dynamic recipient list.
AggregationStrategy uses a predefined static messagecount while RecipientList may return a dynamic recipient list at runtime (ie in my example a certain message might flow out only through o2 and not o1).
So the AggregationStrategy would need to update messagecount for certain message through all their life in the flow (possibly incrementing when a RecipientList throws 2 entries or keep as-is when only 1 entry).

Sounds interesting.
I'll have a look at this.
Thanks,
Sébastien.

Claus Ibsen-2 wrote:

On Sun, Dec 6, 2009 at 6:53 PM, Seb- <seba.public@gmail.com> wrote:
>
> Hi,
> Let's say I have 3 components, Component1 is a RecipientList sending the
> message to both Component2 and Component3.
> Is there an easy configuration way for Camel to do a synchronization on
> outputs (o2 & o3) of Component2 & Component3 with the original message
> coming from Component1.
>
> /----[]----- o2
> i1 --[]--/
> \
> \-----[]---- o3
>

Yes its possible unfortunately we didnt make that possible easily out
of the box until Camel 2.2. You may say that slipped our minds.
The recipient list in 2.2 supports AggregationStrategy so you can
combine the response from o2 and o3 as you like.

Ticket about it
https://issues.apache.org/activemq/browse/CAMEL-2223

See more at, section Using custom AggregationStrategy
http://camel.apache.org/recipient-list.html

See this thread for how you may work around and with some custom
coding do that in 2.1 or older
http://old.nabble.com/recipientList-multithreading-td26635868.html

> Thanks,
> Regards,
> Sébastien.
> --
> View this message in context: http://old.nabble.com/Group-of-routes-and-Synchronization-on-outputs-of-the-group-after-a-split-tp26667241p26667241.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

Re: Group of routes and Synchronization on outputs of the group after a split

2009-12-06T11:40:55Z

Sounds interesting.
I'll have a look at this.
Thanks,
Sébastien.

Claus Ibsen-2 wrote:

On Sun, Dec 6, 2009 at 6:53 PM, Seb- <seba.public@gmail.com> wrote:
>
> Hi,
> Let's say I have 3 components, Component1 is a RecipientList sending the
> message to both Component2 and Component3.
> Is there an easy configuration way for Camel to do a synchronization on
> outputs (o2 & o3) of Component2 & Component3 with the original message
> coming from Component1.
>
> /----[]----- o2
> i1 --[]--/
> \
> \-----[]---- o3
>

Yes its possible unfortunately we didnt make that possible easily out
of the box until Camel 2.2. You may say that slipped our minds.
The recipient list in 2.2 supports AggregationStrategy so you can
combine the response from o2 and o3 as you like.

Ticket about it
https://issues.apache.org/activemq/browse/CAMEL-2223

See more at, section Using custom AggregationStrategy
http://camel.apache.org/recipient-list.html

See this thread for how you may work around and with some custom
coding do that in 2.1 or older
http://old.nabble.com/recipientList-multithreading-td26635868.html

> Thanks,
> Regards,
> Sébastien.
> --
> View this message in context: http://old.nabble.com/Group-of-routes-and-Synchronization-on-outputs-of-the-group-after-a-split-tp26667241p26667241.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

Re: Group of routes and Synchronization on outputs of the group after a split

2009-12-06T11:05:43Z

On Sun, Dec 6, 2009 at 6:53 PM, Seb- <seba.public@...> wrote:

>
> Hi,
> Let's say I have 3 components, Component1 is a RecipientList sending the
> message to both Component2 and Component3.
> Is there an easy configuration way for Camel to do a synchronization on
> outputs (o2 & o3) of Component2 & Component3 with the original message
> coming from Component1.
>
> /----[]----- o2
> i1 --[]--/
> \
> \-----[]---- o3
>

Yes its possible unfortunately we didnt make that possible easily out
of the box until Camel 2.2. You may say that slipped our minds.
The recipient list in 2.2 supports AggregationStrategy so you can
combine the response from o2 and o3 as you like.

Ticket about it
https://issues.apache.org/activemq/browse/CAMEL-2223

See more at, section Using custom AggregationStrategy
http://camel.apache.org/recipient-list.html

See this thread for how you may work around and with some custom
coding do that in 2.1 or older
http://old.nabble.com/recipientList-multithreading-td26635868.html

> Thanks,
> Regards,
> Sébastien.
> --
> View this message in context: http://old.nabble.com/Group-of-routes-and-Synchronization-on-outputs-of-the-group-after-a-split-tp26667241p26667241.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

Group of routes and Synchronization on outputs of the group after a split

2009-12-06T09:53:33Z

Hi,
Let's say I have 3 components, Component1 is a RecipientList sending the message to both Component2 and Component3.
Is there an easy configuration way for Camel to do a synchronization on outputs (o2 & o3) of Component2 & Component3 with the original message coming from Component1.

/----[]----- o2
i1 --[]--/
\
\-----[]---- o3

Thanks,
Regards,
Sébastien.

Re: Implementing Publish Subscribe Channel

2009-12-06T09:50:26Z

Hi Claus,

Claus Ibsen-2 wrote:

No seda does *not* support multiple consumers. Its meant to be used
with a single consumer only.
In 2.1 this is even enforced. Often end users had copy paste mistakes
and didnt want multiple consumers to the same seda endpoint.
Hence why we enforced this now in 2.1.

What is your use case sine you need this? I am interesting in what you
are trying to solve?

What you could do is to extend seda, and have support multiple
consumers and have the Exchange being copied before its handed out to
every
consumers.

Mind that when you copy the Exchange / Message if the body is not a
simple type such as String then you may only copy a reference to it
and thus have multiple consumers work on it concurrently, and thus you
need to be aware of thread safety issues.

And there is a new interface in Camel 2.1, MultipleConsumersSupport,
which indicates whether an endpoint supports multiple consumers or
not.
You need to implement this and return true in your own component.

I'm not sure if a separate component is needed for this, because from my experience the <multicast> element works fine. And that's what I'm trying to get, using the <multicast> functionality in a @Consume'r.

Maybe something like this (proposal):

@Consume(uri="someuri", multicast=true)

My use case is using Camel as event publisher. Exactly like Spring Application Events.

@EndpointInject(uri="seda:events.form")
ProducerTemplate formEvents;

...
formEvents.sendBody(new FormEvent(...));
...

then there are one or more event Listeners like this:

@Consume(uri="seda:events.form")
public void handleFormEvent(FormEvent event) { ... }

BTW, the producer and consumer URI may not be the same. i.e. the publisher of the event may route it in some way and there may be multiple producers. However as far as consumers are concerned, they have this inbox URI (e.g. "seda:events.form") that all events will come together. Then multiple consumers can process the messages (it's InOnly, no need to reply).

I can do this with <multicast>, but my "problem" is that I want it to be "dynamic" i.e. just @Consume annotation is needed, no change in routes. Because the consumers can be created and disposed dynamically.

Re: Implementing Publish Subscribe Channel

2009-12-06T08:13:30Z

On Sun, Dec 6, 2009 at 4:51 PM, Hendy Irawan <hendy@...> wrote:

>
>
>
> Claus Ibsen-2 wrote:
>>
>> Maybe spring event can be used also?
>> http://camel.apache.org/event.html
>>
>
> I guess that'd mean my message has to be an ApplicationEvent.
>

Dont know if Spring enforces to implement an interface but I would
envision they did.

>
> Claus Ibsen-2 wrote:
>>
>> You can create you own component that offers topic like functionally.
>> You could extend the seda or direct component and implement the logic
>> missing.
>>
>
> Thanks for the encouragement. :-)
>
>
> Claus Ibsen-2 wrote:
>>
>> I would assume adding @Consume to any POJO does not require any routes
>> to pre existing and cannot see why its not dynamic.
>>
>
> Yes indeed, unfortunately @Consume breaks when there are two @Consume'rs on
> the same endpoint that is not a publish-subscribe channel. It seems like
> it's doing round-robin (?) instead of multicast.
>
> For example, I'd like:
>
> /* bean1 */
> @Consume("seda:mychannel") public void Yeeha(String msg) { }
> /* bean2 */
> @Consume("seda:mychannel") public void Yaahi(String msg) { }
>
> to behave as if an explicit route is specified (with multicast):
>
> <from uri="seda:channel">
> <multicast>
> <to uri="bean:bean1" />
> <to uri="bean:bean2" />
> </multicast>
> </from>
>
> but right now, it seems messages are being routed round-robin when using the
> @Consumer. That's why I said doing multicast dynamically (with @Consume)
> seem to be not possible.
>

No seda does *not* support multiple consumers. Its meant to be used
with a single consumer only.
In 2.1 this is even enforced. Often end users had copy paste mistakes
and didnt want multiple consumers to the same seda endpoint.
Hence why we enforced this now in 2.1.

What is your use case sine you need this? I am interesting in what you
are trying to solve?

What you could do is to extend seda, and have support multiple
consumers and have the Exchange being copied before its handed out to
every
consumers.

Mind that when you copy the Exchange / Message if the body is not a
simple type such as String then you may only copy a reference to it
and thus have multiple consumers work on it concurrently, and thus you
need to be aware of thread safety issues.

And there is a new interface in Camel 2.1, MultipleConsumersSupport,
which indicates whether an endpoint supports multiple consumers or
not.
You need to implement this and return true in your own component.

> Thank you.
> --
> View this message in context: http://old.nabble.com/Implementing-Publish-Subscribe-Channel-tp26654086p26666101.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

Re: Camel source not available -- Re: cometd client connector for Camel

2009-12-06T08:03:39Z

On Sun, Dec 6, 2009 at 4:54 PM, Hendy Irawan <hendy@...> wrote:

>
>
> Claus Ibsen-2 wrote:
>>
>> I have no idea. But we love contributions so if you think you can
>> improved the camel-cometd component then that would be great.
>>
>
> Thanks Claus, I guess that's the only logical action I should take.
>
> Trying to download Camel source though gives me 404 error:
>
> http://www.apache.org/dist/camel/apache-camel/2.1.0/apache-camel-2.1.0-src.tar.gz
>
> Brings me:
>
> Not Found
>
> The requested URL
> /dist/camel/apache-camel/2.1.0/apache-camel-2.1.0-src.tar.gz was not found
> on this server.
> Apache/2.3.4 (Unix) mod_fcgid/2.3.2-dev Server at www.apache.org Port 80
>

See this topic
http://old.nabble.com/2.1-release-download-td26658552.html

> --
> View this message in context: http://old.nabble.com/cometd-client-connector-for-Camel-tp26635861p26666122.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