Camel Swagger cdi Example

Hey all I was playing around with building REST services and tried out the Camel Swagger cdi Example. It turns out, that it works as expected but is not generating a valid Swagger definition (camel-swagger-java:2.16.2): - No response definition in the put-definition -> Added manually a new one:

Re: Camel Swagger cdi Example

Hi Can you upgrade swagger-java to latest release - it should fix that enum issue. And for the "int" then yeah we love contributions. You are welcome to work on a PR / patch if you want to try that http://camel.apache.org/contributing On Fri, Feb 12, 2016 at 9:05 AM, gagahhag

Re: ActiveMQ Consuming

Hi, thanks for answering. I have two separate servers running ActiveMQ ( my datasources ) and a single Camel App that should consume from those 2 instances in a transactional way. What I can do is from( broker1:queue:source, broker2:queue:source).process( . The problem is what transaction

Re: Camel Swagger cdi Example

Hi Thanks for the really fast answer :-) I tried 2.16.3-SNAPSHOT instead and it worked! Never did contribute to such a project, but I'll have a look at it. There's always a first time... Am 12.02.2016 09:09, schrieb Claus Ibsen-2 [via Camel]: > Hi > > Can you upgrade swagger-java to latest

blueprint/nettyencoderfactory

Hi there, I tried (on camel 2.15.2): and Both do not work. Any ideas/suggestions? Cheers, Thomas.

Re: Jetty Java DSL InstantiationError

I forgot to add I am using camel 2.16.2 -- View this message in context: http://camel.465427.n5.nabble.com/Jetty-Java-DSL-InstantiationError-tp5777659p5777660.html Sent from the Camel - Users mailing list archive at Nabble.com.

Jetty Java DSL InstantiationError

When trying to use jetty to call a REST service from java DSL, I get the following: Caused By: java.lang.InstantiationError: org.eclipse.jetty.util.SocketAddressResolver at org.eclipse.jetty.client.HttpClient.doStart(HttpClient.java:212) at

Saxon cannot write a DOMResult unless saxon9-dom.jar is on the classpath

I'm trying to create a simple Web Service configuration based on the example in the distribution at examples/camel-example-spring-ws: http://camel.apache.org/spring-ws-example.html I have just about the same dependencies as in the example: However, it's run as a standalone spring boot

Re: Camel BeanIO catch and ignore InvalidRecordException

hello, I have exactly same issue with the beanIO component. The solution I saw was handling the error at bean Reader level. i.e. by registering your custom ErrorHandler in BeanReader. But how do we do it using camel is mystery for me . -- View this message in context:

Re: blueprint/nettyencoderfactory

The Netty4 encoder/decoder don’t have a “Charset” property - this is controlled by the “encoding” URI parameter. > On Feb 12, 2016, at 5:36 AM, Walzer, Thomas > wrote: > > Hi there, > > I tried (on camel 2.15.2): > > >

Re: ActiveMQ Consuming

Two questions - - What are the other transaction endpoints you’ll be using? - Will messages from both broker1 and broker2 be involved in the same transaction? > On Feb 12, 2016, at 1:19 AM, Stanisław Kuś wrote: > > Hi, > > thanks for answering. I have two separate

Re: ActiveMQ Consuming

Hi, 1. Each message from each Jms should be processed in a separated transaction and will be passed to a webservice. Additionaly basen on a certain message part a file will be transfered from one ftp to another. 2. For each message independend from which broker it comes a new transaction should

Reading an EBCDIC file from Apache Camel

Hello friends, I want to know if there is any way that we can read an EBCDIC file from Apache Camel. That EBCDIC file has the compressed data and I have corresponding copybook file as well. Any help is much appreciated. Thanks, Sandeep -- View this message in context:

Re: OsgiServiceRegistry caching service references, why?

Part of the issue with crafting good examples or good code for that matter are the exigencies of testing with PojoSR and then using the same code in development. I'll commonly work around PojoSR only to find code doesn't work when deployed in Karaf or vice versa. Since tests can't work across