camel integration in servicemix

[Geert Bozz <ge...@gmail.com>]

Hello all,

I 'm looking for information on how camel is integrated into servicemix and
I have two questions. I want to start by shortly explaining my
understanding, this might benefit others and it helps putting my questions
into its context. If I understand correctly,

1) Camel has an http component which is supposed to point to a jetty http
server, I can imagine this is an embedded http server when camel is used
stand-alone.
2) I 'm quite sure that ServiceMix fullsfulls the osgi http service
contract by using the pax web server, which also happens to be a jetty http
server.

My first question now is: has the camel-servicemix module been modified so
that it uses the servicemix http server? How was this done? Is it just a
matter of configuring the camel bundle?

If I want to get under the hood of the http server used by the pair
camel-servicemix, how do I best tackle this? Is it sufficient to look at
the default jetty server that comes with servicemix, or do I need to focus
on the configuration of the jetty component that comes with camel, and
documented here: http://camel.apache.org/jetty.html.


thanks,

geert

Re: camel integration in servicemix

[Andreas Gies <an...@wayofquality.de>]

Hi Geert, 

Perhaps there are other ways of doing it, but i found reusing the Camel
HTTP servlet right out of the box a bit un-OSGI-ish, so that would be true
for ServiceMix as well.
I have published a blog entry explaining in more detail what the issue was
and I addressed it:

http://www.wayofquality.de/index.php/en/blog/entry/using-the-camel-servlet-
component-in-an-osgi-blueprint-container


I am using pax-web as an HTTP service implementation, but the blog simply
assumes that you some form of http service and hopefully the
pax-web-extender installed.


Hope that helps 
Andreas



Andreas Gies


WoQ ­ Way of Quality UG

http://www.wayofquality.de


Geschäftsführer & CTO

eMail: andreas@wayofquality.de

Tel DE: +49 151 23470823



Tel UK: +44 755 1381918



Fax: +49 1805 006534 2114


Amtsgericht Landshut: HRB 8352
Ust.-Id.: DE274771254

Haftungsausschluss

Diese Email kann vertrauliche und/oder rechtlich geschützte Informationen
enthalten und ist ausschließlich für den/die benannten Adressaten
bestimmt. Sollten Sie nicht der beabsichtigte Empfänger sein oder diese
Email irrtümlich erhalten haben, ist es Ihnen nicht gestattet diese Mail
oder einen Teil davon ohne unsere Erlaubnis zu verbreiten, zu kopieren,
unbefugt weiterzuleiten oder zu behalten. Informieren Sie bitte sofort den
Absender telefonisch oder per Email und löschen Sie diese Email und alle
Kopien aus Ihrem System. Wir haften nicht für die Unversehrtheit von
Emails, nachdem sie unseren Einflussbereich verlassen haben.
Disclaimer

This email may contain confidential and/or privileged information and is
intended solely for the attention and use of the named addressee(s). If
you are not the intended recipient, or a person responsible for delivering
it to the intended recipient, you are not authorized to and must not
disclose, copy, distribute, or retain this message or any part of it
without our authority. Please contact the sender by call or reply email
immediately and destroy all copies and the original message. We are not
responsible for the integrity of emails after they have left our sphere of
control.








Am 7/22/13(30) 3:33 PM schrieb "Geert Bozz" unter <ge...@gmail.com>:

>Hello all,
>
>I 'm looking for information on how camel is integrated into servicemix
>and
>I have two questions. I want to start by shortly explaining my
>understanding, this might benefit others and it helps putting my questions
>into its context. If I understand correctly,
>
>1) Camel has an http component which is supposed to point to a jetty http
>server, I can imagine this is an embedded http server when camel is used
>stand-alone.
>2) I 'm quite sure that ServiceMix fullsfulls the osgi http service
>contract by using the pax web server, which also happens to be a jetty
>http
>server.
>
>My first question now is: has the camel-servicemix module been modified so
>that it uses the servicemix http server? How was this done? Is it just a
>matter of configuring the camel bundle?
>
>If I want to get under the hood of the http server used by the pair
>camel-servicemix, how do I best tackle this? Is it sufficient to look at
>the default jetty server that comes with servicemix, or do I need to focus
>on the configuration of the jetty component that comes with camel, and
>documented here: http://camel.apache.org/jetty.html.
>
>
>thanks,
>
>geert