You could also create a SOAPDataFormat which extends JAXBDataFormat
which I think would be a good choice.
Then the JAXBDataFormat is still pure and clean in terms of JAXB.
And the SOAPDataFormat can over time have additional SOAP related stuff in it.
The code can still be in camel-jaxb if you do
Hi Christian,
I think it dependents what you want to do for further enhancement of the
your current solution. If you just want to add or strip the SOAP , an
option of the JAXB DataFormat could be enough.
If you want to do more enhancement, you'd better create a SOAP
DataFormat for it.
Willem
Hi Willem and Claus,
I have looked into the JaxbDataformat to see what I should implement. As
what I need to do for the new DataFormat is quite similiar to the
JaxbDataFormat I think two aproaches may help to avoid duplicate code.
1) I could create a processor that only removes or adds the SO
On Wed, Jan 20, 2010 at 10:40 AM, Wayne Keenan wrote:
> Hi,
>
> Apologies, I didn't word my previous email very well; what I should have
> also mentioned for clarity is that if I do this:
>
>
> http://0.0.0.0:8080/endpoint"/>
>
>
> ${id}
>
Hi
Please always write which version of Camel you are using.
And others listening in, do that as well. Its important for us to know!
On Wed, Jan 20, 2010 at 10:02 AM, Wayne Keenan wrote:
> Hi,
>
> I have a Jetty endpoint that when recieving a message will perform the
> processing asynchronously
Willem Jiang wrote:
Wayne Keenan wrote:
Hi,
Thanks for replying.
On Wed, Jan 20, 2010 at 3:28 PM, Willem Jiang
wrote:
Hi,
Can you try to set the ID into the message header instead of the message
body ? In this way you can the Request object back :)
http://0.0.0.0:80
Hi,
Is your post request using "application/x-www-form-urlencoded" as the
content-type ?
If so , you should get the parameters from the message header.
Willem
Wayne Keenan wrote:
Hi,
I believe I have found the trouble I am having. I think this bug still
exists in the 2.1.0 release:
http://
Wayne Keenan wrote:
Hi,
Thanks for replying.
On Wed, Jan 20, 2010 at 3:28 PM, Willem Jiang wrote:
Hi,
Can you try to set the ID into the message header instead of the message
body ? In this way you can the Request object back :)
http://0.0.0.0:8080/endpoint"/>
Hi,
You can find more explanation in the wiki [1] of AggregationStrategy
changed in Camel 2.0
http://camel.apache.org/aggregator.html
Willem
Claus Ibsen wrote:
Hi
The oldExchange is null on the first invocation of the aggregation strategy.
On Wed, Jan 20, 2010 at 8:35 PM, lekkie wrote:
Thanks for your quick reply.
This is a lil bit confusing for me. Just to clarify if this is what you
meant.
>From my snippet above, my first invocation on aggrgation strategy will be
the wiretap () which I expect
myaggregation should capture the accompanying (exhange). What you are saying
is tha
Hi Claus,
well, it´s somewhat unclear to me how to configure a kind of a
listening-service based on camel in geronimo. I´m a bit JBoss-minded. ;-)
I thing, I have to create a car? Can I use a jmx-mbean? That's why I was
glad to find the posibillity using the ActiveMQ Spring config. OK, I´ll look
Hi,
I believe I have found the trouble I am having. I think this bug still
exists in the 2.1.0 release:
http://issues.apache.org/activemq/browse/CAMEL-1806
The docs says from: http://camel.apache.org/jetty.html says:
*Camel also populates all request.parameter and request.headers. For
example,
On Wed, Jan 20, 2010 at 4:09 PM, Schneider Christian
wrote:
> Hi Willem and Claus,
>
> if you are interested I can prepare a SoapJaxbDataFormat. I propose to add
> it to the camel-jaxb component.
>
+1
> I think the goal must be to stay with really easy stuff. For everything more
> complex CXF is
Try without AMQ at first.
And can you post the top of the XML file, the stuff with all those
namespace and whatnot.
On Wed, Jan 20, 2010 at 5:28 PM, ulise wrote:
>
> Hi
> I tried to run camel in a freshly downloaded geronimo-tomcat6-javaee5-2.2.
> I simply uncommented the
>
> http://came
Hi
The oldExchange is null on the first invocation of the aggregation strategy.
On Wed, Jan 20, 2010 at 8:35 PM, lekkie wrote:
>
> I have a custom aggregator set up. The custom aggregator combines the
> exchanges of an old and new one and returns them as one.
>
> However, when I log the old exc
Created jira https://issues.apache.org/activemq/browse/CAMEL-2384
If time allows it I will try and set up a test case to document the problem.
Although I'm using Oracle AQ as jms provider I dont think this is the cause
of the problem since all header values seems to be present.
Any chance this w
I have a custom aggregator set up. The custom aggregator combines the
exchanges of an old and new one and returns them as one.
However, when I log the old exchange to the ESB log file, it returns null.
See my snippet below
.
htt
Hi,
yes, I did. All camel-*-2.1.0.jars from the binary camel distribution are in
the lib-folder.
Cheers,
Uli
cmoulliard wrote:
>
> Hi,
>
> Can you check that camel jars files are present in lib folder of geronimo
> please ?
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
Hi,
Can you check that camel jars files are present in lib folder of geronimo
please ?
Regards,
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
twitter : http://twitter.com/cmoulliard
Linkedlin : http://www
Hi
I tried to run camel in a freshly downloaded geronimo-tomcat6-javaee5-2.2.
I simply uncommented the
http://camel.apache.org/schema/spring";>
part in the activemx.xml and changed all the URLs as told in
http://camel.apache.org/excepti
Hi,
Thanks for replying.
On Wed, Jan 20, 2010 at 3:28 PM, Willem Jiang wrote:
> Hi,
>
> Can you try to set the ID into the message header instead of the message
> body ? In this way you can the Request object back :)
>
>
> >>
> >> http://0.0.0.0:8080/endpoint"/>
> >>
Hi,
Can you try to set the ID into the message header instead of the message
body ? In this way you can the Request object back :)
>>
>> http://0.0.0.0:8080/endpoint"/>
>>
>>
>> ${id}
>>
>>
>>
>>
>>
Hi Willem and Claus,
if you are interested I can prepare a SoapJaxbDataFormat. I propose to add
it to the camel-jaxb component.
I think the goal must be to stay with really easy stuff. For everything more
complex CXF is the much better solution. On the other hand I also try to
understand what the
Maybe we can add a SOAP data formate to deal with the soap envelop out
of box.
BTW, It could be easy to just take off or put on the soap envelop.
But if there any WS* work involved, you had to switch to more flexible
way ( to use camel-cxf component).
Willem
Claus Ibsen wrote:
On Wed, Jan 20
I want to add another problem to the same bug:
Camel is incapable of generating this XML date format (XML (W3C) ISO 8601):
Exemple :
2010-12-25T18 :25:01.037-08:00
However using this class exists in jar lib "commons-lang-2.4.jar" from
camel, we can succeed in having this date:
org.apache.com
On Wed, Jan 20, 2010 at 3:34 PM, preben wrote:
>
> Thanks for the help.
>
> For now I'll stick to using Exchange directly - this works.
> Using camel annotations in combination with Spring seems not to work. I'll
> try to create a JIRA tomorrow, but I haven't the time to construct a test
> case. S
Thanks for the help.
For now I'll stick to using Exchange directly - this works.
Using camel annotations in combination with Spring seems not to work. I'll
try to create a JIRA tomorrow, but I haven't the time to construct a test
case. Sorry.
Preben
Claus Ibsen-2 wrote:
>
> On Wed, Jan 20, 20
On Wed, Jan 20, 2010 at 2:04 PM, preben wrote:
>
> The auditmessageDAO is not defined in xml but using @Repository annotation
> and is picked up by Spring douring initializing of the applicationContext.
> Is there a issue regarding this ? should it be defined in XML instead (Camel
> + Spring depen
The auditmessageDAO is not defined in xml but using @Repository annotation
and is picked up by Spring douring initializing of the applicationContext.
Is there a issue regarding this ? should it be defined in XML instead (Camel
+ Spring dependencies)
The funny thing is thoug that the body gets bou
On Wed, Jan 20, 2010 at 1:46 PM, preben wrote:
>
> Actually I was looking for JMSMessageID like this
> @Header(value="JMSMessageID") String jmsMessageId, but when that didn't work
> i changed it to @Headers Map to see if I get any values.
> The parameter get's bound as null !!
And how is auditMes
Actually I was looking for JMSMessageID like this
@Header(value="JMSMessageID") String jmsMessageId, but when that didn't work
i changed it to @Headers Map to see if I get any values.
The parameter get's bound as null !!
Claus Ibsen-2 wrote:
>
> Hi
>
> So which headers are you looking for to
Hi
So which headers are you looking for to be in the audit bean?
You do not have any custom JMS properties, only the regular JMS headers.
And you are saying that Map instance is empty? or is it null?
On Wed, Jan 20, 2010 at 12:26 PM, preben wrote:
>
> Im using camel v. 2.1.0 Sure the 2nd rout
Im using camel v. 2.1.0 Sure the 2nd route says:
[Camel thread 0: seda://audit] 20 jan. 2010 - 12:22:09,858 INFO
org.apache.camel.processor.interceptor.Tracer
[42a5443b-0a62-4477-885f-c6f6c40274b1 >>> (AuditRoute) from(seda://audit)
--> ref:auditMessageDAO method: audit <<< Pattern:InOnly,
Headers
What does the tracer say in the 2nd route?
camel:route id="AuditRoute">
eg from seda:audit -> auditMessageDAO
this is the interesting part
BTW which version of Camel are you using?
On Wed, Jan 20, 2010 at 11:49 AM, preben wrote:
>
> Hi Claus
>
Hi Claus
Seems that the headers are present even on the wiretap endpoint.
:
[DefaultMessageListenerContainer-1] 20 jan. 2010 - 11:44:01,614 INFO
org.apache.camel.processor.interceptor.Tracer
[ID:7D97437F084F8E83E040650A0A1027E5 >>> (RapNotificationRoute)
from(oracleQueue://queue:FURTHERELEMENTS_
On Wed, Jan 20, 2010 at 3:03 AM, Willem Jiang wrote:
> Hi Christian,
>
> Your processor implements a easy way to unmarshal the soap message.
> But I think you can leverage JAXB DataFormat to do the same thing, all you
> need to do is using a camel-xslt component for soap envelop transformation.
>
Hi,
Apologies, I didn't word my previous email very well; what I should have
also mentioned for clarity is that if I do this:
http://0.0.0.0:8080/endpoint"/>
${id}
The same bean is able to obtain the HTTPServlet
Hi
On Tue, Jan 19, 2010 at 10:53 PM, Christian Schneider
wrote:
> Hi all,
>
> I am thinking about how to make one way services easier. Currently I
> generate code for the service using cxf codegen and use the camel-cxf module
> to create a client or endpoint that can be routed over jms using the
Hi,
I have a Jetty endpoint that when recieving a message will perform the
processing asynchronously and syncronously return a correlationId so the
client can come back later to another endpoint to see how processsing is
going.
I found an example on the mailing list of how to pass the HttpSession
On Wed, Jan 20, 2010 at 9:52 AM, preben wrote:
>
> Hi
>
> I'm trying to create a auditservice using a wiretap.
>
> eg.
>
> uri="oracleQueue:queue:FURTHERELEMENTS_TEST?jmsMessageType=Text"/>
>
>
>
Hi
I'm trying to create a auditservice using a wiretap.
eg.
The auditMessageDAO tak
41 matches
Mail list logo
