Actually it's not that easy, but very possible. The impl would be a bit
different depending on what flavor you're using, the Java or C one (in
the latter case you'd need a bit of jni as well and packaging is not
trivial). There will likely be limitations, like running in an OSGi
container for instance. You'll also have to deal with the data types.
The idea is pretty straightforward though:
* the Endpoint configuration is very simple (I don't think you need much
more the Tux service)
* your Tux service would become a Consumer (the event-driven one, not
polling).
* your Consumer and Producers would be Camel Services (already the
default) so you'd call tpinit/tpdone (iirc) in doStart/doStop.
* your Producer.process would invoke on tpcall or tpacall as appropriate
* you have a couple of options of dealing with replies to async calls
(tpacall).
That's kinda the idea.
Hadrian
On 07/25/2012 11:17 AM, Willem Jiang wrote:
If you have third part jar which can do the tp_call, it could be easy to
write a camel-tuxedo component.
On Wed Jul 25 16:57:40 2012, dgb714393701 wrote:
how to create a component of camel for tuxedo? i want to communicate to
TUXEDO use camel.
--
View this message in context:
http://camel.465427.n5.nabble.com/how-to-create-a-component-of-camel-for-tuxedo-tp5716442p5716443.html
Sent from the Camel Development mailing list archive at Nabble.com.
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang
