It's a bit harder for us to let camel-cxf component supports the
dispatch API right now. But if you still want to use the dispatch, you
can write a custom POJO bean and wrap your dispatch implementation
within it. Then you can route the camel message to that POJO bean as well.
Willem
On 2/16/11 7:35 PM, Aki Yoshida wrote:
Hi William,
I want to use this CXF endpoint just as a normal typed CXF endpoint
and I expect to have arbitrary generic CXF interceptors to be placed
just as for the normal case. So, I don't think Camel DSL or processor
can fit into this picture.
Regards, aki
On Tue, Feb 15, 2011 at 7:56 PM, William Tam<email.w...@gmail.com> wrote:
What does your CXF interceptor do? You know you have Camel DSL or
processor in your arsenal.
On 02/15/2011 01:02 PM, Aki Yoshida wrote:
Hi William,
I can't use camel-http because I would like to call some CXF interceptors.
I am wondering if we can modify CxfProducer and CxfEndpoint to support
the dispatch mode.
CXF's DispatchImpl does a few things to set up the dispatch mode
(i.e., setting the dummy service class, adding the dispatch binding
operations, etc) and it eventually calls the same ClientImpl's invoke
method at the end. So, it seems possible to have this feature
integrated in CxfProducer/CxfEndpoint.
I would like to experiment with this idea. If you have some suggestion
that would be appreciated.
Thanks.
Regards, Aki
On Tue, Feb 15, 2011 at 5:19 PM, William Tam<email.w...@gmail.com> wrote:
Hi Aki,
If you need to send arbitrary payload to some target servcie, you may
consider using Camel HTTP component. Camel CXF component uses
ClientFactoryBean APIs (including message mode) which is subject to the
limitation you observed.
Regards,
William
On 02/15/2011 07:49 AM, Aki Yoshida wrote:
Hi,
If you are writing a CXF client, you can write a client using the
CXF's dispatch API to send an arbitrary payload to some target
service.
I would like to configure a camel cxf endpoint that does the same
thing. However, the code seems to require either the WSDL or the
service class.
When I do not set both the wsdlURL and serviceClass parameters, it
still assumes the service class is set and starts initializing the
service class, leading to an NPE.
Am I missing something here or is this a known limitaiton?
Thanks for your help.
Regards, Aki
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
