Re: CXF cross cutting concerns

2016-03-11 Thread Christian Schneider
The one with the "${CXFServer} is easy to fix. Simply use address="/invoice/services". This tells CXF to use the Servlet transport. In OSGi this works using the HTTPService. Christian 2016-03-10 19:53 GMT+01:00 Ranx : > Christian, > > Thanks. I'll look into that. Right now all my services are

Re: Camel+Spring Boot route with 2 ActiveMQ brokers on different servers

2016-03-11 Thread Stanisław Kuś
Hi, Do You need it transactional? Best, Stan 10 mar 2016 10:40 PM "jrp256" napisał(a): > I've set up a route that reads from queue A, modifies the message, and > writes > to queue B. Queue A is on one server, queue B on another, so I've > configured > 2 connection factories with different names,

Re: CXF cross cutting concerns

2016-03-11 Thread Ranx
So I tried a little different approach which works but requires that I create my own JAXWS/JAXRS factory which is OK. As a basic outline I have a factory for setting up SOAP/REST services that will the interface/implementation it finds. Right now that basic Microservice interface just has three

Re: Camel XMLRPC dateTime.iso8601 format.

2016-03-11 Thread Claus Ibsen
Hi Ah yeah that was a little bug in camel-xmlrpc. I have just fixed that so it wont set those values to null. Are in 2.16.3 and 2.17.0 releases. On Fri, Mar 11, 2016 at 4:43 PM, Palmentieri Nunzio wrote: > Hi Claus, > maybe it could be a documentation problem. In fact, I found that setting the

Camel, ActiveMQ, JMSBlobMessage

2016-03-11 Thread Stanisław Kuś
Hi all, I have a question: does Camel support JMS BlobMessage out of the box ? What needs to be considered/set up to get it running? Thanks for answers in advance, Best, Stan

Re: ActiveMQ Consuming

2016-03-11 Thread Stanisław Kuś
Hi, I solved it as follows: 1. Each Broker -> One JMSTransactionMager with ConnectionPool. 2. Each Broker -> separated Route 3. Whole construction with SpringTransactionPolicy set in transacted() 4. Routes created & started at runtime Best, Stan On Sat, Feb 13, 2016 at 5:32 PM, Quinn Stevenso

R: Camel XMLRPC dateTime.iso8601 format.

2016-03-11 Thread Palmentieri Nunzio
Hi Claus, maybe it could be a documentation problem. In fact, I found that setting the timeZone=it_IT on the route, it works fine and it's capable to manage date. .to("xmlrpc:http://{{uri}}/?timeZone=it_IT&synchronous=true&basicEncoding=ISO-8859-1&basicUserName=xx&basicPassword=xx&encoding=ISO-88

Re: Camel dozer component unable to map custom function on field with null value

2016-03-11 Thread Ranx
Not being a real JSON expert I can't help much. I don't find the behavior too surprising though as when JSON is marshaled/unmarshaled nulls aren't usually passed from what I've seen. I have a lot more experience with SOAP and XML in Java than with REST/JSON and I'd have a better idea of how to pr

Re: CamelProxy and on Camel 2.16

2016-03-11 Thread Cristiano Costantini
Hi Claus, I know why I didn't found the "binding" attribute on the : In my XML I used this schema location for camel spring: xsi:schemaLocation="http://camel.apache.org/schema/spring http://camel.apache.org/schema/spring/camel-spring.xsd"; I would expect it to point to the last version of Camel

Re: Rest DSL documentation page (CamelHttpTransportServlet and servlet-name).

2016-03-11 Thread Claus Ibsen
We love contributions http://camel.apache.org/contributing See that link how you can help with the documentation. On Fri, Mar 11, 2016 at 12:02 PM, MEL wrote: > I’ve been using the Rest DSL with the CamelHttpTransportServlet and have had > difficulties in getting it working; after spending some

Rest DSL documentation page (CamelHttpTransportServlet and servlet-name).

2016-03-11 Thread MEL
I’ve been using the Rest DSL with the CamelHttpTransportServlet and have had difficulties in getting it working; after spending some time I discovered it only appears to work when the “” in the web.xml is set to “CamelServlet”. I did eventually find the solution on how to change the mapping to som

R: Camel XMLRPC dateTime.iso8601 format.

2016-03-11 Thread Palmentieri Nunzio
Hi, the java code is: XmlRpcConfigImpl.java from "apache-xmlrpc-3.1.2" Nunzio Palmentieri Engineering Ingegneria Informatica S.p.A. Via Emanuele Gianturco, 15 - 80142 Napoli Tel.+39 0816103388 Mob. +39 3351214806 www.eng.it This electronic message contains information from Engineering Ingeg

Re: Camel XMLRPC dateTime.iso8601 format.

2016-03-11 Thread Claus Ibsen
Ah What java code file is that exactly you did that change? On Fri, Mar 11, 2016 at 11:06 AM, Palmentieri Nunzio wrote: > Hi, > I noticed that in the class XmlRpcConfigImpl.java from apache-xmlrpc-3.1.2, > the timeZone is correctly set to the default (Europe/Berlin) at row 33. > > But after, so

R: Camel XMLRPC dateTime.iso8601 format.

2016-03-11 Thread Palmentieri Nunzio
Hi, I noticed that in the class XmlRpcConfigImpl.java from apache-xmlrpc-3.1.2, the timeZone is correctly set to the default (Europe/Berlin) at row 33. But after, some Camel module calls setTimeZone with pTimeZone=null (row 86). I saw it debugging. So, when the getTimeZone() (79) is called, it