The message is in the proper queue, I just can't see the XML when viewing
through the ActiveMQ console.
I'm hoping to convince the project manager to view the message by a
different means making this issue moot. Thanks for the reply.
willem.jiang wrote:
>
> jfaath wrote:
&g
It's a requirement for the project so the message can be referred to in the
queue. It seems a little cumbersome to view the message in the queue so I'm
going to see if I can get the requirements changed. Thanks for the reply
willem.jiang wrote:
>
> jfaath wrote:
>> I&#
I'm wondering if there is a way to retrieve the messageId of the message when
a producer sends a message to the queue. For example, let's say I have
these routes:
from("wherever").
// do lots of stuff
to("jms:queue:processed");
from("jms:queue:processed")
.choice()
.when(header("errorsFound").i
ge to the queue. At least, that's what I see in
the ActiveMQ console. Any ideas?
jfaath wrote:
>
> Sure, here is the route:
>
> from("servlet:///data-in").convertBodyTo(String.class)
> .to("validator:schema-file.xsd")
> .inOnly(&
und").isEqualTo(true))
.to("jms:queue:errors")
.otherwise().to("mock:finished");
willem.jiang wrote:
>
> Hi,
>
> Can we have a look at your camel route?
> Which version of camel are your using?
>
> You issue relates to the Error
I have a camel application that's using a remote ActiveMQ broker instance.
Messages come in to the application via HTTP and are sent to a "inbound"
queue using "inOnly". Messages are then processed and sent to a "processed"
queue. Finally, if an error occurred during processing, those messages
willem.jiang wrote:
>
>
> Oh, you want to the camel servlet component be managed by camel web
> console.
> After go through the SpringServlet code I think you set the CamelRoute
> configure location into the SpringServlet's init-param just like
> CamelHttpTransportServlet does, then you can
ContextLoaderListener registered?
Is there any way to pass the WebApplicationContext created by the camel
servlet component to jersey's SpringServlet?
jfaath wrote:
>
> That seems to finally work...providing I remove the "Jersey Filter" that
> is used by the web console. Thi
onent/servlet/web-spring.xml
>
> Willem
>
> jfaath wrote:
>> I played around with this by removing everything below the
>> ContextLoaderListener listener. I still get the same error. As a rule,
>> it
>> seems that Tomcat always loads listeners before servlet
contextConfigLocation parameter supposed to
do?
Is there a sample of using this component in an actual servlet container?
willem.jiang wrote:
>
> Hi,
>
> Can you remove the web console part and try again?
> Maybe there are some side effect of the web console configure.
>
&g
So should I post a JIRA on this? The servlet component doesn't seem to work
in v2.2 when used in the web console.
--
View this message in context:
http://old.nabble.com/Deploying-as-web-app-with-jetty-endpoint-tp28171746p28219175.html
Sent from the Camel - Users mailing list archive at Nabble.c
willem.jiang wrote:
>
> You need make sure the CamelHttpTransportServle is deployed first, than
> load the camel context.
> You can take a look at this example first[1].
>
> [1]
> https://svn.apache.org/repos/asf/camel/trunk/components/camel-servlet/src/test/resources/org/a
?
willem.jiang wrote:
>
> Hi,
>
> If you don't want start the jetty engine, you can try to use the
> camel-servlet[1] component.
>
> [1]http://camel.apache.org/servlet.html
>
>
> Willem
>
> jfaath wrote:
>> I've deployed my camel app a
I've deployed my camel app as a web application in tomcat. Works great. The
main starting point for my route is an http server endpoint using
camel-jetty. So, it seems weird to me that tomcat starts and then starts a
jetty instance. Is there any way to use the actual tomcat instance for this
e
the example on the splitter page for an
> example.
>
> In the case there is no error, then your splitter should just return 1
> message and you should be fine.
>
> Hope that helps.
> Allen
>
> On Thu, Mar 25, 2010 at 8:39 AM, jfaath wrote:
>
>>
>> The
ikely create a POJO to split the message up and then use the
> content base router to
> route the message.
>
> On Wed, Mar 24, 2010 at 9:04 AM, jfaath wrote:
>
>>
>> I'll give this a shot. Can you give me a quick example or point me to a
>> sample that does
o basically you can stuff whatever you want into it.
>
>
> On Tue, Mar 23, 2010 at 4:02 PM, jfaath wrote:
>
>>
>> I'm not sure that would work. As I stated in my original post, I don't
>> want
>> to send the entire message to the error queue, just
r?
>
> Then in your route, just send any message to the error queue when the
> header
> is detected.
>
> On Tue, Mar 23, 2010 at 11:57 AM, jfaath wrote:
>
>>
>> I'm looking for some advice on how to deal with errors during a large
>> processing task. I
I'm looking for some advice on how to deal with errors during a large
processing task. It seems like it should be simple but I'm having trouble
figuring out what to do.
I have an HTTP endpoint that receives XML messages then sticks them in a
processing queue. From the queue, they get unmarshall
he wiki page with how to (see
> bottom)
> http://cwiki.apache.org/confluence/display/CAMEL/Jetty
>
> And this commits:
> http://svn.apache.org/viewvc?rev=918337&view=rev
>
>
> On Tue, Mar 2, 2010 at 10:15 PM, jfaath wrote:
>>
>> I just tried that and in f
I just tried that and in fact I don't see the behavior changing under any
variations of the code. What exactly is that supposed to do?
Claus Ibsen-2 wrote:
>
> Hi
>
> Have you tried with the option throwExceptionOnFailure=false
>
>
>
> On Tue, Mar 2, 2
ned when I have 'handled(false)' in the
route. So, it is clear that a 500 error isn't being hidden by any external
forces.
Claus Ibsen-2 wrote:
>
> On Fri, Feb 26, 2010 at 6:31 PM, jfaath wrote:
>>
>> By consulting the documentation, I came up with this code
By consulting the documentation, I came up with this code to handle an error
for messages sent to a jetty http endpoint:
onException(SchemaValidationException.class)
.handled(true)
.transform()
.simple("The format of the incoming message does not conform to the
specification.");
Everything works
23 matches
Mail list logo
