d
> returns a JAX-RS Response. May be the CamelCXF RS code needs to be
tweaked
> a bit to check if JAX-RS Response is already available before continuing
> with the route flow...
>
> Cheers, Sergey
>
>
> On Tue, Nov 20, 2018 at 5:20 PM #S-SmixDev wrote:
>
> > Hi Zoran,
va/io/swagger/v3/jaxrs2/integration/resources/OpenApiResource.java#L28
On Mon, Nov 19, 2018 at 2:03 PM #S-SmixDev wrote:
>
>
> Hi Camel Riders,
>
> I'm trying to integrate a Camel-CXFRS endpoint with Swagger UI using the
> Swagger/OpenAPI Feature.
>
> This works fine with a "pure"
Hi Camel Riders,
I'm trying to integrate a Camel-CXFRS endpoint with Swagger UI using the
Swagger/OpenAPI Feature.
This works fine with a "pure" CXF endpoint, no Camel involved.
When using Camel-CXFRS, however, I can't make it work properly without
extra implementation work in the Camel route.
targetClient=1 means there are no headers except the standard properties
from the MQMD header on the message. You can not send custom headers that
way.
And specifying the targetClient does not have any effect whatsoever when
reading messages from a queue.
Regards,
Jens
Von:blommis
Hi,
I'm wondering if the following scenario can be implemented using standard
Camel components (ie. without using a custom processor and /or custom
components).
Consider a synchronous InOut exchange that triggers some asynchronous
backend processing. The response that needs to be generated for
Cannot convert value of type [com.ibm.mq.jms.MQConnectionFactory] to
required
type [javax.jms.ConnectionFactory] for property 'connectionFactory': no
matching editors or conversion strategy found
That typically means you have multiple copies of the javax,jms classes on
the classpath (e.g.
