users@camel.apache.org Archives

Re: handled exception in sub-route

2009-12-06T22:25:56Z


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  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-06T20: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).


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-  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: Group of routes and Synchronization on outputs of the group after a split

2009-12-06T19:40:56Z


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-  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-tp26667241p26668227.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-06T19:05:43Z

On Sun, Dec 6, 2009 at 6:53 PM, Seb-  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-06T17: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.
-- 
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.

Re: Implementing Publish Subscribe Channel

2009-12-06T17:50:27Z


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  element works fine. And that's what I'm trying to
get, using the  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 , 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: Implementing Publish Subscribe Channel

2009-12-06T16:13:30Z

On Sun, Dec 6, 2009 at 4:51 PM, Hendy Irawan  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):
>
> 
> 
> �
> �
> 
> 
>
> 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-06T16:03:39Z

On Sun, Dec 6, 2009 at 4:54 PM, Hendy Irawan  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

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

2009-12-06T15:54:19Z

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

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

Re: Implementing Publish Subscribe Channel

2009-12-06T15:51:36Z

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.

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

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.

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.

Re: Implementing Publish Subscribe Channel

2009-12-06T11:58:00Z

On Sat, Dec 5, 2009 at 10:31 AM, Hendy Irawan  wrote:
>
> Hi,
>
> I was trying to make a publish-subscribe mechanism by using (only)
> @EndpointInject and @Consume, so that I can have somewhat POJO style routing
> with minimal XML configuration.
>
> It turned out that this didn't work because multiple consumers don't work
> with this setup.
>
> After reading http://camel.apache.org/publish-subscribe-channel.html it
> seems that there are only three ways Camel supports Publish Subscribe:
> 1. JMS Topic
> 2. XMPP Room
> 3. Explicit routes via multicast
>
> Option 1 and 2 is overkill because it requires external server.
>

Maybe spring event can be used also?
http://camel.apache.org/event.html


> So the functionality is basically there in Camel (option 3), however, I
> cannot do it dynamically because it involves explicitly setting up the
> routes, instead of doing it dynamically via @Consume.
>

You can create you own component that offers topic like functionally.
You could extend the seda or direct component and implement the logic
missing.


> Spring Integration seem to support this by allowing to create a
> PublishSubscribeChannel explicitly.
>
> Is it planned to support easy "dynamic" Publish Subscribe Channel via
> annotations (i.e. without explicit configuration)? Thank you.

I would assume adding @Consume to any POJO does not require any routes
to pre existing and cannot see why its not dynamic.


Why dont you create a small sample what you want as its easier to
discuss based on that.

And we love contributions
http://camel.apache.org/contributing.html

Just see Camel 2.1 which have 5 or so new components all contributed by others.


> --
> View this message in context: http://old.nabble.com/Implementing-Publish-Subscribe-Channel-tp26654086p26654086.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: Webdav or Apache VFS components?

2009-12-06T11:53:41Z

On Sat, Dec 5, 2009 at 12:37 AM, boden  wrote:
>
> It doesn't look like there is a WebDAV component or more advanced file system
> component such as VFS.
>
> If I want to talk to WebDAV or arbitrary network shares, what are my options
> with Camel?
>

No a commons-vfs was in the works but it got stalled. I wonder if
commons-vfs is still maintained?
Anyway do you know any good libraries to work with WebDAV?

Otherwise Camel only has the regular file and ftp components


> Thanks!
> --
> View this message in context: http://old.nabble.com/Webdav-or-Apache-VFS-components--tp26648008p26648008.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: cometd client connector for Camel

2009-12-06T11:52:06Z

Hi

On Fri, Dec 4, 2009 at 12:42 PM, Hendy Irawan  wrote:
>
> I'm working with cometd on my current project and tried to use Camel-cometd.
>
> However, it seems that Camel sets up its own cometd server.
>
> What I'd like to do is connect to an existing cometd server, so the Camel
> app acts as a cometd/Bayeux client. Now I'm doing this with cometd.org's
> java-client and doing pretty well.
>
> But if anyone has any ideas how to make integration for this with Camel I'd
> be more than happy to know. I don't know how to create a Camel connector.
>

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


> Thank you.
> --
> View this message in context: http://old.nabble.com/cometd-client-connector-for-Camel-tp26635861p26635861.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: 2.1 release download

2009-12-06T07:26:33Z

On Sat, Dec 5, 2009 at 8:41 PM, lujan99  wrote:
>
> I can't found any link with the distribution.
> (I checked many mirrors)

Yeah I guess it takes time for Apache mirrors to sync.

You can find it in the central maven repo
http://repo1.maven.org/maven2/org/apache/camel/apache-camel/2.1.0/


> --
> View this message in context: http://old.nabble.com/2.1-release-download-tp26658552p26658552.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

2.1 release download

2009-12-05T19:41:58Z


I can't found any link with the distribution.
(I checked many mirrors)
-- 
View this message in context: http://old.nabble.com/2.1-release-download-tp26658552p26658552.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Implementing Publish Subscribe Channel

2009-12-05T09:31:08Z


Hi,

I was trying to make a publish-subscribe mechanism by using (only)
@EndpointInject and @Consume, so that I can have somewhat POJO style routing
with minimal XML configuration.

It turned out that this didn't work because multiple consumers don't work
with this setup.

After reading http://camel.apache.org/publish-subscribe-channel.html it
seems that there are only three ways Camel supports Publish Subscribe:
1. JMS Topic
2. XMPP Room
3. Explicit routes via multicast

Option 1 and 2 is overkill because it requires external server.

So the functionality is basically there in Camel (option 3), however, I
cannot do it dynamically because it involves explicitly setting up the
routes, instead of doing it dynamically via @Consume.

Spring Integration seem to support this by allowing to create a
PublishSubscribeChannel explicitly.

Is it planned to support easy "dynamic" Publish Subscribe Channel via
annotations (i.e. without explicit configuration)? Thank you.
-- 
View this message in context: http://old.nabble.com/Implementing-Publish-Subscribe-Channel-tp26654086p26654086.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: [ANNOUNCE] Apache Camel 2.1.0 Release

2009-12-05T09:26:09Z


Thank you Hadrian!

Sorry for the simple message, but I'm really proud of you guys for your
excellent work.

Hendy


hzbarcea wrote:
> 
> After a bit over three months of hard work we are pleased to introduce  
> the Apache Camel 2.1.0 Release [1]. This is another major effort  
> featuring an impressive 303 issues resolved. The Camel community is  
> growing at a faster pace and we see a lot of involvement and  
> contributions.
> ...
> [1] http://camel.apache.org/camel-210-release.html
> 
-- 
View this message in context: http://old.nabble.com/-ANNOUNCE--Apache-Camel-2.1.0-Release-tp26647803p26654057.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: recipientList multithreading

2009-12-05T08:26:48Z

On Sat, Dec 5, 2009 at 9:20 AM, mcrive  wrote:
>
> Nice one.
> Can you suggest a way to achieve what I need to do with Camel 2.1?
>
>

1)
Yeah you could send them message yourself from a processor / bean and
use the producerTemplate which has an async variation

See more at
http://camel.apache.org/async


2)
Or create your own recipient list processor which is inspired by the
code changes committed.
You just extend the existing recipient list, override the method that
leverages the MulticastProcessor where you indicate true for parallel.

And then use it just as a regular processor

from(x).to(new MyPrallelRecipientList());




>
> Claus Ibsen-2 wrote:
>>
>> No but we got a ticket for it
>> https://issues.apache.org/activemq/browse/CAMEL-2223
>>
>> And its possible to implement as the underlying logic supports it - so
>> its merely just to expose the settings.
>> We should get that into Camel 2.2 then :)
>>
>
> --
> View this message in context: http://old.nabble.com/recipientList-multithreading-tp26635868p26653717.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: recipientList multithreading

2009-12-05T08:20:56Z


Nice one.
Can you suggest a way to achieve what I need to do with Camel 2.1?



Claus Ibsen-2 wrote:
> 
> No but we got a ticket for it
> https://issues.apache.org/activemq/browse/CAMEL-2223
> 
> And its possible to implement as the underlying logic supports it - so
> its merely just to expose the settings.
> We should get that into Camel 2.2 then :)
> 

-- 
View this message in context: http://old.nabble.com/recipientList-multithreading-tp26635868p26653717.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Webdav or Apache VFS components?

2009-12-04T23:37:53Z


It doesn't look like there is a WebDAV component or more advanced file system
component such as VFS.

If I want to talk to WebDAV or arbitrary network shares, what are my options
with Camel?

Thanks!
-- 
View this message in context: http://old.nabble.com/Webdav-or-Apache-VFS-components--tp26648008p26648008.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Errors parsing camel-context.xml

2009-12-04T23:14:23Z


@william, @Claus
Thank you for these tips.  I have solved part of this issue.  I did need to
change the element to 

However, I am still getting the same type of error on the
 element.  I took this example from the camel
tutorial (pt 2).



Looking at the online XSD
(http://www.springframework.org/schema/context/spring-context.xsd) There is
no listing for "placeholderPrefix"or "placeholderSuffix".  Which leads me to
the belief the tutorial is using a different schema.  Any idea which one?

I am using Karaf 1.0.0, Camel 2.0, Spring 2.5.6.SEC01

-pete

p.s. I am guessing that the tutorial assumed a ServiceMix 4.0 installation.
I have successfully gotten Camel/ActiveMQ/Hibernate/etc working in
out-of-box Karaf 1.0 and my feature file looks fairly different than the
tutorial.   I'd be happy to share it with those interested, or attach it to
the tutorial, if someone would enlighten me on the best way to do that.



Claus Ibsen-2 wrote:
> 
> On Fri, Dec 4, 2009 at 2:25 AM, Willem Jiang 
> wrote:
>> Which version of ServiceMix are you using?
>> Can you past your camel-context file?
>>
>> Maybe you are not using a right version of camel-spring schema ?
>>
> 
> Yeah I think some of the data formats got cleaned up in 2.1. And json
> could very well be one of them.
> So make sure to use the XSD version that matches the version of Camel.
> 
> And beware some IDE tools will use the online XSD which is SNAPSHOT based.
> You should really use the XSD which is located in camel-spring.jar you
> are using.
> 
> 
> What you can always do is to declare the data format in the top
> 
> 
>    
> 
> 
> And then refer to it in the route
> 
> 
> 
> 
>> Willem
>>
>> Pete Mueller wrote:
>>>
>>> Hello,
>>> I am receiving the following error trying to start up my camel routing
>>> bundle with a camel-context.xml in it.
>>> The error is:
>>> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException:
>>> Line
>>> 16 in XML document from URL
>>> [bundle://135.0:0/META-INF/spring/camel-context.xml] is invalid; nested
>>> exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.a:
>>> Invalid
>>> content was found starting with element 'json'. One of
>>> '{"http://camel.apache.org/schema/spring":artixDS,
>>> "http://camel.apache.org/schema/spring":bindy,
>>> "http://camel.apache.org/schema/spring":csv,
>>> "http://camel.apache.org/schema/spring":flatpack,
>>> "http://camel.apache.org/schema/spring":gzip,
>>> "http://camel.apache.org/schema/spring":hl7,
>>> "http://camel.apache.org/schema/spring":jaxb,
>>> "http://camel.apache.org/schema/spring":json,
>>> "http://camel.apache.org/schema/spring":rss,
>>> "http://camel.apache.org/schema/spring":secureXML,
>>> "http://camel.apache.org/schema/spring":serialization,
>>> "http://camel.apache.org/schema/spring":string,
>>> "http://camel.apache.org/schema/spring":tidyMarkup,
>>> "http://camel.apache.org/schema/spring":xmlBeans,
>>> "http://camel.apache.org/schema/spring":xstream,
>>> "http://camel.apache.org/schema/spring":zip}' is expected.
>>>
>>> Clearly from the error, it shows that "json" is an allowed element. but
>>> SAX
>>> says otherwise.  Any idea how to reconcile this?  I have a similar error
>>> with using the placeholderPrefix attribute inside a property-placeholder
>>> element.
>>>
>>> Thanks,
>>> -p
>>>
>>> Here are relevant portions of my camel-context.xml if it helps.  I
>>> thought
>>> perhaps I'm using the wrong schema.
>>> 
>>> >>        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>> xmlns:context="http://www.springframework.org/schema/context"
>>>        xmlns:osgi="http://www.springframework.org/schema/osgi"
>>> xmlns:osgix="http://www.springframework.org/schema/osgi-compendium"
>>>        xmlns:camel="http://camel.apache.org/schema/spring"
>>>
>>>        xsi:schemaLocation="http://www.springframework.org/schema/beans
>>> http://www.springframework.org/schema/beans/spring-beans.xsd
>>>                http://www.springframework.org/schema/context
>>> http://www.springframework.org/schema/context/spring-context.xsd
>>>                http://www.springframework.org/schema/osgi
>>> http://www.springframework.org/schema/osgi/spring-osgi.xsd
>>>                http://www.springframework.org/schema/osgi-compendium
>>>
>>> http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd
>>>                http://camel.apache.org/schema/spring
>>> http://camel.apache.org/schema/spring/camel-spring.xsd">
>>>
>>>        >> placeholderPrefix="#{" placeholderSuffix="}" />
>>>                  >> library="Jackson"
>>> unmarshalTypeName="com.routecloud.bean.Message" />
>>>  
>>>
>>> ...
>>
>>
> 
> 
> 
> -- 
> 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/Errors-parsing-camel-context.xml-tp26635732p26646469.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Best Practices for Triggering Routes from Code

2009-12-04T22:21:00Z


Actually, I wanted to know how to start it from the same jvm using OSGi. Any
thoughts on this?

/Ron


Claus Ibsen-2 wrote:
> 
> On Fri, Dec 4, 2009 at 5:45 AM, rgavlin  wrote:
>>
>> Hi Claus,
>>
>> Let's say I have a camel route that begins with from("nmr:...") deployed
>> as
>> an OSGi bundle in the upcoming SMX 4.1. Within a Camel route in another
>> OSGi
>> bundle I would like to lookup and then start the first route. Is it
>> possible
>> to use the OSGi Registry to perform such a lookup? If yes, do you have
>> any
>> examples of doing so?
>>
> 
> Not out of the box as staring a route is done from the CamelContext
> and thus you need to do that using the CamelContext which owns the
> route.
> So starting from another JVM is not possible.
> 
> You can however use JMX to do this as you can invoke operations from
> one JVM to another.
> 
> You could use a JMS topic that each CamelContext has a build in route
> who listen on and then you can send "commands" to all or specific
> camel contexts.
> And maybe in the future we could add such a feature to Camel itself.
> As it probably makes sense to manage such routes / flows more dynamic
> and without the hazzle from JMX.
> 
> 
> 
>> Thanks,
>>
>> /Ron
>>
>>
>>
>> Claus Ibsen-2 wrote:
>>>
>>> On Thu, Dec 3, 2009 at 1:32 AM, mumbly  wrote:
>>>>
>>>> I'm talking about on demand triggering. Basically, I want to be able to
>>>> trigger a route programatically from within my code. I'm using quartz
>>>> already for certain batch processing. I'm just trying to understand how
>>>> the
>>>> items I listed differ, whether they are the set you'd want to use for
>>>> on
>>>> demand triggering and whether the ProducerTemplate is the right way to
>>>> go
>>>> about that.
>>>>
>>>
>>> Its easier in 2.1 as you can create routes which aren't started when
>>> Camel starts
>>> http://camel.apache.org/configuring-route-startup-ordering-and-autostartup.html
>>>
>>> And you can assign the route an id using .routeId in Java DSL or just
>>> "id" attribute in XML.
>>>
>>> Then you can manually start that route from JMX, Java code etc.
>>>
>>> CamelContext context = ...
>>>
>>> context.startRoute("theIdOfYourRoute");
>>>
>>> context.stopRoute("theIdOfYourRoute");
>>>
>>>
>>>
>>>
>>>> --Tim
>>>>
>>>>
>>>> Dragisa Krsmanovic wrote:
>>>>>
>>>>> It depends what you mean by 'triggering'.
>>>>>
>>>>> If you want to automatically send a message to a queue at specific
>>>>> intervals you can use Quartz component.
>>>>>
>>>>> For example, to send a "Hello World" message every 3 minutes:
>>>>>
>>>>> from("quartz://myCron?cron=0+0/3+*+*+*+?")
>>>>> .setBody(constant("Hello World"))
>>>>> .to(destination);
>>>>>
>>>>> Where destination can be anything ("direct:myQueue",
>>>>> "activemq:myQueue"
>>>>> etc.)
>>>>>
>>>>>
>>>>>
>>>>> On Wed, 2009-12-02 at 14:00 -0800, mumbly wrote:
>>>>>> While many of our processes are triggered by some external event
>>>>>> (timer,
>>>>>> file
>>>>>> transfers, emails, web/REST/SOAP requests), there are a number of
>>>>>> instances
>>>>>> where we want to trigger a route from within our code. I'm trying
to
>>>>>> understand how Camel allows me to do this and what the recommended
>>>>>> practices/patterns for this type of interaction are.
>>>>>>
>>>>>> I see a handful of components which seem like they would meet the
>>>>>> criteria
>>>>>> for trigger, but I'm not clear on which I should use. Basically I'm
>>>>>> looking
>>>>>> at:
>>>>>>
>>>>>> * direct
>>>>>> * jms
>>>>>> * seda
>>>>>> * vm
>>>>>>
>>>>>> It seems to me like they are similar, but it is unclear which are
>>>>>> best
>>>>>> under
>>>>>> what conditions. Is there some document comparing the pros and cons
>>>>>> and
>>>>>> potential use cases for these transports in non-test circumstances?
>>>>>>
>>>>>> And is the general pattern of direct triggering to use a
>>>>>> ProducerTemplate?
>>>>>> It felt a bit like this was mainly for testing, but I don't see other
>>>>>> methods used in the examples (or for that matter, I don't recall
>>>>>> seeing
>>>>>> ProducerTemplate in non-test code, though I haven't searched too
>>>>>> closely).
>>>>>>
>>>>>> Basically, just trying to get some guidance as to the recommended
>>>>>> practice.
>>>>>>
>>>>>> Thanks.
>>>>>>
>>>>>> --Tim
>>>>>
>>>>>
>>>>> --
>>>>> Dragisa Krsmanovic
>>>>> Java Developer
>>>>> Public Library of Science
>>>>> http://www.plos.org
>>>>>
>>>>>
>>>>> --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>>>>> This email is confidential to the intended recipient. If you have
>>>>> received
>>>>> it in error, please notify the sender and delete it from your system.
>>>>> Any
>>>>> unauthorized use, disclosure or copying is not permitted. The views or
>>>>> opinions presented are solely those of the sender and do not
>>>>> necessarily
>>>>> represent those of Public Library of Science unless otherwise
>>>>> specifically
>>>>> stated. Please note that neither Public Library of Science nor any of
>>>>> its
>>>>> agents accept any responsibility for any viruses that may be contained
>>>>> in
>>>>> this e-mail or its attachments and it is your responsibility to scan
>>>>> the
>>>>> e-mail and attachments (if any).
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/Best-Practices-for-Triggering-Routes-from-Code-tp26617252p26619145.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/Best-Practices-for-Triggering-Routes-from-Code-tp26617252p26635764.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/Best-Practices-for-Triggering-Routes-from-Code-tp26617252p26642545.html
Sent from the Camel - Users mailing list archive at Nabble.com.

[ANNOUNCE] Apache Camel 2.1.0 Release

2009-12-04T19:20:56Z

After a bit over three months of hard work we are pleased to introduce  
the Apache Camel 2.1.0 Release [1]. This is another major effort  
featuring an impressive 303 issues resolved. The Camel community is  
growing at a faster pace and we see a lot of involvement and  
contributions.

The feature and improvements list is too large to fit here, so please  
check out the release notes. Most notable changes are:

	� Claus was very busy with a serious Camel JMX overhaul, including a  
pluggable management API to allow 3rd party tools.
	� Improvements for using Camel in OSGi environments
	� A bunch of new components contributed by the community such as
		� Printer very handy to batch print those reports overnight
		� SNMP gives you the capability to poll SNMP capable devices or  
receive traps.
		� GAE provides connectivity to the cloud computing services provided  
by Googls's App Engine
	� Improvements in error handling
	� As usual, a lot of fixes and enhancement of the 70+ Components
Many thanks and our gratitude to all the contributors who made this  
release possible. Download Camel now and enjoy the ride!

The Camel Riders


[1] http://camel.apache.org/camel-210-release.html

Re: Free Fuse day - talks on Apache ActiveMQ, ServiceMix and Camel

2009-12-04T18:04:57Z

Yay!  Just found out I'll be attending the San Francisco event!

Anyone else able to make it out?


On Mon, Nov 30, 2009 at 7:24 AM, Rob Davies  wrote:
>
> If any folks are in New York on December 8th or near San Francisco on
> December 10th - there is a free Community day sponsored by Fuse Source -
> with talks on Apache ServiceMix, ActiveMQ and Camel.
> If you'd like to attend - you need to register - its all free and includes
> lunch. If you can't make it - James Strachan and myself will no doubt be
> found in a local bar afterwards - so why not pop by for a chat and a beer.
> Not being local, suggestions are welcome :)
>
> To register for the New York �event (Hyatt Hotel next to Grand Central) on
> December 8th - go here: http://form.fusesource.com/forms/registerny2009
> To register for the San Francisco event (Hyatt Hotel next to the er, Airport
> :( ) �on December 10th - go here:
> http://form.fusesource.com/forms/registersf2009
>
> cheers,
>
> Rob
>
> Rob Davies
> http://twitter.com/rajdavies
> I work here: http://fusesource.com
> My Blog: http://rajdavies.blogspot.com/
> I'm writing this: http://www.manning.com/snyder/
>
>
>
>
>
>



-- 
Regards,
Hiram

Blog: http://hiramchirino.com

Open Source SOA
http://fusesource.com/

Re: NullPointerException in FileComponent

2009-12-04T17:23:05Z



Claus Ibsen-2 wrote:
> 
> And you are sure your bean does not throw a NPE exception?
> 
> But yeah without a stacktrace or any more detailed logging its hard to
> work out.
> 

I actually got a stack trace this time:

[2009-12-04 01:46:53,105][WARN][Thread: 1
org.apache.camel.component.file.FileComponent@1c04f13][camel.impl.ScheduledPollConsumer(ScheduledPollConsumer)-run(68)]:
An exception occured while polling:
Endpoint[file:data/input?consumer.recursive=false&lock=true&consumer.exclusiveReadLock=true&noop=true]:
null
java.lang.NullPointerException
    at
org.apache.camel.component.file.FileConsumer.pollFileOrDirectory(FileConsumer.java:99)
    at
org.apache.camel.component.file.FileConsumer.poll(FileConsumer.java:66)
    at
org.apache.camel.impl.ScheduledPollConsumer.run(ScheduledPollConsumer.java:66)
    at etc...

however, a few lines before that, I got a:
Caused by: java.io.IOException: Too many open files

from a different exception.  So, it's not really a camel bug, although the
error from camel is a bit misleading.

btw, the code around line 99 is
            if (isValidFile(fileOrDirectory)) {
                if (LOG.isTraceEnabled()) {
                    LOG.trace("Polling directory " + fileOrDirectory);
                }
                File[] files = fileOrDirectory.listFiles();
                for (File file : files) {                         <------
line 99
                    rc += pollFileOrDirectory(file, isRecursive()); //
self-recursion
                }
            }

listFiles() is defined to return null is some cases.  Camel 2.0 has an
explicit check for that, and just silently returns.

eric
-- 
View this message in context: http://old.nabble.com/NullPointerException-in-FileComponent-tp26594231p26636156.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: recipientList multithreading

2009-12-04T16:49:01Z

On Fri, Dec 4, 2009 at 1:09 PM, Claus Ibsen  wrote:
> On Fri, Dec 4, 2009 at 1:02 PM, mcrive  wrote:
>>
>> Is there a way to make the recipientList to send to endpoint in a multi
>> thread manner?
>> for instance if it contains a list of FTP endpoint (producer) I would like
>> to deploy files at the same time.
>> as it is implemented now it starts producing the 2nd as the 1st is completed
>> --
>
> No but we got a ticket for it
> https://issues.apache.org/activemq/browse/CAMEL-2223
>

Hi

I have implemented this and committed to trunk.
Will thus be included in Camel 2.2.
svn rev: 887262.


The wiki page
http://camel.apache.org/recipient-list.html

Has been updated but it takes a couple of hours for it to be synced.

You are welcome to try 2.2-SNAPSHOT and see for yourself.
http://camel.apache.org/download.html




> And its possible to implement as the underlying logic supports it - so
> its merely just to expose the settings.
> We should get that into Camel 2.2 then :)
>
>
>> View this message in context: http://old.nabble.com/recipientList-multithreading-tp26635868p26635868.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
>



-- 
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: Jersey No Longer Supported?

2009-12-04T16:39:37Z

The component http://camel.apache.org/web-console.html has been designed
around jersey implementation of JAX-RS

As you mention camel-cxf is based on CXF and camel-restlet on RESTlet

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 Fri, Dec 4, 2009 at 5:29 PM, mumbly  wrote:

>
> I'm a bit confused as to whether Jersey is currently supported for REST.
> I've
> seen indications that it was supported at some point from searches I've
> made, but it looks like there are only camel-cxf and camel-restlet
> components currently in the lineup. Did Jersey support get deprecated? Was
> it never really there?
>
> Thanks.
>
> --Tim
> --
> View this message in context:
> http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26635942.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>

Jersey No Longer Supported?

2009-12-04T16:29:08Z


I'm a bit confused as to whether Jersey is currently supported for REST. I've
seen indications that it was supported at some point from searches I've
made, but it looks like there are only camel-cxf and camel-restlet
components currently in the lineup. Did Jersey support get deprecated? Was
it never really there?

Thanks.

--Tim
-- 
View this message in context: http://old.nabble.com/Jersey-No-Longer-Supported--tp26635942p26635942.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Question about camel-jpa and camel-etl

2009-12-04T12:20:55Z

I have found a workaround by adding this in the spring config file, it works

    
    
           
    


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 Fri, Dec 4, 2009 at 1:11 PM, Claus Ibsen  wrote:

> Hi
>
> Why dont you try to fix it yourself? Maybe its just a matter of adding
> that factory to the configuration.
>
>
> On Fri, Dec 4, 2009 at 11:05 AM, Charles Moulliard 
> wrote:
> > In the wiki page of camel-jpa component, it is mentioned that a
> > entityManagerFactory must be specified like this :
> >
> > 
> >   
> > 
> >
> >
> > Surprisingly, I don't see this in the camel-example-etl example.
> >
> > When deploying camel-example-etl on Apache Felix Karaf, felix complains
> that
> > :
> >
> > Caused by: java.lang.IllegalArgumentException: entityManagerFactory must
> be
> > specified
> >    at org.apache.camel.util.ObjectHelper.notNull(ObjectHelper.java:244)
> >    at
> > org.apache.camel.component.jpa.JpaEndpoint.validate(JpaEndpoint.java:230)
> >    at
> >
> org.apache.camel.component.jpa.JpaEndpoint.createConsumer(JpaEndpoint.java:87)
> >
> > 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: Two routes with InOut - jms ??

2009-12-04T12:12:10Z

Use tracer and check what the JMSReplyTo is set to. It should be InOut MEP.

On Wed, Dec 2, 2009 at 5:10 PM, Charles Moulliard  wrote:
> The following route works fine :
>
> � � class="org.apache.camel.example.reportincident.restful.ReportIncidentService"
> />
> � � class="org.apache.camel.example.reportincident.routing.RestFullProcessor"/>
>
> � �
> serviceClass="org.apache.camel.example.reportincident.restful.ReportIncidentService"
> />
>
> � � � � � �xmlns="http://camel.apache.org/schema/osgi">
>
> � � � �
> � � � � � �
> � � � � � �
> � � � �
> � �
>
> but when I try to use in between a jms queue the exchange.getOut().setBody()
> defined in the method processRequest is never returned to the camel cxfrs
> endpoint
>
> � � � �
> � � � � � �
> � � � � � �
> � � � �
>
> � � � �
> � � � � � �
> � � � � � �
> � � � �
>
> 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: Question about camel-jpa and camel-etl

2009-12-04T12:11:28Z

Hi

Why dont you try to fix it yourself? Maybe its just a matter of adding
that factory to the configuration.


On Fri, Dec 4, 2009 at 11:05 AM, Charles Moulliard  wrote:
> In the wiki page of camel-jpa component, it is mentioned that a
> entityManagerFactory must be specified like this :
>
> 
> � 
> 
>
>
> Surprisingly, I don't see this in the camel-example-etl example.
>
> When deploying camel-example-etl on Apache Felix Karaf, felix complains that
> :
>
> Caused by: java.lang.IllegalArgumentException: entityManagerFactory must be
> specified
> � �at org.apache.camel.util.ObjectHelper.notNull(ObjectHelper.java:244)
> � �at
> org.apache.camel.component.jpa.JpaEndpoint.validate(JpaEndpoint.java:230)
> � �at
> org.apache.camel.component.jpa.JpaEndpoint.createConsumer(JpaEndpoint.java:87)
>
> 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: recipientList multithreading

2009-12-04T12:09:50Z

On Fri, Dec 4, 2009 at 1:02 PM, mcrive  wrote:
>
> Is there a way to make the recipientList to send to endpoint in a multi
> thread manner?
> for instance if it contains a list of FTP endpoint (producer) I would like
> to deploy files at the same time.
> as it is implemented now it starts producing the 2nd as the 1st is completed
> --

No but we got a ticket for it
https://issues.apache.org/activemq/browse/CAMEL-2223

And its possible to implement as the underlying logic supports it - so
its merely just to expose the settings.
We should get that into Camel 2.2 then :)


> View this message in context: http://old.nabble.com/recipientList-multithreading-tp26635868p26635868.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

recipientList multithreading

2009-12-04T12:02:45Z


Is there a way to make the recipientList to send to endpoint in a multi
thread manner?
for instance if it contains a list of FTP endpoint (producer) I would like
to deploy files at the same time.
as it is implemented now it starts producing the 2nd as the 1st is completed
-- 
View this message in context: http://old.nabble.com/recipientList-multithreading-tp26635868p26635868.html
Sent from the Camel - Users mailing list archive at Nabble.com.

cometd client connector for Camel

2009-12-04T11:42:08Z


I'm working with cometd on my current project and tried to use Camel-cometd.

However, it seems that Camel sets up its own cometd server.

What I'd like to do is connect to an existing cometd server, so the Camel
app acts as a cometd/Bayeux client. Now I'm doing this with cometd.org's
java-client and doing pretty well.

But if anyone has any ideas how to make integration for this with Camel I'd
be more than happy to know. I don't know how to create a Camel connector.

Thank you.
-- 
View this message in context: http://old.nabble.com/cometd-client-connector-for-Camel-tp26635861p26635861.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Testing Camel with a Groovy script

2009-12-04T10:13:15Z

On Fri, Dec 4, 2009 at 9:37 AM, bgoetzmann  wrote:
>
> Hello,
>
> I would liket just point out this article on Groovy and Camel:
> http://groovy.dzone.com/articles/groovy-ride-camel
>
> What is very interesting with Groovy and its GRAPE system is that you can
> easily test Camel with a simple Groovy script even used in the Groovy
> console!
> Perhaps, this can be useful for some introduction to Camel in the coming
> book "Camel in action"!!
>

Yeah its a great article and nice that you can have all in a single
file and dont need to battle with maven poms.
However for some people getting groovy installed and ready to use is
also a challenge.

For the book we have though of a section about alternative languages
such as Scala, Groovy, Ruby etc. to use with Camel.
But there is just so many things to talk about with Camel that we have
to make a decision what to include.

Feedback and ideas what you want in the book is welcome and preferred
to be discussed at the book forum
http://www.manning-sandbox.com/forum.jspa?forumID=601




> Cheers,
>
> Bertrand.
> --
> View this message in context: http://old.nabble.com/Testing-Camel-with-a-Groovy-script-tp26635810p26635810.html
> Sent from the Camel - Users (activemq) 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

Question about camel-jpa and camel-etl

2009-12-04T10:05:41Z

In the wiki page of camel-jpa component, it is mentioned that a
entityManagerFactory must be specified like this :


   



Surprisingly, I don't see this in the camel-example-etl example.

When deploying camel-example-etl on Apache Felix Karaf, felix complains that
:

Caused by: java.lang.IllegalArgumentException: entityManagerFactory must be
specified
    at org.apache.camel.util.ObjectHelper.notNull(ObjectHelper.java:244)
    at
org.apache.camel.component.jpa.JpaEndpoint.validate(JpaEndpoint.java:230)
    at
org.apache.camel.component.jpa.JpaEndpoint.createConsumer(JpaEndpoint.java:87)

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

Getting error when using Apache camel inside servicemix.

2009-12-04T09:36:11Z


Hi,

I created one webservice in the OSGI format and installed it in the
servicemix.
The webservice worked fine and i was able to send and receive requests
through SoapUI software.

I tried to add some apache camel code inside this so that i can send a
string to a file.

The implementation is as follows
This is my webservice implementation class.

package com.webservice.calculator;

import java.util.logging.Logger;
import javax.jws.WebMethod;
import javax.jws.WebParam;
import javax.jws.WebResult;
import javax.jws.WebService;
import javax.xml.bind.annotation.XmlSeeAlso;
import javax.xml.ws.RequestWrapper;
import javax.xml.ws.ResponseWrapper;

import org.apache.camel.CamelContext;
import org.apache.camel.Component;
import org.apache.camel.Endpoint;
import org.apache.camel.Exchange;
import org.apache.camel.Producer;
import org.apache.camel.ProducerTemplate;
import org.apache.camel.component.file.FileComponent;
import org.apache.camel.component.log.LogComponent;
import org.apache.camel.impl.DefaultCamelContext;

import com.progress.pso.payments_api.PaymentsApi;

/**
 * This class was generated by Apache CXF 2.2.5
 * Tue Dec 01 17:46:59 IST 2009
 * Generated source version: 2.2.5
 * 
 */

@javax.jws.WebService(
                      serviceName = "CalculatorService",
                      portName = "CalculatorSoapPort",
                      targetNamespace = "http://calculator.webservice.com",
                      wsdlLocation =
"file:/D:/harbeer/Maven_Project/payment-web-service-osgi/src/main/resources/wsdl/Calculator.wsdl",
                      endpointInterface =
"com.webservice.calculator.CalculatorPortType")
                      
public class CalculatorPortTypeImpl implements CalculatorPortType {

    private static final Logger LOG =
Logger.getLogger(CalculatorPortTypeImpl.class.getName());
    private PaymentsApi paymentApi;
    private CamelContext camel;
    private ProducerTemplate template;

    
    public CalculatorPortTypeImpl() throws Exception {
    	camel = new DefaultCamelContext();
    	template = camel.createProducerTemplate();
    	camel.addComponent("file", new FileComponent());
    	camel.start();
    }
    
    public void setPaymentApi(PaymentsApi paymentApi) {
    	this.paymentApi = paymentApi;
    }

    /* (non-Javadoc)
     * @see
com.webservice.calculator.CalculatorPortType#subtractNumbers(java.math.BigInteger 
inputOne ,)java.math.BigInteger  inputTwo )*
     */
    public java.math.BigInteger subtractNumbers(java.math.BigInteger
inputOne,java.math.BigInteger inputTwo) { 
        try {
        	sendToCamelFile("harbeer");
            return paymentApi.subtractNumbers(inputOne, inputTwo);
        } catch (Exception ex) {
            ex.printStackTrace();
            throw new RuntimeException(ex);
        }
    }

    
    private void sendToCamelFile(String name) {
    	try {
    		
            // get the log component
            Component component = camel.getComponent("file");

            Endpoint endpoint =
component.createEndpoint("file:///D:/harbeer");
            Exchange exchange = endpoint.createExchange();
            exchange.getIn().setBody(name);
            exchange.getIn().setHeader(FileComponent.HEADER_FILE_NAME,
"harbeer.txt");

            // now we want to send the exchange to this endpoint and we then
need a producer
            // for this, so we create and start the producer.
            Producer producer = endpoint.createProducer();
            System.out.println(producer);
            producer.start();
            System.out.println(name);
            producer.process(exchange);
            producer.stop();

        } catch (Exception e) {
            // we ignore any exceptions and just rethrow as runtime
            throw new RuntimeException(e);

        }

    }

}

I installed this new webservice implementation inside servicemix 4 as an
osgi bundle.
I got following exception when i called webservice method subtractNumbers();


Caused by: org.apache.camel.NoTypeConversionAvailableException: No type
converte
r available to convert from type: class
org.apache.camel.component.file.FileMess
age to the required type: java.io.InputStream with value FileMessage:
D:\harbeer

        at
org.apache.camel.impl.converter.DefaultTypeConverter.doConvertTo(Defa
ultTypeConverter.java:147)
        at
org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(Defaul
tTypeConverter.java:90)
        at
org.apache.camel.impl.converter.DefaultTypeConverter.convertTo(Defaul
tTypeConverter.java:86)
        at
org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:85)
        at
org.apache.camel.impl.MessageSupport.getBody(MessageSupport.java:52)
        at
org.apache.camel.util.ExchangeHelper.getMandatoryInBody(ExchangeHelpe
r.java:130)
        at
org.apache.camel.component.file.FileProducer.process(FileProducer.jav
a:78)
        at
org.apache.camel.component.file.FileProducer.process(FileProducer.jav
a:61)
        at
com.webservice.calculator.CalculatorPortTypeImpl.sendToCamelFile(Calc
ulatorPortTypeImpl.java:129)
        ... 31 more

Please help if i am missing some thing.

With Regards
Harbeer Kadian
-- 
View this message in context: http://old.nabble.com/Getting-error-when-using-Apache-camel-inside-servicemix.-tp26635824p26635824.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Errors parsing camel-context.xml

2009-12-04T08:39:03Z

Pete,

I think it's just a matter of adding the camel: prefix before the json
element as well - the way it is written now, the json element is not
using the camel namespace and I suspect that's why you're getting the
parse exception (which says it found element "json" and was expecting
"http://camel.apache.org/schema/spring":json )

Regards,

Gert Vanthienen
------------------------
Open Source SOA: http://fusesource.com
Blog: http://gertvanthienen.blogspot.com/



2009/12/4 Pete Mueller :
>
> Hello,
>
> I am receiving the following error trying to start up my camel routing
> bundle with a camel-context.xml in it.
>
> The error is:
> org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line
> 16 in XML document from URL
> [bundle://135.0:0/META-INF/spring/camel-context.xml] is invalid; nested
> exception is org.xml.sax.SAXParseException: cvc-complex-type.2.4.a: Invalid
> content was found starting with element 'json'. One of
> '{"http://camel.apache.org/schema/spring":artixDS,
> "http://camel.apache.org/schema/spring":bindy,
> "http://camel.apache.org/schema/spring":csv,
> "http://camel.apache.org/schema/spring":flatpack,
> "http://camel.apache.org/schema/spring":gzip,
> "http://camel.apache.org/schema/spring":hl7,
> "http://camel.apache.org/schema/spring":jaxb,
> "http://camel.apache.org/schema/spring":json,
> "http://camel.apache.org/schema/spring":rss,
> "http://camel.apache.org/schema/spring":secureXML,
> "http://camel.apache.org/schema/spring":serialization,
> "http://camel.apache.org/schema/spring":string,
> "http://camel.apache.org/schema/spring":tidyMarkup,
> "http://camel.apache.org/schema/spring":xmlBeans,
> "http://camel.apache.org/schema/spring":xstream,
> "http://camel.apache.org/schema/spring":zip}' is expected.
>
> Clearly from the error, it shows that "json" is an allowed element. but SAX
> says otherwise. �Any idea how to reconcile this? �I have a similar error
> with using the placeholderPrefix attribute inside a property-placeholder
> element.
>
> Thanks,
> -p
>
> Here are relevant portions of my camel-context.xml if it helps. �I thought
> perhaps I'm using the wrong schema.
>
> 
>  � � � �xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:context="http://www.springframework.org/schema/context"
> � � � �xmlns:osgi="http://www.springframework.org/schema/osgi"
> xmlns:osgix="http://www.springframework.org/schema/osgi-compendium"
> � � � �xmlns:camel="http://camel.apache.org/schema/spring"
>
> � � � �xsi:schemaLocation="http://www.springframework.org/schema/beans
> http://www.springframework.org/schema/beans/spring-beans.xsd
> � � � � � � � �http://www.springframework.org/schema/context
> http://www.springframework.org/schema/context/spring-context.xsd
> � � � � � � � �http://www.springframework.org/schema/osgi
> http://www.springframework.org/schema/osgi/spring-osgi.xsd
> � � � � � � � �http://www.springframework.org/schema/osgi-compendium
> http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd
> � � � � � � � �http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring.xsd">
>
> � � � � placeholderPrefix="#{" placeholderSuffix="}" />
> � � � �
> � � � � � unmarshalTypeName="com.routecloud.bean.Message" />
> � � � �
>
> ...
> --
> View this message in context: http://old.nabble.com/Errors-parsing-camel-context.xml-tp26635732p26635732.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
>

Testing Camel with a Groovy script

2009-12-04T08:37:15Z


Hello,

I would liket just point out this article on Groovy and Camel:
http://groovy.dzone.com/articles/groovy-ride-camel

What is very interesting with Groovy and its GRAPE system is that you can
easily test Camel with a simple Groovy script even used in the Groovy
console!
Perhaps, this can be useful for some introduction to Camel in the coming
book "Camel in action"!!

Cheers,

Bertrand.
-- 
View this message in context: http://old.nabble.com/Testing-Camel-with-a-Groovy-script-tp26635810p26635810.html
Sent from the Camel - Users (activemq) mailing list archive at Nabble.com.

Re: Classpath problem with camel-cxf and OSGi

2009-12-04T08:04:13Z

An alternative possibility mentioned in a previous post is to use Apache
Felix Karaf (kernel of SMX4) if you don't need NMR, JBI components but only
camel

You can install easily the camel-cxf feature. This feature will
automatically install CXF.

http://repository.apache.org/snapshots/org/apache/camel/karaf/features/2.1-SNAPSHOT/features-2.1-SNAPSHOT-features.xml


mvn:commons-pool/commons-pool/1.4
-

mvn:org.apache.geronimo.specs/geronimo-jms_1.1_spec/1.1.1

mvn:org.springframework/spring-jms/2.5.6.SEC01
-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.asm/2.2.3_3

-

mvn:org.apache.geronimo.specs/geronimo-servlet_2.5_spec/1.1.2

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jetty-bundle/6.1.14_2

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-codec/1.3_2

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.jdom/1.1_2

mvn:org.codehaus.jettison/jettison/1.1
-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.ant/1.7.0_3

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.bcel/5.2_2

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.xalan/2.7.1_2

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.xerces/2.9.1_3

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.xmlbeans/2.4.0_2

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.xmlsec/1.4.3_2

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.xmlresolver/1.2_2

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.woodstox/3.2.8_1

mvn:org.apache.ws.commons.schema/XmlSchema/1.4.5
mvn:commons-lang/commons-lang/2.4
mvn:commons-collections/commons-collections/3.2.1
-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.antlr/2.7.7_2

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.oro/2.0.8_3

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.velocity/1.6.2_3

mvn:org.apache.ws.commons.axiom/axiom-impl/1.2.8
mvn:org.apache.ws.commons.axiom/axiom-api/1.2.8
-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.javax.mail/1.4.1_2

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.neethi/2.0.4_1

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.abdera/0.4.0-incubating_3

-

mvn:org.apache.geronimo.specs/geronimo-jaxws_2.1_spec/1.0

-

mvn:org.apache.geronimo.specs/geronimo-annotation_1.0_spec/1.1.1

-

mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.saaj-api-1.3/1.4.0

-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.wsdl4j/1.6.2_2

-

mvn:org.apache.servicemix.specs/org.apache.servicemix.specs.jsr311-api-1.0/1.3.0

-

mvn:org.apache.geronimo.specs/geronimo-ws-metadata_2.0_spec/1.1.2

mvn:org.apache.cxf/cxf-bundle/2.2.5
-

mvn:org.apache.servicemix.bundles/org.apache.servicemix.bundles.commons-io/1.3.2_3

camel-spring-osgi
http
mvn:org.apache.camel/camel-cxf/2.1-SNAPSHOT



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 Fri, Dec 4, 2009 at 2:23 AM, Willem Jiang  wrote:

> As we are in the middle of whole bunch of release.
> CXF 2.2.5 , Camel 2.1.0 , then ServiceMix 4.1.0 ...
>
> If you can wait for a week, you will get what you want :)
>
> If you can't wait, you may need to uninstall the CXF 2.2.4 bundle and
> reinstall CXF 2.2.5 bundle yourself.
>
> Willem
>
>
>
> TheWinch wrote:
>
>> Is there a way to use Camel-cxf  2.1.0 in Servicemix 4.1.0 ?
>>
>> I have downloaded SMX 4.1.0-SNAPSHOT, but I can't install Camel-cxf. I
>> have
>> noted also that SMX uses CXF2.2.4 while Camel uses CXF 2.2.5. Any
>> knowledge
>> on this side ? Should I better ask in the SMX mailing list ?
>>
>>
>> Claus Ibsen-2 wrote:
>>
>>> On Thu, Dec 3, 2009 at 9:09 AM, TheWinch
>>>  wrote:
>>>
>>>> Hi,
>>>>
>>>> Thanks for this answer. Is there a place where I can get a packaged
>>>> snapshot
>>>> version of camel 2.1.0 ? Or should I build it from the SVN ?
>>>>
>>>>  Yes the download page at Camel have links to .zip of SNAPSHOT and how
>>> to setup maven to use SNAPSHOT
>>> http://camel.apache.org/download.html
>>>
>>>
>>>
>>>  willem.jiang wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> This issue is related the get default bus issue[1], and it should be
>>>>> fixed in the coming out Camel 2.1.0.
>>>>> [1]https://issues.apache.org/activemq/browse/CAMEL-2216
>>>>>
>>>>> Willem
>>>>>
>>>>> TheWinch wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I'm trying to deploy dynamically endpoints using camel-cxf. I have
an
>>>>>> example that works perfectly well in camel 2.0.0 standalone, and
that
>>>>>> does
>>>>>> not work in camel 2.0.0 deployed on SMX4 (code provided below).
>>>>>> I have read on forums that this might come from class-path issues.
>>>>>> However I
>>>>>> can't see where it comes from. Could someone help ?
>>>>>>
>>>>>> To deploy the endpoint I do:
>>>>>>
>>>>>> // in Test:
>>>>>> public void doTest() { builder.deployEndpoint(); }
>>>>>> // in DynamicBuilder:
>>>>>> public void deployEndpoint() {
>>>>>>        CamelContext context = getContext();
>>>>>>
>>>>>>        final String endpointUri = "cxf:" +
>>>>>> "http://localhost:9000/service"
>>>>>> + "?serviceClass=" + SERVICE_CLASS;
>>>>>>        def = from( endpointUri );
>>>>>>        def.process( new CallbackProcessor() );
>>>>>>        context.addRouteDefinitions( Arrays.asList( def ) );
>>>>>>        context.startRoute( def );
>>>>>> }
>>>>>>
>>>>>> This works OK in camel standalone, and in SMX4 this generates the
>>>>>> following
>>>>>> error:
>>>>>>
>>>>>> org.apache.camel.RuntimeCamelException: java.lang.RuntimeException:
>>>>>> Could
>>>>>> not find destination factory for transport
>>>>>> http://schemas.xmlsoap.org/soap/h
>>>>>> ttp
>>>>>>        at
>>>>>>
>>>>>> org.apache.camel.util.ObjectHelper.wrapRuntimeCamelException(ObjectHelper.java:1011)
>>>>>>        at
>>>>>>
>>>>>> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:121)
>>>>>>        at
>>>>>>
>>>>>> org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:469)
>>>>>>        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.AbstractDelegatedExecutionApplicationContext.finishRefresh(AbstractDelegatedExecutionApplicationCo
>>>>>> ntext.java:380)
>>>>>>        at
>>>>>>
>>>>>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.ja
>>>>>> va:346)
>>>>>>        at
>>>>>>
>>>>>> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85)
>>>>>>        at
>>>>>>
>>>>>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplication
>>>>>> Context.java:308)
>>>>>>        at
>>>>>>
>>>>>> org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(Dependen
>>>>>> cyWaiterApplicationContextExecutor.java:138)
>>>>>>        at java.lang.Thread.run(Thread.java:619)
>>>>>> Caused by: java.lang.RuntimeException: Could not find destination
>>>>>> factory
>>>>>> for transport http://schemas.xmlsoap.org/soap/http
>>>>>>        at
>>>>>>
>>>>>> org.apache.cxf.binding.soap.SoapTransportFactory.getDestination(SoapTransportFactory.java:76)
>>>>>>        at
>>>>>> org.apache.cxf.endpoint.ServerImpl.initDestination(ServerImpl.java:90)
>>>>>>        at
>>>>>> org.apache.cxf.endpoint.ServerImpl.(ServerImpl.java:69)
>>>>>>        at
>>>>>>
>>>>>> org.apache.cxf.frontend.ServerFactoryBean.create(ServerFactoryBean.java:118)
>>>>>>        at
>>>>>>
>>>>>> org.apache.cxf.jaxws.JaxWsServerFactoryBean.create(JaxWsServerFactoryBean.java:167)
>>>>>>        at
>>>>>>
>>>>>> org.apache.camel.component.cxf.CxfConsumer.(CxfConsumer.java:108)
>>>>>>        at
>>>>>>
>>>>>> org.apache.camel.component.cxf.CxfEndpoint.createConsumer(CxfEndpoint.java:97)
>>>>>>        at
>>>>>>
>>>>>> org.apache.camel.impl.EventDrivenConsumerRoute.addServices(EventDrivenConsumerRoute.java:57)
>>>>>>        at
>>>>>>
>>>>>> org.apache.camel.impl.DefaultRoute.getServicesForRoute(DefaultRoute.java:81)
>>>>>>        at
>>>>>> org.apache.camel.impl.RouteService.doStart(RouteService.java:77)
>>>>>>        at
>>>>>> org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:52)
>>>>>>        at
>>>>>>
>>>>>> org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:825)
>>>>>>        at
>>>>>>
>>>>>> org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:99)
>>>>>>        at
>>>>>>
>>>>>> org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:119)
>>>>>>        ... 12 more
>>>>>>
>>>>>> My camel context:
>>>>>>
>>>>>>
>>>>>> 
>>>>>> >>>>>       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>>>>>>       xmlns:cxf="http://camel.apache.org/schema/cxf"
>>>>>>       xsi:schemaLocation="
>>>>>>       http://www.springframework.org/schema/beans
>>>>>> http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
>>>>>>       http://camel.apache.org/schema/cxf
>>>>>> http://camel.apache.org/schema/cxf/camel-cxf.xsd
>>>>>>       http://camel.apache.org/schema/spring
>>>>>> http://camel.apache.org/schema/spring/camel-spring.xsd
>>>>>>    ">
>>>>>>   
>>>>>>   
>>>>>>   >>>>> resource="classpath:META-INF/cxf/cxf-extension-http-jetty.xml"
>>>>>> />
>>>>>>
>>>>>>    
>>>>>>   >>>>> xmlns="http://camel.apache.org/schema/spring">
>>>>>>       
>>>>>>   
>>>>>>
>>>>>>   >>>>> destroy-method="tearDown">
>>>>>>     
>>>>>>   
>>>>>> 
>>>>>>
>>>>>> And my import directives:
>>>>>>                        javax.jws,
>>>>>>                        javax.wsdl,
>>>>>>                        javax.xml.bind,
>>>>>>                        javax.xml.bind.annotation,
>>>>>>                        javax.xml.namespace,
>>>>>>                        javax.xml.soap,
>>>>>>                        javax.xml.ws,
>>>>>>                        META-INF.cxf,
>>>>>>                        META-INF.cxf.osgi,
>>>>>>
>>>>>>                     org.apache.cxf,
>>>>>>                     org.apache.cxf.binding,
>>>>>>                     org.apache.cxf.binding.soap,
>>>>>>                     org.apache.cxf.binding.soap.interceptor,
>>>>>>                     org.apache.cxf.binding.soap.model,
>>>>>>                     org.apache.cxf.binding.xml,
>>>>>>                     org.apache.cxf.bindings.xformat,
>>>>>>                     org.apache.cxf.common.classloader,
>>>>>>                     org.apache.cxf.common.i18n,
>>>>>>                     org.apache.cxf.common.logging,
>>>>>>                     org.apache.cxf.common.util,
>>>>>>                     org.apache.cxf.configuration,
>>>>>>                     org.apache.cxf.configuration.security,
>>>>>>                     org.apache.cxf.configuration.spring,
>>>>>>                     org.apache.cxf.databinding,
>>>>>>                             org.apache.cxf.endpoint,
>>>>>>                             org.apache.cxf.feature,
>>>>>>                             org.apache.cxf.frontend,
>>>>>>                             org.apache.cxf.headers,
>>>>>>                             org.apache.cxf.helpers,
>>>>>>                             org.apache.cxf.interceptor,
>>>>>>                             org.apache.cxf.io,
>>>>>>                             org.apache.cxf.jaxrs,
>>>>>>                             org.apache.cxf.jaxrs.client,
>>>>>>                             org.apache.cxf.jaxrs.model,
>>>>>>                             org.apache.cxf.jaxrs.utils,
>>>>>>                             org.apache.cxf.jaxws,
>>>>>>                             org.apache.cxf.jaxws.context,
>>>>>>                             org.apache.cxf.message,
>>>>>>                             org.apache.cxf.phase,
>>>>>>                             org.apache.cxf.service,
>>>>>>                             org.apache.cxf.service.factory,
>>>>>>                             org.apache.cxf.service.invoker,
>>>>>>                             org.apache.cxf.service.model,
>>>>>>                             org.apache.cxf.staxutils,
>>>>>>                             org.apache.cxf.ws.addressing,
>>>>>>                             org.apache.cxf.wsdl,
>>>>>>                             org.apache.cxf.wsdl11,
>>>>>>                             org.apache.cxf.transport,
>>>>>>                             org.apache.cxf.transport.http,
>>>>>>                             org.apache.cxf.transport.http_jetty,
>>>>>>                             org.apache.cxf.transport.http.policy,
>>>>>>
>>>>>>                        org.apache.cxf.bus,
>>>>>>                        org.apache.cxf.bus.spring,
>>>>>>                        org.apache.cxf.bus.resource,
>>>>>>                        org.apache.cxf.resource,
>>>>>>                        org.springframework.beans.factory.config,
>>>>>>                        org.apache.servicemix.common.osgi,
>>>>>>                        *
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>  --
>>>> View this message in context:
>>>>
>>>> http://old.nabble.com/Classpath-problem-with-camel-cxf-and-OSGi-tp26612544p26621724.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
>>>
>>>
>>>
>>
>