Re: Jetty in route not working as expected

[Claus Ibsen]

Make sure to type it correct, eg a colon was missing, and maybe avoid
using port 80, if that is not free on your computer

http://localhost:/test"/>

And use 0.0.0.0 instead of localhost if it should be reachable from
outside the localhost.



On Thu, Dec 10, 2015 at 10:45 PM, rwoolf  wrote:
> I have created a very simple route that uses Jetty to try to learn how to use
> it.  I am trying this in servicemix 6.0.1  My camel context is defined in
> blueprint.  The jetty server instance starts, but I always get 404 error
> when trying to call anything.
>
> In my browser I make a make a request to: http://localhost/test?id=2.
>
> I would expect to get my ID of 2 to be output to the logs, and then the
> response to the browser be the text "Hello World"
>
> But nothing happens in Camel, the route is never called.  What I get back in
> the browser is:
> HTTP ERROR: 404
> Problem accessing /test. Reason:
> Not Found
> Powered by Jetty://
>
> Am I missing something simple?  Do I not understand the use of Jetty
> correctly?  Any help appreciated.
>
> Here is my simple blueprint/camel context
>
> 
>  xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="
>   http://www.osgi.org/xmlns/blueprint/v1.0.0
>   http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd";>
>
> http://camel.apache.org/schema/blueprint";>
>   
> 
> 
> 
>   Hello World
> 
>   
> 
> 
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/Jetty-in-route-not-working-as-expected-tp5774970.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: CamelHttpTransportServlet & split, output not updated

[Claus Ibsen]

See the splitter only example at
http://camel.apache.org/composed-message-processor.html



On Fri, Dec 11, 2015 at 12:42 AM, Lars Hansen  wrote:
> So, I thought I was clever. I have a CamelHttpTransportServlet with a route
> mapped up, it takes parameters with some dates, performs a split, queries a
> MongoDB, an aggregator picks up the results from the two requests and merges
> them. BUT
>
> Whenever I use split, what is printed on the OutputStream is what the body
> was like BEFORE my initial split. I have written a small route to illustrate
> it.
>
> from("servlet:///test")
> .setBody().simple("hello\nworld")
> .split().tokenize("\n")
> .setBody().simple("modified ${body}")
> .aggregate(constant(true),new AggregationStrategy() {
>
> @Override
> public Exchange aggregate(Exchange oldExchange, 
> Exchange newExchange) {
> newExchange.getIn().setBody("aggregated");
> return newExchange;
> }
> }).completionSize(2)
> .setBody().simple("finito ${body}")
> .log("${body}")
>
> It takes the input hello\nworld, splits it in two, it has a rather plain
> AggregationStrategy, that always rejects the exchanges and sets the body to
> "aggregated". When done, the body is rewritten and I would expect the output
> of the Servlet to be "finito aggregated". That is however not the case.
>
> The output is hello\nworld
>
> I am running Camel 2.14.1.
>
> I have enabled full trace and captured the output, I noted this line myself
> /UnitOfWork afterRouteL: route2 for ExchangeId:
> Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 with Exchange[Message: hello/
> which indicates to me that the result is fetched prior to the actual work
> within the split / aggregation pipeline has been executed.
>
> Any ideas are greatly appreciated. Would hate to take a step backwards and
> start injecting beans to do the work and transformations.
>
> [  http-bio-9090-exec-8] CamelHttpTransportServlet  DEBUG
> Service: org.apache.catalina.connector.RequestFacade@48fab4ad
> [  http-bio-9090-exec-8] DefaultHttpBinding DEBUG
> readRequest org.apache.catalina.connector.RequestFacade@48fab4ad
> [  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
> method GET with Content-Type null
> [  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
> method GET
> [  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
> query null
> [  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
> url http://localhost:9090/attribution-web/reports/test
> [  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
> uri /attribution-web/reports/test
> [  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
> path /test
> [  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
> content-type null
> [  http-bio-9090-exec-8] DefaultUnitOfWork  DEBUG
> UnitOfWork created for ExchangeId:
> Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 with Exchange[Message: [Body is
> null]]
> [  http-bio-9090-exec-8] EventHelperDEBUG
> Notification of event is disabled:
> Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 exchange created:
> Exchange[Message: [Body is null]]
> [  http-bio-9090-exec-8] CamelHttpTransportServlet  DEBUG
> Processing request for exchangeId:
> Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1
> [  http-bio-9090-exec-8] DefaultUnitOfWork  DEBUG
> UnitOfWork beforeRoute: route2 for ExchangeId:
> Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 with Exchange[Message: [Body is
> null]]
> [  http-bio-9090-exec-8] CamelInternalProcessor DEBUG
> Processing exchange for exchangeId:
> Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 -> Exchange[Message: [Body is
> null]]
> [  http-bio-9090-exec-8] Pipeline   DEBUG
> ExchangeId: Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 should continue
> routing: true
> [  http-bio-9090-exec-8] Pipeline   DEBUG
> Processing exchangeId: Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 >>>
> Exchange[Message: [Body is null]]
> [  http-bio-9090-exec-8] CamelInternalProcessor DEBUG
> Processing exchange for exchangeId:
> Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 -> Exchange[Message: [Body is
> null]]
> [  http-bio-9090-exec-8] DefaultErrorHandlerDEBUG
> isRunAllowed() -> true (Run allowed if we are not stopped/stopping)
> [  http-bio-9090-exec-8] Tracer INFO
> Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 >>> (route2)
> from(servlet:///test) --> setBody[Simple: hello
> world] <<< Pattern:InOut, Headers:{accept-encoding=gzip, deflate,
> CamelHtt

Re: BAM support across different application running in different CamelContext's

[Claus Ibsen]

No that old camel-bam module should not be used really.

The Camel message include a breadcrumb
http://camel.apache.org/mdc-logging.html

So a way is to include the breadcrumb in the logging so you can track
it from log files.



On Thu, Dec 10, 2015 at 10:10 PM, gilboy  wrote:
> Hi
>
> I have a use case where I need to track an order from a front office system
> to middle and back office systems. The camel BAM module looks like a good
> fit.
>
> But unless I am mistaken it appears to assume that all the routes run within
> the same CamelContext. Does it support having the different routes deployed
> on different CamelContexts on different JVM's
>
> Thanks
> Joe
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/BAM-support-across-different-application-running-in-different-CamelContext-s-tp5774966.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

How to specify the UDP source port in dynamic To (toD)?

[SteveR]

I'm using *Camel 2.16.0*, *camel-netty4*, and the new dynamic *toD()* feature
to send UDP acknowledgements back to the associated UDP client.

In my Camel route that deals with acknowledgements, I have an
*AckBackProcessor* that composes the UDP response to be sent back to the UDP
client.  Right before returning from the *AckBackProcessor* I print out the
*NETTY_LOCAL_ADDRESS* and *NETTY_REMOTE_ADDRESS* headers in the Exchange's
inMsg and they look as expected.

I'm required to use an application-specific well-known UDP source port in
the acknowledgement (e.g. *61133*). However, somehow, after the
*AckBackProcessor* returns and the *toD()* executes, my tcpdump shows that
the UDP source port has changed from *61133* to what looks to be an
ephemeral source port.

So my question is, with *camel-netty4* and the new dynamic *toD()* feature,
how do I specify a UDP source port of my choosing?

Here's what my route looks like.  It's a SEDA queue:

from(ackQueueURI) 
.setExchangePattern(ExchangePattern.InOnly)
.id("setExchangePattern_" + ackQueueRouteId)
.routeId(ackQueueRouteId)
.startupOrder(ackQueueRouteStartupOrder)
.setProperty(Exchange.CHARSET_NAME,
ExpressionBuilder.constantExpression(charsetName))
.id("setProperty_" + ackQueueRouteId + "_" + 
charsetName)
 // AckBackProcessor formulates the UDP ack and does
setHeader("ACK_REQUIRED") to "true" or "false"
.process(ackBackProcessor).id(ackBackProcessorId)
.choice()
.when(header("ACK_REQUIRED").isEqualTo("false"))
.to("log:DEV_NULL_LOG?level=OFF") // Drop UDP 
packet since ack is not
required
.otherwise()
// Otherwise, this UDP request requires an 
acknowledgement.
// Dynamic To does remote address substitution 
from the in-flight
exchange header.
.toD(ackToURI).id("toD_" + ackQueueRouteId + 
"_TO_CLIENT")
.end();


Here's the method used to create the acknowledgement URI referenced within
the *toD(*):

/**
 * Builds and returns the string containing the acknowledgment to URI.
 *
 * @param dest
 * @param clientPipelineFactoryName
 * @return  The string containing the ackToURI
 */
private String getAckToURI(Destination dest, String
clientPipelineFactoryName) {
StringBuilder sb = new StringBuilder();

   
sb.append("netty4:udp").append(":/${header.CamelNettyRemoteAddress}")
 
.append("?clientPipelineFactory=#").append(clientPipelineFactoryName);

String ackOptions = dest.getOptions();
if(ackOptions != null && !ackOptions.isEmpty()) {
sb.append(ackOptions);
}

String ackExtraOptions = dest.getExtraOptions();
if(ackExtraOptions != null && !ackExtraOptions.isEmpty()) {
sb.append(ackExtraOptions);
}

logger.info("getAckToURI(): ackToURI = {}", sb.toString());
return sb.toString();
}



--
View this message in context: 
http://camel.465427.n5.nabble.com/How-to-specify-the-UDP-source-port-in-dynamic-To-toD-tp5774964.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Placeholder of Camel from tag is not getting updated with new values

[siddhesh]

Pals, is this the issue same as mentioned in  defect  CAMEL-9124
   ? 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Placeholder-of-Camel-from-tag-is-not-getting-updated-with-new-values-tp5774909p5774973.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Shutdown sequence when running Camel in Springboot

[raffi]

Nevermind, figured it out from this article:

http://www.javacodegeeks.com/2014/10/spring-boot-actuator-custom-endpoint-with-mvc-layer-on-top-of-it.html





--
View this message in context: 
http://camel.465427.n5.nabble.com/Shutdown-sequence-when-running-Camel-in-Springboot-tp5774960p5774974.html
Sent from the Camel - Users mailing list archive at Nabble.com.

CamelHttpTransportServlet & split, output not updated

[Lars Hansen]

So, I thought I was clever. I have a CamelHttpTransportServlet with a route
mapped up, it takes parameters with some dates, performs a split, queries a
MongoDB, an aggregator picks up the results from the two requests and merges
them. BUT

Whenever I use split, what is printed on the OutputStream is what the body
was like BEFORE my initial split. I have written a small route to illustrate
it.

from("servlet:///test")
.setBody().simple("hello\nworld")
.split().tokenize("\n")
.setBody().simple("modified ${body}")
.aggregate(constant(true),new AggregationStrategy() {

@Override
public Exchange aggregate(Exchange oldExchange, 
Exchange newExchange) {
newExchange.getIn().setBody("aggregated");
return newExchange;
}
}).completionSize(2)
.setBody().simple("finito ${body}")
.log("${body}")

It takes the input hello\nworld, splits it in two, it has a rather plain
AggregationStrategy, that always rejects the exchanges and sets the body to
"aggregated". When done, the body is rewritten and I would expect the output
of the Servlet to be "finito aggregated". That is however not the case.

The output is hello\nworld

I am running Camel 2.14.1.

I have enabled full trace and captured the output, I noted this line myself
/UnitOfWork afterRouteL: route2 for ExchangeId:
Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 with Exchange[Message: hello/
which indicates to me that the result is fetched prior to the actual work
within the split / aggregation pipeline has been executed.

Any ideas are greatly appreciated. Would hate to take a step backwards and
start injecting beans to do the work and transformations.

[  http-bio-9090-exec-8] CamelHttpTransportServlet  DEBUG
Service: org.apache.catalina.connector.RequestFacade@48fab4ad
[  http-bio-9090-exec-8] DefaultHttpBinding DEBUG
readRequest org.apache.catalina.connector.RequestFacade@48fab4ad
[  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
method GET with Content-Type null
[  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
method GET
[  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
query null
[  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
url http://localhost:9090/attribution-web/reports/test
[  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
uri /attribution-web/reports/test
[  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
path /test
[  http-bio-9090-exec-8] DefaultHttpBinding DEBUG HTTP
content-type null
[  http-bio-9090-exec-8] DefaultUnitOfWork  DEBUG
UnitOfWork created for ExchangeId:
Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 with Exchange[Message: [Body is
null]]
[  http-bio-9090-exec-8] EventHelperDEBUG
Notification of event is disabled:
Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 exchange created:
Exchange[Message: [Body is null]]
[  http-bio-9090-exec-8] CamelHttpTransportServlet  DEBUG
Processing request for exchangeId:
Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1
[  http-bio-9090-exec-8] DefaultUnitOfWork  DEBUG
UnitOfWork beforeRoute: route2 for ExchangeId:
Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 with Exchange[Message: [Body is
null]]
[  http-bio-9090-exec-8] CamelInternalProcessor DEBUG
Processing exchange for exchangeId:
Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 -> Exchange[Message: [Body is
null]]
[  http-bio-9090-exec-8] Pipeline   DEBUG
ExchangeId: Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 should continue
routing: true
[  http-bio-9090-exec-8] Pipeline   DEBUG
Processing exchangeId: Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 >>>
Exchange[Message: [Body is null]]
[  http-bio-9090-exec-8] CamelInternalProcessor DEBUG
Processing exchange for exchangeId:
Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 -> Exchange[Message: [Body is
null]]
[  http-bio-9090-exec-8] DefaultErrorHandlerDEBUG
isRunAllowed() -> true (Run allowed if we are not stopped/stopping)
[  http-bio-9090-exec-8] Tracer INFO 
Id-Lorem-Ipsum-w7016-64641-1449789898589-0-1 >>> (route2)
from(servlet:///test) --> setBody[Simple: hello
world] <<< Pattern:InOut, Headers:{accept-encoding=gzip, deflate,
CamelHttpQuery=null,
breadcrumbId=Id-Lorem-Ipsum-w7016-64641-1449789898589-0-2,
CamelHttpUrl=http://localhost:9090/attribution-web/reports/test,
Content-Type=null, CamelHttpMethod=GET, user-agent=Mozilla/5.0 (Windows NT
6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0,
CamelHttpUri=/attribution-web/reports/test,

Jetty in route not working as expected

[rwoolf]

I have created a very simple route that uses Jetty to try to learn how to use
it.  I am trying this in servicemix 6.0.1  My camel context is defined in
blueprint.  The jetty server instance starts, but I always get 404 error
when trying to call anything.

In my browser I make a make a request to: http://localhost/test?id=2.

I would expect to get my ID of 2 to be output to the logs, and then the
response to the browser be the text "Hello World"

But nothing happens in Camel, the route is never called.  What I get back in
the browser is:
HTTP ERROR: 404
Problem accessing /test. Reason:
Not Found
Powered by Jetty://

Am I missing something simple?  Do I not understand the use of Jetty
correctly?  Any help appreciated.

Here is my simple blueprint/camel context


http://www.osgi.org/xmlns/blueprint/v1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="
  http://www.osgi.org/xmlns/blueprint/v1.0.0
  http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd";>

http://camel.apache.org/schema/blueprint";>
  



  Hello World
  
  





--
View this message in context: 
http://camel.465427.n5.nabble.com/Jetty-in-route-not-working-as-expected-tp5774970.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Shutdown sequence when running Camel in Springboot

[raffi]

Yeah, I see that working now, just POST to "/shutdown" and springboot shuts
everything down, including Camel.

The problem with SB's shutdown endpoint is, although it stops Camel first,
then the JVM, the initial request to `/shutdown` returns immediately, but
the time between the request and when the JVM terminates can take up to 60s,
sometimes more, and that's a problem for our deployment scripts. But if I
shutdown Camel from JMX, then shutdown SB from "/shutdown", it's much more
predictable.

I want to override Springboot's shutdown process with custom code to
shutdown Camel manually from JMX. Doing so blocks until Camel is shutdown,
and that's what I'm after, except I can't figure out how to override
Springboot's shutdown sequence.   



--
View this message in context: 
http://camel.465427.n5.nabble.com/Shutdown-sequence-when-running-Camel-in-Springboot-tp5774960p5774968.html
Sent from the Camel - Users mailing list archive at Nabble.com.

BAM support across different application running in different CamelContext's

[gilboy]

Hi

I have a use case where I need to track an order from a front office system
to middle and back office systems. The camel BAM module looks like a good
fit. 

But unless I am mistaken it appears to assume that all the routes run within
the same CamelContext. Does it support having the different routes deployed
on different CamelContexts on different JVM's

Thanks
Joe



--
View this message in context: 
http://camel.465427.n5.nabble.com/BAM-support-across-different-application-running-in-different-CamelContext-s-tp5774966.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Shutdown sequence when running Camel in Springboot

[Henryk Konsek]

Yes. CamelContext is wired as a Spring bean with registered shutdown
method, so calling Spring's shutdown will close CamelContext in the first
place before closing Spring context.

Cheers!

czw., 10.12.2015 o 20:25 użytkownik raffi  napisał:

> With respect to graceful shutdown, does Springboot hook into Camel such
> that
> invoking Springboot's standard "/shutdown" endpoint automatically shuts
> down
> Camel first, then the JVM?
>
> Trying to understand if explicit shutdown hooks are requried.
>
> Best
> Raffi
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Shutdown-sequence-when-running-Camel-in-Springboot-tp5774960.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
-- 
Henryk Konsek
http://about.me/hekonsek

Re: The Camel Name - Just A Thought

[Henryk Konsek]

Whoever is the smoker you refer to, he has great taste in cigarettes. I
also used to be chain-smokers of Camels several years ago ;) .

Cheers!

czw., 10.12.2015 o 16:48 użytkownik Claus Ibsen 
napisał:

> On Thu, Dec 10, 2015 at 4:39 PM, Raul Kripalani  wrote:
> > I would also venture a guess that the name Camel has something to do with
> > another platform called Mule back in 2006-2007 :)
> >
>
> Only one person really knows. And he was smooking cigarettes back then ;)
> But yeah a Camel is the strongest of all the beast of burdens. Mules
> are dumb ass donkeys.
>
>
>
> > Regards,
> > Raúl.
> >
> > On Thu, Dec 10, 2015 at 3:26 PM, Claus Ibsen 
> wrote:
> >
> >> Yeah and there is some other reasons here
> >> http://camel.apache.org/why-the-name-camel.html
> >>
> >> On Thu, Dec 10, 2015 at 4:10 PM, gbchriste 
> >> wrote:
> >> > Section 1.1 of Camel In Action says, "The Apache Camel project was
> named
> >> > Camel simply because the name is short and easy to remember."
> >> >
> >> > But here's a thought.  When you think about it, the name "Camel" is so
> >> > appropriate to the notion of what Camel does that you'd think the name
> >> was
> >> > chosen on purpose.  Even the picture of the Bedouin fits.
> >> >
> >> > For the nomadic, desert-dwelling people of ages past, the camel was
> the
> >> key
> >> > method of transport, and was essential to creating and maintaining the
> >> lines
> >> > of communication that connected distant communities.  Individuals,
> >> families,
> >> > trade goods of all kinds, and messages were all carried back and
> forth by
> >> > caravans of camels.
> >> >
> >> >
> >> >
> >> > --
> >> > View this message in context:
> >>
> http://camel.465427.n5.nabble.com/The-Camel-Name-Just-A-Thought-tp5774938.html
> >> > Sent from the Camel - Users mailing list archive at Nabble.com.
> >>
> >>
> >>
> >> --
> >> Claus Ibsen
> >> -
> >> http://davsclaus.com @davsclaus
> >> Camel in Action 2: https://www.manning.com/ibsen2
> >>
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>
-- 
Henryk Konsek
http://about.me/hekonsek

Shutdown sequence when running Camel in Springboot

[raffi]

With respect to graceful shutdown, does Springboot hook into Camel such that
invoking Springboot's standard "/shutdown" endpoint automatically shuts down
Camel first, then the JVM?

Trying to understand if explicit shutdown hooks are requried. 

Best
Raffi



--
View this message in context: 
http://camel.465427.n5.nabble.com/Shutdown-sequence-when-running-Camel-in-Springboot-tp5774960.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Configuring Camel-Swagger

[Anthony Clegg]

Unfortunately this is completely different from our situation, I have already
looked at this example. We are using JBoss Fuse 2.1 released on the 7th Dec
2015. We are using osgi bundles and only have the camel rest dsl in our
camel context. I want to know how to configure swagger in this environment.
We had this working on our old technology stack where we had a war file and
an application context run through Tomcat. Now we are using bundles wrapped
into jar files placed into the deploy folder of the JBoss fuse karaf
environment. 

Thanks for your repsonse.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Configuring-Camel-Swagger-tp5774922p5774959.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Configuring Camel-Swagger

[Greg Autric]

Hi Antony

have you ever seen the camel-example-swagger-java ?
It looks like the same as yours.

best regards,

Greg AUTRIC
JBoss Middleware Consultant

email   : gautric __at__ redhat __dot__ com
twitter : @gautric_io

Red Hat Global Services
Red Hat France SARLsit: http://www.redhat.fr
Le Linea, 1 rue du General Leclerc, 92047 Paris La Défense Cedex
Sent from webmail

- Mail original -
De: "Anthony Clegg" 
À: users@camel.apache.org
Envoyé: Jeudi 10 Décembre 2015 14:23:40
Objet: Configuring Camel-Swagger

I have just downloaded the latest JBoss Fuse Environment 6.2.1 and I am told
that swagger now works? The red hat documentation
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2/html/Apache_Camel_Component_Reference/IDU-Swagger.html
is suggesting using camel-swagger however this is documented as being
deprecated? 

Also I am using a spring xml context file for my dependency injection and
not blueprint.

I have all my POJO's annotated correctly for swagger so could anyone please
help me get swagger working.

Here is my xml

http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:cxf="http://camel.apache.org/schema/cxf";
xmlns:osgi="http://www.springframework.org/schema/osgi"; 
xmlns:context="http://www.springframework.org/schema/context";
xmlns:tx="http://www.springframework.org/schema/tx";
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd 
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx.xsd
  ">
http://camel.apache.org/schema/spring";>

 
java.lang.Throwable

true












































 




















   











--
View this message in context: 
http://camel.465427.n5.nabble.com/Configuring-Camel-Swagger-tp5774922.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Route Setup Advice

[gbchriste]

I like the succinctness of this but I think I'll stick with an explicit route
for each messagtype/processor for now.  One of the main goals I'm trying to
achieve is to straighten out and clarify a rather convoluted and
difficult-to-comprehend pile of code created by the contractor that wrote
the original application.  It has taken me literally over a year to get to
the point where I can follow through all the twists and turns that it takes. 
So I want my fix to be clear and immediately understandable by the next
person that has to take this over.  

As I get further in I may decide to use this more elegant approach but for
now I think having the message type and target processor specified in the
route will help achieve one of my main goal.

Thanks for the input! 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Route-Setup-Advice-tp5774950p5774957.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: The Camel Name - Just A Thought

[Preben.Asmussen]

yeah - but donkeys seems to have friends in high places.

I just got slides from latest Gartner conference with reference product
slides
snippet from slides ->

API Manager:
  – Apigee
  – TIBCO (Mashery)

API Gateway:
  – CA (Layer 7)
  – Axway (Vordel)

ESB Suite:
  – Oracle SOA Suite
  – Software AG WebMethods

iPaaS:
  – MuleSoft Cloud
  – Dell Boomi

A whole lot of expensive, hard to operate donkey software.
  



--
View this message in context: 
http://camel.465427.n5.nabble.com/The-Camel-Name-Just-A-Thought-tp5774938p5774956.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Route Setup Advice

[gbchriste]

Yes.  If you look at the example code I have 2 routes, one subscribing to
activemq:topic:fastmessages and one subscribing to
activemq:topic:slowmessages

All of the messages coming down the pipe from the fastmessages topic go
straight to the handler for that message type.  In the real app this happens
to be a steady stream of air traffic data with each message carrying
latitude, longitude, altitude, speed, et al for an aircraft, and gets passed
through to a method that plots the target up on a map display.

Messages coming down the pipe from the slowmessages are of various
informational content and will get routed and processed according to their
content.

The backend service that is publishing the messages put each message in to
the appropriate topic, and also set the messagetype header if it is a
slowmessage



--
View this message in context: 
http://camel.465427.n5.nabble.com/Route-Setup-Advice-tp5774950p5774955.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Route Setup Advice

[Greg Autric]

Hi Gary,

You can also use more dynamic stuff for slow messages route

from("direct:slowMessage").toD("bean:foo?method=Process${header.MessageType}");

but you have to check ${header.MessageType} to avoid NoSuchMethod

as riddellg said, I think Client just wants push message without thinking about 
slow or fast messages.
  
best regards,

Greg AUTRIC
JBoss Middleware Consultant

email   : gautric __at__ redhat __dot__ com
twitter : @gautric_io

Red Hat Global Services
Red Hat France SARLsit: http://www.redhat.fr
Le Linea, 1 rue du General Leclerc, 92047 Paris La Défense Cedex
Sent from webmail

- Mail original -
De: "gbchriste" 
À: users@camel.apache.org
Envoyé: Jeudi 10 Décembre 2015 17:53:43
Objet: Route Setup Advice

The application I'm dealing with receives and processes XML messages from a
back end service.  The messages fall in to 2 basic categories which I'll
call fast messages and slow messages.

Fast messages are all of the same type and format, just different values in
the XML elements.  They are all handled by the same internal process.  They
arrive from the back end at the rate of about 40 per second.

Slow messages can be one of about 7 or 8 different types and formats but
only arrive at the rate of about 1 every 3 minutes, and each is handled by a
different internal process.  

Given the rate of arrival of fast messages and the consistency of
processing, I don't want to waist time filtering those out from the rest.  
And conversely, given the slower rate of arrival of slow messages, I see no
harm in taking the time to filter those.

So I'm thinking of establishing 2 routes for the incoming messages.  One
route dedicated just to the fast messages, and a second route for slow
messages that applies a selector to send each to it's required processor.

Here's something along the lines of what I have in mind:


from("activemq:topic:fastmessages").bean("MessageProcessor.class,
"ProcessFastMessage);

from("activemq:topic:slowmessages").choice()
.when(header("MessageType").isEqualTo("SlowMessage1"))
 .bean(MessageProcessor.class, "ProcessSlowMessage1")
.when(header("MessageType").isEqualTo("SlowMessage2"))
  .bean(MessageProcessor.class, "ProcessMessage2")
.when(header("MessageType).isEqualTo("SlowMessage3"))
  .bean(MessageProcessor.class, "ProcessMessage3");


Advisable?  Yes/No?  Any pitfalls or traps I need to lookout for?

Any and all help appreciated.

Thanks,

Gary




--
View this message in context: 
http://camel.465427.n5.nabble.com/Route-Setup-Advice-tp5774950.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Route Setup Advice

[riddellg]

Implied from your sample but just checking - you're planning on using MQ
topics to separate the 2 classes of message? Makes it really simple on the
service side (I like what you have) but the client does need to be aware of
the topics and publish to the correct one. 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Route-Setup-Advice-tp5774950p5774952.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: The Camel Name - Just A Thought

[Mark Frazier]

Point, Set, and Match: Claus.

> On Dec 10, 2015, at 7:47 AM, Claus Ibsen  wrote:
>> 
> But yeah a Camel is the strongest of all the beast of burdens. Mules
> are dumb ass donkeys.

Route Setup Advice

[gbchriste]

The application I'm dealing with receives and processes XML messages from a
back end service.  The messages fall in to 2 basic categories which I'll
call fast messages and slow messages.

Fast messages are all of the same type and format, just different values in
the XML elements.  They are all handled by the same internal process.  They
arrive from the back end at the rate of about 40 per second.

Slow messages can be one of about 7 or 8 different types and formats but
only arrive at the rate of about 1 every 3 minutes, and each is handled by a
different internal process.  

Given the rate of arrival of fast messages and the consistency of
processing, I don't want to waist time filtering those out from the rest.  
And conversely, given the slower rate of arrival of slow messages, I see no
harm in taking the time to filter those.

So I'm thinking of establishing 2 routes for the incoming messages.  One
route dedicated just to the fast messages, and a second route for slow
messages that applies a selector to send each to it's required processor.

Here's something along the lines of what I have in mind:


from("activemq:topic:fastmessages").bean("MessageProcessor.class,
"ProcessFastMessage);

from("activemq:topic:slowmessages").choice()
.when(header("MessageType").isEqualTo("SlowMessage1"))
 .bean(MessageProcessor.class, "ProcessSlowMessage1")
.when(header("MessageType").isEqualTo("SlowMessage2"))
  .bean(MessageProcessor.class, "ProcessMessage2")
.when(header("MessageType).isEqualTo("SlowMessage3"))
  .bean(MessageProcessor.class, "ProcessMessage3");


Advisable?  Yes/No?  Any pitfalls or traps I need to lookout for?

Any and all help appreciated.

Thanks,

Gary




--
View this message in context: 
http://camel.465427.n5.nabble.com/Route-Setup-Advice-tp5774950.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: The Camel Name - Just A Thought

[Donald Whytock]

On Thu, Dec 10, 2015 at 10:47 AM, Claus Ibsen  wrote:

> On Thu, Dec 10, 2015 at 4:39 PM, Raul Kripalani  wrote:
> > I would also venture a guess that the name Camel has something to do with
> > another platform called Mule back in 2006-2007 :)
> >
>
> Only one person really knows. And he was smooking cigarettes back then ;)
> But yeah a Camel is the strongest of all the beast of burdens. Mules
> are dumb ass donkeys.
>

Not to mention incapable of reproduction.  Whereas Camel's still producing
new releases.

JUnit, Interceptors and Notifys in a webapp

[riddellg]

I love the Interceptors and Notifys when running a Spring DSL camel
application standalone under JUnit. However our operational deployment model
is as a war/webapp rather than a standalone Spring app. I am trying to
figure out how to attach Interceptors and Notifiers from a JUnit test onto a
route that is running in a webapp.

I can start Tomcat from the JUnit setup() and publish my war into it, and
the route starts up. (I'm using the CamelTestSpringSupport for JUnit, and
using the "tomcat-embed-core" dependency to start Tomcat from JUnit). 
However in my JUnit test class I have to instantiate an
AbstractXMLApplicationContext which starts a new CamelContext, even though I
am referencing the same camel config file. So my JUnit client is not
actually hitting the code running in the webapp. Is it possible to get a
handle from the JUnit test code to the CamelContext that is running under
Tomcat? And pass that back in the "createApplicationContext". 

As far as I can tell the Tomcat that is started is in the same JVM, and the
camel route is auto-assigned a name ("camel-1") and then "camel-3" for the
JUnit one, so it seems that the CamelContexts might be aware of each other.

Some code below showing what I'm trying to do. Anyone know if this is
possible?



public class TestEmailServiceIntercept extends CamelSpringTestSupport {

@Override
protected AbstractXmlApplicationContext createApplicationContext() 
{
return new ClassPathXmlApplicationContext("camel-config.xml");
}

@Test
public void testCloudantException() throws Exception 
{
RouteDefinition route = context.getRouteDefinition("main");
route.adviceWith(context, new RouteBuilder()
{
public void configure() throws Exception
{

interceptSendToEndpoint("bean:cloudantClient?method=storeToCloudant")
.process(new 
SimulateCloudantResponseProcessor("EXCEPTION"));
}
});

thanks for any help,



--
View this message in context: 
http://camel.465427.n5.nabble.com/JUnit-Interceptors-and-Notifys-in-a-webapp-tp5774946.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: The Camel Name - Just A Thought

[Claus Ibsen]

On Thu, Dec 10, 2015 at 4:39 PM, Raul Kripalani  wrote:
> I would also venture a guess that the name Camel has something to do with
> another platform called Mule back in 2006-2007 :)
>

Only one person really knows. And he was smooking cigarettes back then ;)
But yeah a Camel is the strongest of all the beast of burdens. Mules
are dumb ass donkeys.



> Regards,
> Raúl.
>
> On Thu, Dec 10, 2015 at 3:26 PM, Claus Ibsen  wrote:
>
>> Yeah and there is some other reasons here
>> http://camel.apache.org/why-the-name-camel.html
>>
>> On Thu, Dec 10, 2015 at 4:10 PM, gbchriste 
>> wrote:
>> > Section 1.1 of Camel In Action says, "The Apache Camel project was named
>> > Camel simply because the name is short and easy to remember."
>> >
>> > But here's a thought.  When you think about it, the name "Camel" is so
>> > appropriate to the notion of what Camel does that you'd think the name
>> was
>> > chosen on purpose.  Even the picture of the Bedouin fits.
>> >
>> > For the nomadic, desert-dwelling people of ages past, the camel was the
>> key
>> > method of transport, and was essential to creating and maintaining the
>> lines
>> > of communication that connected distant communities.  Individuals,
>> families,
>> > trade goods of all kinds, and messages were all carried back and forth by
>> > caravans of camels.
>> >
>> >
>> >
>> > --
>> > View this message in context:
>> http://camel.465427.n5.nabble.com/The-Camel-Name-Just-A-Thought-tp5774938.html
>> > Sent from the Camel - Users mailing list archive at Nabble.com.
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> http://davsclaus.com @davsclaus
>> Camel in Action 2: https://www.manning.com/ibsen2
>>



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

Re: The Camel Name - Just A Thought

[Raul Kripalani]

I would also venture a guess that the name Camel has something to do with
another platform called Mule back in 2006-2007 :)

Regards,
Raúl.

On Thu, Dec 10, 2015 at 3:26 PM, Claus Ibsen  wrote:

> Yeah and there is some other reasons here
> http://camel.apache.org/why-the-name-camel.html
>
> On Thu, Dec 10, 2015 at 4:10 PM, gbchriste 
> wrote:
> > Section 1.1 of Camel In Action says, "The Apache Camel project was named
> > Camel simply because the name is short and easy to remember."
> >
> > But here's a thought.  When you think about it, the name "Camel" is so
> > appropriate to the notion of what Camel does that you'd think the name
> was
> > chosen on purpose.  Even the picture of the Bedouin fits.
> >
> > For the nomadic, desert-dwelling people of ages past, the camel was the
> key
> > method of transport, and was essential to creating and maintaining the
> lines
> > of communication that connected distant communities.  Individuals,
> families,
> > trade goods of all kinds, and messages were all carried back and forth by
> > caravans of camels.
> >
> >
> >
> > --
> > View this message in context:
> http://camel.465427.n5.nabble.com/The-Camel-Name-Just-A-Thought-tp5774938.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
>
>
>
> --
> Claus Ibsen
> -
> http://davsclaus.com @davsclaus
> Camel in Action 2: https://www.manning.com/ibsen2
>

Re: The Camel Name - Just A Thought

[Claus Ibsen]

Yeah and there is some other reasons here
http://camel.apache.org/why-the-name-camel.html

On Thu, Dec 10, 2015 at 4:10 PM, gbchriste  wrote:
> Section 1.1 of Camel In Action says, "The Apache Camel project was named
> Camel simply because the name is short and easy to remember."
>
> But here's a thought.  When you think about it, the name "Camel" is so
> appropriate to the notion of what Camel does that you'd think the name was
> chosen on purpose.  Even the picture of the Bedouin fits.
>
> For the nomadic, desert-dwelling people of ages past, the camel was the key
> method of transport, and was essential to creating and maintaining the lines
> of communication that connected distant communities.  Individuals, families,
> trade goods of all kinds, and messages were all carried back and forth by
> caravans of camels.
>
>
>
> --
> View this message in context: 
> http://camel.465427.n5.nabble.com/The-Camel-Name-Just-A-Thought-tp5774938.html
> Sent from the Camel - Users mailing list archive at Nabble.com.



-- 
Claus Ibsen
-
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2

The Camel Name - Just A Thought

[gbchriste]

Section 1.1 of Camel In Action says, "The Apache Camel project was named
Camel simply because the name is short and easy to remember."

But here's a thought.  When you think about it, the name "Camel" is so
appropriate to the notion of what Camel does that you'd think the name was
chosen on purpose.  Even the picture of the Bedouin fits.

For the nomadic, desert-dwelling people of ages past, the camel was the key
method of transport, and was essential to creating and maintaining the lines
of communication that connected distant communities.  Individuals, families,
trade goods of all kinds, and messages were all carried back and forth by
caravans of camels.



--
View this message in context: 
http://camel.465427.n5.nabble.com/The-Camel-Name-Just-A-Thought-tp5774938.html
Sent from the Camel - Users mailing list archive at Nabble.com.

ActiveMQ Component Questions

[gbchriste]

Total newbie here with Camel and ActiveMQ.  I've done a bit of prototyping
coding directly against ActiveMQ in Java and .Net but now that I'm thinking
of folding Camel into my plans, I've started looking at the Camel ActiveMQ
component.

Couple of questions.  First, does activemq use a default broker of
tcp://localhost:61616 if I don't otherwise specify?  The reason I'm asking
is I inadvertantly commented out the context.addComponent("activemq",...)
part of my code but I was still able to publish a message to an ActiveMQ
broker running at localhost:61616 and consume it.  My working trial code is
as follows where I'm just posting the body of a file to a topic and then
consuming it back to be processed by a bean:

_context = new DefaultCamelContext();
//_context.addComponent("activemq",
ActiveMQComponent.activeMQComponent("tcp://localhost:61616"));

   

_context.addRoutes(new RouteBuilder() {;
@Override
public void configure() {
 
from("file:e:\\data\\inbox?noop=true").convertBodyTo(String.class).to("activemq:topic:myfile");
 
from("activemq:topic:myfile").bean(ProcessMessage.class);

}
});

I have 2 routes - one reads the contents of a file and sends to
topic:myfile, the other consumes from topic:myfile and sends it a bean.  You
can see that I left _context.addComponent commented out but the publish and
subscribe still works.

Second, am I correct in my understanding that if I'm using the ActiveMQ
component instead of the JMS component then connection pooling is
automatically turned on?  If so, how do I configure the pool properties?  I
need examples in Java DSL rather than Spring as my intent is to do all my
Camel configuration via Java.

I'm already drinking out of a fire hose trying to wrap my head around the
Camel and ActiveMQ pieces and don't want to insert yet another platform
technology (i.e. Spring) in to the mix at this point.

Thanks,

Gary



--
View this message in context: 
http://camel.465427.n5.nabble.com/ActiveMQ-Component-Questions-tp5774930.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Using Stream Cache With Apache Camel

[kikou1984]

Hi Claus,

Well, the main purpose is to read a file block by block (for exemple, each
10 Mo) , for that i thought to use the splitter for split sub message, then
for other business process, i need to reload the file from the begining (not
really from the beginning but some date that has already be splitted) , for
exemple i need to retrieve the first line to make some operations ,
therefore i thought using streamcache.

I can't parsing many time the same File , because it takes a lot of memory
,mainly in the world of banking , we use very large files , so we have to
use splitter then find away to use the stream cache.

So , do you have an example about Stream cache, how can i put some data ( I
think we have to add on the route streamCache="true") and how can i retrieve
it.

Thxs.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Using-Stream-Cache-With-Apache-Camel-tp5774856p5774923.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Configuring Camel-Swagger

[Anthony Clegg]

I have just downloaded the latest JBoss Fuse Environment 6.2.1 and I am told
that swagger now works? The red hat documentation
https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.2/html/Apache_Camel_Component_Reference/IDU-Swagger.html
is suggesting using camel-swagger however this is documented as being
deprecated? 

Also I am using a spring xml context file for my dependency injection and
not blueprint.

I have all my POJO's annotated correctly for swagger so could anyone please
help me get swagger working.

Here is my xml

http://www.springframework.org/schema/beans";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; 
xmlns:cxf="http://camel.apache.org/schema/cxf";
xmlns:osgi="http://www.springframework.org/schema/osgi"; 
xmlns:context="http://www.springframework.org/schema/context";
xmlns:tx="http://www.springframework.org/schema/tx";
xsi:schemaLocation="
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd 
http://camel.apache.org/schema/spring
http://camel.apache.org/schema/spring/camel-spring.xsd
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd
http://camel.apache.org/schema/cxf
http://camel.apache.org/schema/cxf/camel-cxf.xsd
http://www.springframework.org/schema/context
http://www.springframework.org/schema/context/spring-context-3.0.xsd
http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx.xsd
  ">
http://camel.apache.org/schema/spring";>

 
java.lang.Throwable

true












































 




















   











--
View this message in context: 
http://camel.465427.n5.nabble.com/Configuring-Camel-Swagger-tp5774922.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel cxfrs proxy response

[Sergey Beryozkin]

Hi

Unfortunately I'm very busy right now with the other project so I can't 
help with investigating, can you please get Camel source and trace what 
is happening ?
It looks like the body is consumed somehow after a CXFRS call returns, 
may be the stream is cached, etc... Let us know if you can get to the 
bottom of it...
The only comment I can make is that in newer Camel releases one does not 
have to type no-op method implementations and having the interface or 
even or CXF specific model is sufficient, with RST DSL work pending to 
be completed a bit later on. This is not relevant to this issue though...


Thanks, Sergey

On 10/12/15 02:46, hoomanb wrote:

Hi Sergey,

Thanks for your reply on this, on the link that you have mentioned the
solution appears to be setting the Response return type for the the
controller, however this doesn't seem to work in my case. In

.bean(new ProcessJsonResponse(), "processBody")

I'm basically returning the result as Response object:

return Response.status(Status.OK).entity(MyObjectList).build();

additionally I thought I might change the return type of my controller as
well:

@GET
 @Path("/{objectId}")
 @Produces(MediaType.APPLICATION_JSON)
 public Response getMyObject(@PathParam("objectId") String objectId)
{
 return null;

 }

I'm receiving the 200 Response back but the result is null. When I debug
this in unit test I'll see this:

Response.status(Status.OK).entity(MyObjectList).build();

contains the result. Deploying the solution into fuse and hitting the REST
service only seems to return headers:

12:20:20,663 | INFO  | qtp790919676-179 | LoggingOutInterceptor|
118 - org.apache.cxf.cxf-core - xxx | Outbound Message
---
ID: 4
Response-Code: 200
Content-Type:
Headers: {operationNamespace=[xxx], Host=[localhost:9002],
breadcrumbId=[ID-xxx-50363-1449711439513-3-1], User-Agent=[curl/7.27.0],
objectId=[xxx], X-Powered-By=[ASP.NET], Server=[Microsoft-IIS/7.0],
Cache-Control=[private, max-age=0], X-AspNet-Version=[4.0.30319],
ResponseContext=[{xxx, org.apache.cxf.service.model.MessageInfo=[MessageInfo
OUTPUT: {xxx], schema-validation-enabled=NONE, org.apache.cxf.client=true,
org.apache.cxf.message.inbound=true,
org.apache.cxf.message.Message.PROTOCOL_HEADERS={Cache-Control=[private,
max-age=0], Content-Length=[1559], content-type=[text/xml; charset=utf-8],
Date=[Thu, 10 Dec 2015 02:20:15 GMT], Server=[Microsoft-IIS/7.0],
X-AspNet-Version=[4.0.30319], X-Powered-By=[ASP.NET]},
org.apache.cxf.interceptor.LoggingMessage.ID=6,
javax.xml.ws.wsdl.service={xxx,
org.apache.cxf.binding.soap.SoapVersion=org.apache.cxf.binding.soap.Soap11@62090db0,
org.apache.cxf.message.Message.ENCODING=UTF-8,
javax.xml.ws.wsdl.interface={xxx, javax.xml.ws.wsdl.operation={xxx}xxx,
javax.xml.ws.wsdl.description=xxx?wsdl,
org.apache.cxf.service.model.BindingMessageInfo=org.apache.cxf.service.model.BindingMessageInfo@138eb4b0,
Content-Type=text/xml; charset=utf-8, org.apache.cxf.headers.Header.list=[],
org.apache.cxf.message.Message.RESPONSE_CODE=200}], Date=[Thu, 10 Dec 2015
02:20:15 GMT], SOAPAction=[xxx], Accept=[application/json],
org.apache.cxf.headers.Header.list=[[]], Content-Length=[0]}

please correct me if I misunderstood you.

Thanks
Hooman




--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-cxfrs-proxy-response-tp5774775p5774883.html
Sent from the Camel - Users mailing list archive at Nabble.com.




--
Sergey Beryozkin

Talend Community Coders
http://coders.talend.com/

Placeholder of Camel from tag is not getting updated with new values

[siddhesh]

Hi All, 
I have my publicAddress property defined in Spring XML and using it in Java
DSL(Route builders). Value of 'publicAddress' comes from Web GUI.




I was previously using Camel 2.10 and have switched to 2.15.

Following code is used to create Route builders which has different public
addresses. With this code in place, if I create second Route builder, value
of 'publicAddress' does not gets updated. RouteBuilder gets created with old
value of 'publicAddress'

from(abcd+ ":"+ serviceName+ "://{{publicAddress}}?loggingEnabled=
{{loggingEnabled}}").routeId(xyz + serviceName + "Route");

I tried using properties:{{publicAddress}} but that gave me null value. Any
idea which placeholder I need to use to resolve this issue ?



--
View this message in context: 
http://camel.465427.n5.nabble.com/Placeholder-of-Camel-from-tag-is-not-getting-updated-with-new-values-tp5774909.html
Sent from the Camel - Users mailing list archive at Nabble.com.