Hi Sergey,
the component looks pretty good already. There is one thing though I
would like to discuss.
More or less the core of this component is the OSGi service we use to
communicate between the bundles. You currently use the camel Processor
interface for this.
While this is quite suitab
Excellent remark Christian.
I have also another concern regrading to the component which is : "Does it
support TX propagation with or without Spring ?"
https://issues.apache.org/jira/browse/CAMEL-5368
https://issues.apache.org/jira/browse/CAMEL-5292
On Wed, Jun 20, 2012 at 10:36 AM, Christian S
I'm a bit skeptic about this component.
It seems at first glance that if conflates a few things like osgi
service access, multicast, etc...
If the goal is to do inter-bundle communication, the new component
coming from CAMEL-5370 should already do that and I don't really see
the need for the compon
Hi,
When my route is shutting down in Camel 2.9.2, I get a
NullPointerException on line 108 of SedaConsumer. The line reads:
LOG.debug("Preparing to shutdown, waiting for {} consumer threads
to complete.", latch.getCount());
Is it possible that latch is null? Am I doing something wrong, or
On Wed, Jun 20, 2012 at 10:15 AM, Alex Anderson
wrote:
> Hi,
>
> When my route is shutting down in Camel 2.9.2, I get a
> NullPointerException on line 108 of SedaConsumer. The line reads:
>
> LOG.debug("Preparing to shutdown, waiting for {} consumer threads
> to complete.", latch.getCount());
On Wed, Jun 20, 2012 at 7:12 AM, vishal1981
wrote:
> Thank you for your reply.
> I have ended up doing the following (given my limited knowledge of J2EE)
> 1. Define a @Service class in JBoss to act as a wrapper to my camel context.
> (We are on EJB 3.0 and hence dont have @Singelton).
> 2. This
hello,
I split messages using
from(incomingQueue)
.startupOrder(1)
*.split().tokenizeXML("update", "dbStream")*
.convertBodyTo(Document.class)
.choice()
.when().xpath(SUBSCRIPTION_XPATH)
.to(AGGREGATE_MESSAGES)
.otherwise()
.to(PRODUCERS)
.end();
however, when the XML does not contain neither n
> This has been fixed. The issue is the seda consumer has not been
> started prior to shutdown.
Thanks, Claus. Has the fix been released yet?
On Wed, Jun 20, 2012 at 2:10 PM, Alex Anderson wrote:
>> This has been fixed. The issue is the seda consumer has not been
>> started prior to shutdown.
>
> Thanks, Claus. Has the fix been released yet?
No will be in 2.9.3 and 2.10
--
Claus Ibsen
-
FuseSource
Email: cib...@fuse
On Wed, Jun 20, 2012 at 1:02 PM, PJ Walstroem wrote:
> hello,
> I split messages using
>
> from(incomingQueue)
> .startupOrder(1)
> *.split().tokenizeXML("update", "dbStream")*
> .convertBodyTo(Document.class)
> .choice()
> .when().xpath(SUBSCRIPTION_XPATH)
> .to(AGGREGATE_MESSAGES)
> .otherwise()
if the filter() Predicate returns false, I assume the processing stops there?
I would like to go beyond the split() and carry on with the .convertBodyTo()
etc. in case the filter() returns false.
I tried something like
from(incomingQueue)
.choice()
.when().xpath(UPDATE_XPATH)
.split().tokenizeXML(
>
> No will be in 2.9.3 and 2.10
Nice. I notice from JIRA that there aren't many issues left; is there
a date set for release?
Hi
Easier to crete a route for the splitter
And then have another route that does the filter. And use the direct
endpoint to call the other route.
from X
filter bla
to splitme
end
common stuff here
from direct:splitme
split tokenize xml
On Wed, Jun 20, 2012 at 2:55 PM, PJ Walstr
On Wed, Jun 20, 2012 at 2:57 PM, Alex Anderson wrote:
>>
>> No will be in 2.9.3 and 2.10
>
> Nice. I notice from JIRA that there aren't many issues left; is there
> a date set for release?
2.10 is soon, eg a RC has been cut, then it has the testing/voting phase.
When 2.10 is out, we wanna cut a
thank you, that worked perfectly.
--
View this message in context:
http://camel.465427.n5.nabble.com/Split-how-to-leave-message-untouched-tp5714734p5714749.html
Sent from the Camel - Users mailing list archive at Nabble.com.
I tested to send an "Expect: 100-continue" with SoapUI, and my service runs
well. The error must then not come from this.
Actually, I am not able to find what induce this behavior. Sometimes it
works, sometimes not. I have 2 different wireshark traces that are similar
and the behavior of my service
Hi Camel Experts -
I have a route that uses the HTTP component to call a web service. If the
HTTP component returns
"org.apache.camel.component.http.HttpOperationFailedException", then the
definition specifies to attempt redeliveries.
The RedeliveryPolicy specifies a redelivery delay of 15 sec
Hi Claus,
thanks for your reply! The protocol is indeed line based. I actually tried
to write my own codec, but without success, the decode method always was
called two times, and only the result of the first call ended up in the
message body. That's why I was asking for mina2 docu.
Anyway, I end
Hello Charles,
The component does not contain any transaction-specific or spring-specific
logic.
Handling of transactions should be done using transactional-client
(http://camel.apache.org/transactional-client.html) EIP.
Basically, if you need to call the consuming bundles in a transaction sta
We are running a Karaf 2.2.7 server with camel 2.8.4 routes that moves
message from an ActiveMQ 5.6.0 standalone instance to a WebsphereMQ server
and vice versa. After running for around 2 weeks Karaf starts throwing Out
of Memory Error and has to be restarted. The routes are pretty simple and
on
You set transacted to true but didn't provide a transaction manager. In
your Camel route you also don't use transacted(). This looks false. Could
you change this?
Best,
Christian
Sent from a mobile device
Am 20.06.2012 22:52 schrieb "Jason Queen" :
> We are running a Karaf 2.2.7 server with came
I am new to Camel and Camel Bindy, I am trying to understand Bindy api for
parsing flat file. I need a sample code (like a main class) to test Bindy
api.
I have looked at the documentation and could only find an example with
integration camel.
--
View this message in context:
http://camel.46542
Does camel Bindy supports text file (text file) processing. I am looking the
documentation and I see the annotations only for CSV file and fixed length
files.
In my case, I need to process flat files (.txt) which have pipe separated
data.
--
View this message in context:
http://camel.465427.n5.
Christian,
Yes I will try setting it with Spring's
org.springframework.jms.connection.JmsTransactionManager and the flag on the
routes. We have only used WMQ up until recent, so im new to using AMQ. The
WMQ components wouldnt start up without one defined until i configured it
with a manager. I
Hello Christian,
Firstly I thought about some kind of indirect dependency on camel, but I
suppose that such
an indirection will complicate the component with copying of headers, bodies,
properties,
etc. from and to a camel exchange in case of duplication of camel exchange api
(lightweight analog
Thanks!
You are right :)
--
View this message in context:
http://camel.465427.n5.nabble.com/How-to-post-to-restful-service-in-camel-routes-tp5714698p5714789.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi Guillaume,
Of course if there is more convenient way to communicate between
bundles there is no need in the component. On the moment of development
of this component there were multiple ways to do that, for instance:
1. jms component which is rather heavyweight to do inter-bundle communication
For sure that camel-bindy supports also a text file where the separator
is a pipe.
Here is an example
*case 3 : separator = '|'*
Compare to the previous case, the separator here is '|' instead of ';' :
10| J| Pauline| M| XD12345678| Fortis Dynamic 15/15| 2500| USD| 08-01-2009
@CsvRecord( sepa
Yeah, it's well documented at [1].
[1] http://camel.apache.org/bindy.html
Best,
Christian
On Thu, Jun 21, 2012 at 8:23 AM, Charles Moulliard wrote:
> For sure that camel-bindy supports also a text file where the separator is
> a pipe.
> Here is an example
>
> *case 3 : separator = '|'*
>
> Comp
Yeah, and I agree leveraging OSGi services for that is a good idea.
That's not really what I'm concerned about.
The goal is to have a way to multicast a message to a set of endpoint
which will be discovered at runtime, and that's not really OSGi
specific (though the fact that OSGi has a service re
Hi
Besides Bindy there is other Camel components for flat files parsing.
http://camel.apache.org/data-format.html
One of the projects I think seems to be very compelling is the new
beanio coming in the new Camel 2.10 release (out later this month)
http://camel.apache.org/beanio.html
On Thu, Ju
In [1] you can read about how to run Camel standalone with a Main
class/method.
In [2] you can find a unit tests of camel-bindy. Our unit tests are always
a good place to search for solutions/examples. Look around at [3]...
[1]
http://camel.apache.org/running-camel-standalone-and-have-it-keep-runn
Sergey,
I agree on Guillaume remark. We should improve what we have in camel
project instead of creating a new component. There is a new one "direct-vm"
which has been created in camel 2.10 (camel-core) to support communication
over camelContext when the camel routes runs in the same JVM. Personal
Hi
This has been improved in Camel 2.9.1 onwards
https://issues.apache.org/jira/browse/CAMEL-4950
- Graceful Shutdown is now more aggressive if timeout occurred during
shutdown, rejecting continued processing of messages or redeliveries.
There is a default timeout of 5 minutes in the graceful sh
On Wed, Jun 20, 2012 at 10:21 PM, Alexander Kaiser
wrote:
> Hi Claus,
>
> thanks for your reply! The protocol is indeed line based. I actually tried
> to write my own codec, but without success, the decode method always was
> called two times, and only the result of the first call ended up in the
+1
I like that aproach. It would make the OSGi services component a lot simpler.
from("foo:bar").recipientList(osgiServices("myldapfilter"))
I guess we can use a similar aproach to achieve load balancing. Not sure if the
example below already would work but I am sure we could make it work this
That's really my main goal. If we fit into what already exists more,
we'll be able to better leverage everything.
On Thu, Jun 21, 2012 at 8:48 AM, Christian Schneider
wrote:
> +1
>
> I like that aproach. It would make the OSGi services component a lot
> simpler.
>
>
> from("foo:bar").recipientLi
Agree, I think that enhancing the existing could achieve this.
Regards
JB
On 06/21/2012 08:51 AM, Guillaume Nodet wrote:
That's really my main goal. If we fit into what already exists more,
we'll be able to better leverage everything.
On Thu, Jun 21, 2012 at 8:48 AM, Christian Schneider
wro
38 matches
Mail list logo
