Re: Lately (2.14) NullPointerExceptions instead of TypeConversionExceptions
Probably the stacktrace will not help: the npe is thrown on the line where i use the object returned from getBody(Some.class); The problem ist that no exception is thrown by getBody(Some.class) but null is returned. So there must be a path that returns null. -- View this message in context: http://camel.465427.n5.nabble.com/Lately-2-14-NullPointerExceptions-instead-of-TypeConversionExceptions-tp5759751p5760690.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: jmx- annotated RouteBuilder not showing up in JConsole
Thanks for the hint that helped much - i tried both. on first site there is no different in extending ServiceSupport (onStart, onStop mus be added) or implementing Service (start, stop methods must be added). -- View this message in context: http://camel.465427.n5.nabble.com/jmx-annotated-RouteBuilder-not-showing-up-in-JConsole-tp5760486p5760691.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Date format issue in xstream marshalling.
Hello, Can any one please help in retaining the date value instead converting to GMT? Thanks, Sayed -- View this message in context: http://camel.465427.n5.nabble.com/Date-format-issue-in-xstream-marshalling-tp5758860p5760697.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: EventNotifierSupport - Endpoint ID accessible ?
There is already stats per processor (eg each step in the route) - these stats are in the jmx. On Mon, Dec 15, 2014 at 11:46 AM, Michael Täschner m.taesch...@gmail.com wrote: Hi, yes these are not Endpoints in the routes but I saw no clear definitions for the steps and each can be given an id I am interested in. I will check both approaches to see how to easily pick up the corresponding id for mapping the collected metrics against each step. @Claus: Do you think it makes sense to have monitoring/statistics down to route definition steps or will they be redundant compared to the monitoring/statistics of the overall route ? Thanks and Regards, Michael 2014-12-15 7:54 GMT+01:00 Claus Ibsen claus.ib...@gmail.com: Endpoints do not have ids. Elemenets in routes have ids, so you can grab it from the route definitions, there is api on camel context to dive in and find that. On Sat, Dec 13, 2014 at 3:35 PM, Willem Jiang willem.ji...@gmail.com wrote: The id attribute is define in OptionalIdentifiedDefinition which can be unmarshaled from xml. But it’s not defined in endpoint, so you cannot access it from endpoint. -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On December 12, 2014 at 11:13:58 PM, Michael Täschner ( m.taesch...@gmail.com) wrote: Hi Camel-Riders, using Camel 2.13.2 we extend EventNotifierSupport to implement statistics collection for routes and endpoints. For endpoints we can extract the configured route id via exchange.getFromRouteId() but I can see no way to access the id for endpoints in our camel spring dsl, only thing accessible is endpoint.getEndpointKey() which gives back the uri content. Unfortunately this is not very stable if uri options change and not a good reference for our statistics map. Is there a way to access the id for endpoints as declared in the route ? Example route: uri=cxf:bean:isbExampleService?dataFormat=MESSAGEsynchronous=true / ServiceImpl Endpoint: EndpointKey: direct:isb.lhsystems.com/services/IsbExampleServiceImpl id = serviceImpl -- not visible/accessible ?! Thanks and Regards, Michael -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/ -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Programmatically referring to route/context names within routes,
Hi,
I have a generic dead letter queue handler. Before messages are put onto
the dead letter queue, my routes log details of the exceptions (via an
interceptor within the same context). I'd like to also stamp the messages
with the route and context from which the exception was thrown.
I could just type the correct names into every interceptor, but it would be
nicer if I could do something like this:
!-- Make the route log the exception before sending to the dead
letter queue --
interceptSendToEndpoint uri={{dead.letter.uri}}
id=deadletter-logger
log logName=jellyfish-messaging loggingLevel=ERROR
message=Dead letter interceptor invoked /
to
uri=log:org.jellyfish.notifications?level=ERRORamp;showCaughtException=trueamp;showStackTrace=trueamp;showException=true
/
*setOutHeader headerName=DLQ-context
constant{{camel-current-context-id}}/constant
/setOutHeadersetOutHeader headerName=DLQ-route
constant{{camel-intercepted-route-id}}/constant
/setOutHeader*/interceptSendToEndpoint
You'll note that I'm already pulling in the dead letter queue name from
config - i.e. {{dead.letter.uri}}. The magic sauce would be having
environment variables like:-
- {{camel-current-context-id}}
- {{camel-intercepted-route-id}}
Is this sort of thing available?
I'm running Camel 2.12.3 and ActiveMQ on 5.7.0.
Thanks,
J.
Re: Programmatically referring to route/context names within routes,
Hi
See the simple language which has many details.
And the message history eip
http://camel.apache.org/message-history
On Mon, Dec 15, 2014 at 12:29 PM, Jeremy Gooch jer...@huwun.com wrote:
Hi,
I have a generic dead letter queue handler. Before messages are put onto
the dead letter queue, my routes log details of the exceptions (via an
interceptor within the same context). I'd like to also stamp the messages
with the route and context from which the exception was thrown.
I could just type the correct names into every interceptor, but it would be
nicer if I could do something like this:
!-- Make the route log the exception before sending to the dead
letter queue --
interceptSendToEndpoint uri={{dead.letter.uri}}
id=deadletter-logger
log logName=jellyfish-messaging loggingLevel=ERROR
message=Dead letter interceptor invoked /
to
uri=log:org.jellyfish.notifications?level=ERRORamp;showCaughtException=trueamp;showStackTrace=trueamp;showException=true
/
*setOutHeader headerName=DLQ-context
constant{{camel-current-context-id}}/constant
/setOutHeadersetOutHeader headerName=DLQ-route
constant{{camel-intercepted-route-id}}/constant
/setOutHeader*/interceptSendToEndpoint
You'll note that I'm already pulling in the dead letter queue name from
config - i.e. {{dead.letter.uri}}. The magic sauce would be having
environment variables like:-
- {{camel-current-context-id}}
- {{camel-intercepted-route-id}}
Is this sort of thing available?
I'm running Camel 2.12.3 and ActiveMQ on 5.7.0.
Thanks,
J.
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: Changes in Java 8 generics breaking Camel
I am using Camel 2.14.0. I do see one problem, though maybe it's just a lack of understanding of the process you're using to compare results. Annotations like @Consume have a retention policy of runtime, meaning the compiler leaves them in the compiled class file (I believe). Your decompiled code does not show any annotations. I fully expect to see the same methods generated via Java 7 and 8, but the annotations on them should be different in the 8 generated byte code. -- View this message in context: http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics-breaking-Camel-tp5760638p5760703.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: cfx web service client error
Hi Willem
now am getting below error
Response-Code: 500
Encoding: UTF-8
Content-Type: application/soap+xml; charset=utf-8
Headers: {Cache-Control=[private], connection=[keep-alive],
Content-Length=[508], content-type=[application/soap+xml; charset=utf-8],
Date=[Mon, 15 Dec 2014 12:14:53 GMT], Server=[Microsoft-IIS/7.5], Via=[1.0
proxy (squid/3.1.8)], X-AspNet-Version=[4.0.30319], X-Cache=[MISS from
proxy], X-Cache-Lookup=[MISS from proxy:3128], X-Powered-By=[ASP.NET]}
Payload: ?xml version=1.0 encoding=utf-8?soap:Envelope xmlns:soap=
http://www.w3.org/2003/05/soap-envelope; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance; xmlns:xsd=
http://www.w3.org/2001/XMLSchema;soap:Bodysoap:Faultsoap:Codesoap:Valuesoap:Receiver/soap:Value/soap:Codesoap:Reasonsoap:Text
xml:lang=enServer was unable to process request. ---gt; Object
reference not set to an instance of an
object./soap:Text/soap:Reasonsoap:Detail
//soap:Fault/soap:Body/soap:Envelope
--
Please advise me to over come this issue
This is my enpoint configuration
String cxfAddressLine = cxf:
http://123.231.66.11/gslwsairavailabilitydisplay/Service1.asmx?wsdlURL=galieo.wsdl;
//
+ dataFormat=PAYLOAD //
+ serviceName={http://tempuri.org/}Service1; //
+ synchronous=true //
+ loggingFeatureEnabled=true //
+ portName={http://tempuri.org/}Service1Soap12;
Request file:
AirAvailabilityDisplay
!--Optional:--
PCCT6C/PCC
!--Optional:--
ClientIDG1038416/ClientID
!--Optional:--
SignOnZT6C/MWS/SignOn
!--Optional:--
StartDt20141005/StartDt
!--Optional:--
StartCityCMB/StartCity
!--Optional:--
EndCityLON/EndCity
!--Optional:--
AvailPrefA/AvailPref
!--Optional:--
ClassPrefY/ClassPref
!--Optional:--
AirLineExcludeIncludeI/AirLineExcludeInclude
!--Optional:--
AirLinesUL/AirLines
!--Optional:--
FltTypePrefA/FltTypePref
/AirAvailabilityDisplay
On Thu, Dec 11, 2014 at 3:36 PM, Dharashan Sithamparam cdharsh...@gmail.com
wrote:
thanks lot i will check and let you know
On Wed, Dec 10, 2014 at 8:42 AM, Willem.Jiang [via Camel]
ml-node+s465427n5760433...@n5.nabble.com wrote:
You just defined a wrong service name, it could be “s:Service1Soap”, or
“s:Service1Soap12”.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On December 9, 2014 at 11:15:28 PM, dharshan ([hidden email]
http:///user/SendEmail.jtp?type=nodenode=5760433i=0) wrote:
Hi
When i sent the request i have getting below error .
Caused by: org.apache.camel.FailedToCreateProducerException: Failed to
create Producer for endpoint: Endpoint[cxf://bean:galileo]. Reason:
org.apache.cxf.service.factory.ServiceConstructionException: Could not
find
definition for service {http://tempuri.org/}AirAvailabilityDisplay.
Please advis me on this
I have attached my config file ,wsdl file and request file with this
thread
.
config file : camel-context.xml
wsdl: galieo.wsdl
Request: request.xml
--
View this message in context:
http://camel.465427.n5.nabble.com/cfx-web-service-client-error-tp5760403.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
If you reply to this email, your message will be added to the
discussion below:
http://camel.465427.n5.nabble.com/cfx-web-service-client-error-tp5760403p5760433.html
To unsubscribe from cfx web service client error, click here
http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_codenode=5760403code=Y2RoYXJzaGFuc0BnbWFpbC5jb218NTc2MDQwM3wtODU2NDQ3NTAy
.
NAML
http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
--
Regards
S.Dharshan
--
Regards
S.Dharshan
--
View this message in context:
http://camel.465427.n5.nabble.com/cfx-web-service-client-error-tp5760403p5760702.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Changes in Java 8 generics breaking Camel
Current Camel 2.14.0 is built with JDK7 and we run the CI with JDK8 and didn’t find the issue that you said. Can you create a JIRA and submit a test case for it? -- Willem Jiang Red Hat, Inc. Web: http://www.redhat.com Blog: http://willemjiang.blogspot.com (English) http://jnn.iteye.com (Chinese) Twitter: willemjiang Weibo: 姜宁willem On December 15, 2014 at 9:39:22 PM, andrewcelerity (and...@celerityglobal.com) wrote: I am using Camel 2.14.0. I do see one problem, though maybe it's just a lack of understanding of the process you're using to compare results. Annotations like @Consume have a retention policy of runtime, meaning the compiler leaves them in the compiled class file (I believe). Your decompiled code does not show any annotations. I fully expect to see the same methods generated via Java 7 and 8, but the annotations on them should be different in the 8 generated byte code. -- View this message in context: http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics-breaking-Camel-tp5760638p5760703.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: cfx web service client error
It looks like you didn’t setup your camel route rightly?
Can you show me your camel route?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On December 15, 2014 at 10:31:09 PM, dharshan (cdharsh...@gmail.com) wrote:
Hi Willem
now am getting below error
Response-Code: 500
Encoding: UTF-8
Content-Type: application/soap+xml; charset=utf-8
Headers: {Cache-Control=[private], connection=[keep-alive],
Content-Length=[508], content-type=[application/soap+xml; charset=utf-8],
Date=[Mon, 15 Dec 2014 12:14:53 GMT], Server=[Microsoft-IIS/7.5], Via=[1.0
proxy (squid/3.1.8)], X-AspNet-Version=[4.0.30319], X-Cache=[MISS from
proxy], X-Cache-Lookup=[MISS from proxy:3128], X-Powered-By=[ASP.NET]}
Payload: soap:Receiver xml:lang=enServer was unable to process request.
--- Object
reference not set to an instance of an
object. /
--
Please advise me to over come this issue
This is my enpoint configuration
String cxfAddressLine = cxf:
http://123.231.66.11/gslwsairavailabilitydisplay/Service1.asmx?wsdlURL=galieo.wsdl;
//
+ dataFormat=PAYLOAD //
+ serviceName={http://tempuri.org/}Service1; //
+ synchronous=true //
+ loggingFeatureEnabled=true //
+ portName={http://tempuri.org/}Service1Soap12;
Request file:
T6C
G1038416
ZT6C/MWS
20141005
CMB
LON
A
Y
I
UL
A
On Thu, Dec 11, 2014 at 3:36 PM, Dharashan Sithamparam wrote:
thanks lot i will check and let you know
On Wed, Dec 10, 2014 at 8:42 AM, Willem.Jiang [via Camel]
ml-node+s465427n5760433...@n5.nabble.com wrote:
You just defined a wrong service name, it could be “s:Service1Soap”, or
“s:Service1Soap12”.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On December 9, 2014 at 11:15:28 PM, dharshan ([hidden email]
) wrote:
Hi
When i sent the request i have getting below error .
Caused by: org.apache.camel.FailedToCreateProducerException: Failed to
create Producer for endpoint: Endpoint[cxf://bean:galileo]. Reason:
org.apache.cxf.service.factory.ServiceConstructionException: Could not
find
definition for service {http://tempuri.org/}AirAvailabilityDisplay.
Please advis me on this
I have attached my config file ,wsdl file and request file with this
thread
.
config file : camel-context.xml
wsdl: galieo.wsdl
Request: request.xml
--
View this message in context:
http://camel.465427.n5.nabble.com/cfx-web-service-client-error-tp5760403.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
If you reply to this email, your message will be added to the
discussion below:
http://camel.465427.n5.nabble.com/cfx-web-service-client-error-tp5760403p5760433.html
To unsubscribe from cfx web service client error, click here
.
NAML
--
Regards
S.Dharshan
--
Regards
S.Dharshan
--
View this message in context:
http://camel.465427.n5.nabble.com/cfx-web-service-client-error-tp5760403p5760702.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Changes in Java 8 generics breaking Camel
Am 15.12.14 14:38 schrieb andrewcelerity unter and...@celerityglobal.com: I am using Camel 2.14.0. I do see one problem, though maybe it's just a lack of understanding of the process you're using to compare results. Annotations like @Consume have a retention policy of runtime, meaning the compiler leaves them in the compiled class file (I believe). Your decompiled code does not show any annotations. Well spotted. I used jad to decompile Foo.class: http://varaneckas.com/jad Which apparently did not take the @Consume annotation into the account, don't know why. That said using JAD produced the expected @Consume annotated method: http://jd.benow.ca But as Willem has already said it could help us if you would provide a concrete code showing the problem in Java 8, like some compilation errors or a failing test in Java 8 which works properly in Java 7 and what not. Then we could nail down the problem in case there¹s any. Babak I fully expect to see the same methods generated via Java 7 and 8, but the annotations on them should be different in the 8 generated byte code. -- View this message in context: http://camel.465427.n5.nabble.com/Changes-in-Java-8-generics-breaking-Came l-tp5760638p5760703.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Throttling based on content in camel
Hi, Looking at the documentation says that ThrottlingInflightRoutePolicy does throttling that is approximate based, meaning that its more coarse grained and not explicit precise as the Throttler (did a poc and coul. Also it looks like the RoutePolicy applies to the entire Route when compared to the Throttler which could act only on a endpoint. Looking at the Throttler features of being precise and capable of acting like a funnel i am considering of extending this throttler for having the support for checking based on content. Any complications that the team thinks which perhaps i am not considering please do let me know.. Regards, -Yogesh -- View this message in context: http://camel.465427.n5.nabble.com/Throttling-based-on-content-in-camel-tp5760505p5760709.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: FW: Spring Camel Parent Context
Looks like a JIRA had already been created. Claus wasn't a big fan of the change. https://issues.apache.org/jira/browse/CAMEL-5858 I might try to create a patch and see if there will still be resistance. I can't imagine I'm the only one with a use case of centralized CamelContext configuration, but wanting to customize on a per actual context implementation. Specifically setting unique ID's can help with logging and JMX management. -- View this message in context: http://camel.465427.n5.nabble.com/Spring-Camel-Parent-Context-tp5760366p5760715.html Sent from the Camel - Users mailing list archive at Nabble.com.
How to avoid cxfrs:rserver adding extra header params (accept-encoding) -
Hi
we are using camel cxfrs server to expose our proxy services, The service
is exposer is working fine but if the response is more that certain limit
looks like the client is not able to receive getting timed out exception.
Then we have identified that the camel service adding some extra header
parameter such as accept-encoding.
So my question would be how do we avoid these extra header params and send
only the actual param.
Headers: {Accept=[application/xml], *accept-encoding=[gzip, deflate],*
accept-language=[en-us], Authorization=[xx], connection=[keep-alive],
Content-Length=[0], Content-Type=[null], host=[localhost:8001],
user-agent=[xxx/14.0.0 (x86_64)]}
but we dont send the accept-encoding= header param but getting added in
the cxfrs server
how could i remove this extra params and send only the actual param.
Thanks
Kumaran
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-avoid-cxfrs-rserver-adding-extra-header-params-accept-encoding-tp5760716.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Problem with InOnly exchange pattern using with RestDSL
Hello! I'm using spark-java as rest-dsl provider (but I already tried with
the servlet component and still didn't work) and I'm having some issues
using in only in a rest dsl route:
That's the rest configuration:
restConfiguration().component(spark-rest).bindingMode(RestBindingMode.json)
.dataFormatProperty(prettyPrint, true);
my endpoint:
rest(/rs/tm).consumes(APPLICATION_RESOURCE_JSON).produces(APPLICATION_RESOURCE_JSON)
.post().outType(Transaction.class).type(Transaction.class)
.to(direct:processTransaction);
and, my direct:processTransaction:
from(direct:processTransaction)
.process(e - {
//doing really funny stuff over here
})
.inOnly(seda:processTransaction);
so... whenever i try to send a message to an endpoint using InOnly exchange
pattern, the rest-dsl endpoint gets messed up, for example, it is not
converted automatically to json before returning to the client, and also
content type is not set, but, when I try to use the InOut pattern,
everything works fine, but I really need this endpoint to be async at that
point.
oh, and yeah, when I don't set the InOnly pattern before calling the seda
endpoint, the message is sent sync, i have no idea why.
does anyone know what could be happening?
waiting for an answer, thanks!!
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-InOnly-exchange-pattern-using-with-RestDSL-tp5760717.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Re: cfx web service client error
Hi
I have pasted below my java class
public class CamelCfxTest extends RouteBuilder {
String endPoint = cxf:
http://123.231.66.11/gslwsairavailabilitydisplay/Service1.asmx?wsdlURL=galieo.wsdl;
//
+ dataFormat=PAYLOAD //
+ serviceName={http://tempuri.org/}Service1; //
+ synchronous=true //
+ loggingFeatureEnabled=true //
+ portName={http://tempuri.org/}Service1Soap;;
public static void main(String[] args) throws Exception {
CamelContext camelContext = new DefaultCamelContext();
camelContext.addRoutes(new CamelCfxTest());
camelContext.start();
Thread.sleep(1000);
}
@Override
public void configure() throws Exception {
from(file://Input).to(endPoint).process(new Processor() {
public void process(Exchange exchng) throws Exception {
System.out.println(exchng + exchng.getIn(String.class));
}
});
}
}
On Mon, Dec 15, 2014 at 8:19 PM, Willem.Jiang [via Camel]
ml-node+s465427n5760706...@n5.nabble.com wrote:
It looks like you didn’t setup your camel route rightly?
Can you show me your camel route?
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On December 15, 2014 at 10:31:09 PM, dharshan ([hidden email]
http:///user/SendEmail.jtp?type=nodenode=5760706i=0) wrote:
Hi Willem
now am getting below error
Response-Code: 500
Encoding: UTF-8
Content-Type: application/soap+xml; charset=utf-8
Headers: {Cache-Control=[private], connection=[keep-alive],
Content-Length=[508], content-type=[application/soap+xml;
charset=utf-8],
Date=[Mon, 15 Dec 2014 12:14:53 GMT], Server=[Microsoft-IIS/7.5],
Via=[1.0
proxy (squid/3.1.8)], X-AspNet-Version=[4.0.30319], X-Cache=[MISS from
proxy], X-Cache-Lookup=[MISS from proxy:3128], X-Powered-By=[ASP.NET]}
Payload: soap:Receiver xml:lang=enServer was unable to process
request. --- Object
reference not set to an instance of an
object. /
--
Please advise me to over come this issue
This is my enpoint configuration
String cxfAddressLine = cxf:
http://123.231.66.11/gslwsairavailabilitydisplay/Service1.asmx?wsdlURL=galieo.wsdl;
//
+ dataFormat=PAYLOAD //
+ serviceName={http://tempuri.org/}Service1; //
+ synchronous=true //
+ loggingFeatureEnabled=true //
+ portName={http://tempuri.org/}Service1Soap12;
Request file:
T6C
G1038416
ZT6C/MWS
20141005
CMB
LON
A
Y
I
UL
A
On Thu, Dec 11, 2014 at 3:36 PM, Dharashan Sithamparam wrote:
thanks lot i will check and let you know
On Wed, Dec 10, 2014 at 8:42 AM, Willem.Jiang [via Camel]
[hidden email] http:///user/SendEmail.jtp?type=nodenode=5760706i=1
wrote:
You just defined a wrong service name, it could be “s:Service1Soap”,
or
“s:Service1Soap12”.
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.iteye.com (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On December 9, 2014 at 11:15:28 PM, dharshan ([hidden email]
) wrote:
Hi
When i sent the request i have getting below error .
Caused by: org.apache.camel.FailedToCreateProducerException: Failed
to
create Producer for endpoint: Endpoint[cxf://bean:galileo]. Reason:
org.apache.cxf.service.factory.ServiceConstructionException: Could
not
find
definition for service {http://tempuri.org/}AirAvailabilityDisplay.
Please advis me on this
I have attached my config file ,wsdl file and request file with
this
thread
.
config file : camel-context.xml
wsdl: galieo.wsdl
Request: request.xml
--
View this message in context:
http://camel.465427.n5.nabble.com/cfx-web-service-client-error-tp5760403.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
If you reply to this email, your message will be added to the
discussion below:
http://camel.465427.n5.nabble.com/cfx-web-service-client-error-tp5760403p5760433.html
To unsubscribe from cfx web service client error, click here
.
NAML
--
Regards
S.Dharshan
--
Regards
S.Dharshan
--
View this message in context:
http://camel.465427.n5.nabble.com/cfx-web-service-client-error-tp5760403p5760702.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
If you reply to this email, your message will be added to the discussion
below:
http://camel.465427.n5.nabble.com/cfx-web-service-client-error-tp5760403p5760706.html
To unsubscribe from cfx web service
Re: REST DSL Exception Handling
This is when the Json request comes in to the webservice. I am deliberately sending in a malformed Json object, just so that I can handle it - our service will be called by various applications, and I want to be able to send a response back to the caller with the message that the Json is malformed. I tried setting the bridgeErrorHandler property, but it does not help. See below for the configuration in Spring: restConfiguration bindingMode=auto component=restlet port=8085 consumerProperty key=bridgeErrorHandler value=true/ /restConfiguration -- View this message in context: http://camel.465427.n5.nabble.com/REST-DSL-Exception-Handling-tp5760600p5760714.html Sent from the Camel - Users mailing list archive at Nabble.com.
Re: Problem with InOnly exchange pattern using with RestDSL
Hi
Maybe you should use the wire tap eip
On Tue, Dec 16, 2014 at 1:17 AM, gabfssilva gabfssi...@gmail.com wrote:
Hello! I'm using spark-java as rest-dsl provider (but I already tried with
the servlet component and still didn't work) and I'm having some issues
using in only in a rest dsl route:
That's the rest configuration:
restConfiguration().component(spark-rest).bindingMode(RestBindingMode.json)
.dataFormatProperty(prettyPrint, true);
my endpoint:
rest(/rs/tm).consumes(APPLICATION_RESOURCE_JSON).produces(APPLICATION_RESOURCE_JSON)
.post().outType(Transaction.class).type(Transaction.class)
.to(direct:processTransaction);
and, my direct:processTransaction:
from(direct:processTransaction)
.process(e - {
//doing really funny stuff over here
})
.inOnly(seda:processTransaction);
so... whenever i try to send a message to an endpoint using InOnly exchange
pattern, the rest-dsl endpoint gets messed up, for example, it is not
converted automatically to json before returning to the client, and also
content type is not set, but, when I try to use the InOut pattern,
everything works fine, but I really need this endpoint to be async at that
point.
oh, and yeah, when I don't set the InOnly pattern before calling the seda
endpoint, the message is sent sync, i have no idea why.
does anyone know what could be happening?
waiting for an answer, thanks!!
--
View this message in context:
http://camel.465427.n5.nabble.com/Problem-with-InOnly-exchange-pattern-using-with-RestDSL-tp5760717.html
Sent from the Camel - Users mailing list archive at Nabble.com.
--
Claus Ibsen
-
Red Hat, Inc.
Email: cib...@redhat.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen
hawtio: http://hawt.io/
fabric8: http://fabric8.io/
Re: REST DSL Exception Handling
Hi Thanks for trying. I logged a ticket to support this in next release https://issues.apache.org/jira/browse/CAMEL-8155 On Mon, Dec 15, 2014 at 8:01 PM, restful camel bin...@gmail.com wrote: This is when the Json request comes in to the webservice. I am deliberately sending in a malformed Json object, just so that I can handle it - our service will be called by various applications, and I want to be able to send a response back to the caller with the message that the Json is malformed. I tried setting the bridgeErrorHandler property, but it does not help. See below for the configuration in Spring: restConfiguration bindingMode=auto component=restlet port=8085 consumerProperty key=bridgeErrorHandler value=true/ /restConfiguration -- View this message in context: http://camel.465427.n5.nabble.com/REST-DSL-Exception-Handling-tp5760600p5760714.html Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen - Red Hat, Inc. Email: cib...@redhat.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen hawtio: http://hawt.io/ fabric8: http://fabric8.io/
Re: How to avoid cxfrs:rserver adding extra header params (accept-encoding) -
Adding more informations.
I am using Camel 2.14.0 version and we are exposing services using cxfrs
component, When the response size is but the response by default the header
parameter is set as Transfer-Encoding = chunk, but we are expecting
Transfer-Encoding = Identity; in the response header. How to customize
this.
Any help would be very much appreciated.
Thanks
Kumar
Kumaran wrote
Hi
we are using camel cxfrs server to expose our proxy services, The service
is exposer is working fine but if the response is more that certain limit
looks like the client is not able to receive getting timed out exception.
Then we have identified that the camel service adding some extra header
parameter such as accept-encoding.
So my question would be how do we avoid these extra header params and send
only the actual param.
Headers: {Accept=[application/xml],
*
accept-encoding=[gzip, deflate],
*
accept-language=[en-us], Authorization=[xx], connection=[keep-alive],
Content-Length=[0], Content-Type=[null], host=[localhost:8001],
user-agent=[xxx/14.0.0 (x86_64)]}
but we dont send the accept-encoding= header param but getting added in
the cxfrs server
how could i remove this extra params and send only the actual param.
Thanks
Kumaran
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-avoid-cxfrs-rserver-adding-extra-header-params-accept-encoding-tp5760716p5760722.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Intermittent error: No content to map due to end-of-input
hi guys,
I am quite new to Camel. We are using Camel 2.14.
I got this intermittent error which is quite annoying. It happens very
rarely and randomly. If I send the same request again, it will process just
fine.
2014-12-15 17:24:56.700 ERROR 1852673485@qtp-1010937526-2
common.exception.MTSErrorHandler Received Exception
com.fasterxml.jackson.databind.JsonMappingException: No content to map due
to end-of-input
at Source: org.apache.camel.converter.stream.InputStreamCache@64288413;
line: 1, column: 1
After searching this exception, I have seen many places where people suggest
to use stream caching. However in our case, stream caching is already used.
I am not sure however if it is set up properly.
Thanks in advance for any your inputs.
Cheers
Shan
*This is our camel context config*
camel:camelContext id=camelContext errorHandlerRef=errorHandler
trace=${camel.trace:false} streamCache=true
When project starts up, this line indicates it is enabled:
2014-12-16 16:13:04.300 INFO [main] [camel.spring.SpringCamelContext]
StreamCaching is enabled on CamelContext: camelContext
*This is our code.*
RouteDefinition rdRouteDefinition = from(
createListeningService()
).routeId( getRouteId() );
rdRouteDefinition.wireTap(
ABCMaintenanceRouteDefinition.AUDIT_LOGGING.getCamelRoute() );
rdRouteDefinition
.process(new Processor() {
@Override
public void process(Exchange exchange) throws Exception
{
_log.info(Before unmarshall() );
_log.info(exchange body = +
exchange.getIn().getBody());
_log.info(exchange body size = +
exchange.getIn().getBody(InputStreamCache.class).length());
}
})
.unmarshal().json(JsonLibrary.Jackson, ExecutionRequest.class)
.to(ABCRouteType.VALIDATOR.getRoutePrefix() + requestXsd)
.convertBodyTo(FIXExecutionReport.class)
.process(fixMessageProcessor)
.wireTap( ABCRouteType.LOG.getRoutePrefix() + _log.getName() +
ABCGenericConstants.LOGGING_ROUTE_OPTIONS )
.inOnly( routeType.getRoutePrefix() + publishingDestination );
rdRouteDefinition.wireTap(
ABCMaintenanceRouteDefinition.AUDIT_LOGGING.getCamelRoute() );
*This is the logging *
2014-12-15 17:24:56.682 INFO 1852673485@qtp-1010937526-2 Before
unmarshall()
2014-12-15 17:24:56.682 INFO 1852673485@qtp-1010937526-2 exchange body =
org.apache.camel.converter.stream.InputStreamCache@64288413
2014-12-15 17:24:56.683 INFO 1852673485@qtp-1010937526-2 exchange body size
= 646
2014-12-15 17:24:56.700 ERROR 1852673485@qtp-1010937526-2
common.exception.ABCErrorHandler Received Exception
com.fasterxml.jackson.databind.JsonMappingException: No content to map due
to end-of-input
at Source: org.apache.camel.converter.stream.InputStreamCache@64288413;
line: 1, column: 1
--
View this message in context:
http://camel.465427.n5.nabble.com/Intermittent-error-No-content-to-map-due-to-end-of-input-tp5760725.html
Sent from the Camel - Users mailing list archive at Nabble.com.
