On Thu, Sep 17, 2009 at 7:06 PM, Winsks wrote:
>
> Thanks for the info... I am able to do that now with the help of
> tag along the route to
> convert the SOAPMessage to string...
> I have an other doubt; While configuring Camel CxF endpoints through spring
> configuration like below,
>
>
Thanks for the info... I am able to do that now with the help of
tag along the route to
convert the SOAPMessage to string...
I have an other doubt; While configuring Camel CxF endpoints through spring
configuration like below,
http://localhost:8080/websvc/JaxWsService";
serviceCl
Hi
onCompletion did the trick.
Camel rocks!
Keep up the good job!
regards,
attila
Claus Ibsen-2 wrote:
>
> Another solutions is to use the onCompletion callback so you can write
> to the DB when the file exchange is done
> http://davsclaus.blogspot.com/2009/06/on-road-to-camel-20-oncompletion
I just create a JIRA[1] and committed a quick fix for it.
BTW, I also back ported the CAMEL-1936 into camel-1.x branch.
[1] https://issues.apache.org/activemq/browse/CAMEL-2020
Willem
Claus Ibsen wrote:
On Thu, Sep 17, 2009 at 10:30 AM, Willem Jiang wrote:
Yes, we fixed the NPE of BundleCon
Another solutions is to use the onCompletion callback so you can write
to the DB when the file exchange is done
http://davsclaus.blogspot.com/2009/06/on-road-to-camel-20-oncompletion.html
On Thu, Sep 17, 2009 at 12:06 PM, Bak Attila wrote:
>
> Hi
>
> I am using m02. I did not say that it is not
On Thu, Sep 17, 2009 at 12:06 PM, Bak Attila wrote:
>
> Hi
>
> I am using m02. I did not say that it is not propagated to the end. But
> there i will have many splitted messages. And i want somehow wait for the
> last one :)
> That is the task. I could naturally write(overwrite) it each time in th
Hi
I am using m02. I did not say that it is not propagated to the end. But
there i will have many splitted messages. And i want somehow wait for the
last one :)
That is the task. I could naturally write(overwrite) it each time in the DB.
But i do not want to do that if waiting for all to be proce
Hi
What version of Camel are you using?
I do think we have ensured that properties/headers are propagated when
using xslt and the likes.
You can use the tracer to see how you message looks like while being
routed and where the filename is lost.
http://camel.apache.org/tracer
On Thu, Sep 17, 20
Hi
That is the current design when Camel was created to pass messages
using a copy mechanism.
So when you route it over SEDA it "looses" the original JmsMessage
object as its no longer bound to the JmsConsumer.
So if you need to preserve some special data then extract that
manually and set as cam
Hi,
I have the following use case:
I have an incoming file in xml. This will be validated, then transformed
with xslt, splitted after the transformation and finally the splitted parts
will be persisted into a DB. Configured like:
from("file:src/data/generated?noop=true").convert
On Thu, Sep 17, 2009 at 10:30 AM, Willem Jiang wrote:
> Yes, we fixed the NPE of BundleContext[1] few month ago.
> Maybe we need to back port this fix to camel 1.6.x.
>
> [1] https://issues.apache.org/activemq/browse/CAMEL-1936
Yeah I think so if its easy and doable. SMX users will still be usin
Hello.
I recently changes some routes to use SEDA instead of direct and since then
started to get ClassCastException on the following code in my processor.
JmsMessage in = (JmsMessage) exchange.getIn();
ActiveMQTextMessage activeMQTextMessage = (ActiveMQTextMessage)
in.getJmsMessage();
Yes, we fixed the NPE of BundleContext[1] few month ago.
Maybe we need to back port this fix to camel 1.6.x.
[1] https://issues.apache.org/activemq/browse/CAMEL-1936
Willem
Claus Ibsen wrote:
On Thu, Sep 17, 2009 at 9:25 AM, TheWinch
wrote:
Very strange behaviour.
I just stopped servicemix
On Thu, Sep 17, 2009 at 9:25 AM, TheWinch
wrote:
>
> Very strange behaviour.
> I just stopped servicemix and restarted it (without clearing the bundles
> cache) and booom, the component seems to work !
>
> I think my issue is more related to the Karaf container than to Camel. The
> fact is at
Very strange behaviour.
I just stopped servicemix and restarted it (without clearing the bundles
cache) and booom, the component seems to work !
I think my issue is more related to the Karaf container than to Camel. The
fact is at the beginning my component had some missing dependencies, tha
Hi Claus,
I have tested several configurations.
1. As long as I stick to some relative format, it works fine, but I don't
know where the scanned directories are supposed to be located. Have an idea
for this point ?
2. I have tested routes like "file://C:/toto", "file:///C:/toto",
"file:C:/toto
16 matches
Mail list logo
