One thing you can try:
If you do a dispatch.getRequestContext().put(MessageContext.WSDL_OPERATION,
new QName("http://my.namespace";, "myOperation"));
before calling the invoke, it MAY be able to properly match the operation name
and thus not use the generic "invoke" operation. That said, you MAY need to
create the Dispatch client from a Service that was created with a WSDL URL.
Dan
On Thursday, May 26, 2011 1:02:56 PM Gunnar Morling wrote:
> Hi,
>
> I'm trying to use CXF's coloc feature
> (http://cxf.apache.org/docs/coloc-feature.html). Things work fine when
> using a "real" client for accessing the service (meaning the generated
> service/port classes for my service).
>
> But I'm running into trouble when using a dynamic client, namely a
> JAX-WS dispatch client. The cause seems to be that in
> org.apache.cxf.binding.coloc.ColocOutInterceptor#isColocated() the
> name of the invoked operation is compared against the names hosted by
> the co-located server port. As the invoked method name is a generic
> one in the dispatch scenario ("invoke" actually) this comparison fails
> and instead of the coloc transport the standard transport using HTTP
> is performed.
>
> Is there anything I could do about this? If JAX-WS dispatch based
> clients are generally not supported, is there any other way to use the
> coloc transport in a generic manner? Or is this just an issue, for
> which I should open up a feature request in JIRA?
>
> Thanks in advance,
>
> Gunnar
--
Daniel Kulp
[email protected]
http://dankulp.com/blog
Talend - http://www.talend.com
