).
How can this be done in an easy way (with a splitter) ... ?
The aim ist to get one Message (with one Customer in the body) out from a
JMS-Queue and put n messages (with one Adress[i] in the body) to a JMSQueue
DRy
--
View this message in context:
http://old.nabble.com/Splitting-nested
e the beast a little bit ... :wistle:
We now try (or evaluate) to build a camel-based system that replaces the
eGate installations on some of the remote systems. Therefore we need an
component/adapter (or bean(?)) that could send and receive messages to and
from egate (not completely JMS compatible).
also worked with the SeeBeyond/SUN
products for years
... DRy
--
View this message in context:
http://old.nabble.com/Component-Adapter-for-SeeBeyond-eGate-and-or-SUN-JCAPS-ICAN-tp26358554p26358554.html
Sent from the Camel - Users mailing list archive at Nabble.com.
.start(ServiceSupport.java:55)
at
org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:868)
at
org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:197)
at
org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:101)
... 23 m
Hi,
Claus Ibsen-2 wrote:
>
> We try to update it while we work on it. Will be too hard / near
> impossible after the release to dig in the JIRAs and commit logs to
> write the release notes afterwards. So we do try to keep it as up to
> date as possible. All together makes it easier for us and
Null()) and myObject is null I'll get
an exception
Caused by: java.lang.IllegalArgumentException: bean, ref or beanType must be
specified on: Bean[]
at org.apache.camel.util.ObjectHelper.notNull(ObjectHelper.java:260)
... DRy
--
View this message in context:
http://old.nabble.com/Dynamicly-en
se notes are up to date while snapshot
development ... great! Thx!
... DRy
--
View this message in context:
http://old.nabble.com/TraceableUnitOfWork-%282.1-Snapshot-2009-11-15%29-tp26357100p26357140.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
I can't find TraceableUnitOfWork in the newest 2.1 snapshot (should be in
camel-core-2.1-SNAPSHOT.jar) ...
... DRy
--
View this message in context:
http://old.nabble.com/TraceableUnitOfWork-%282.1-Snapshot-2009-11-15%29-tp26357100p26357100.html
Sent from the Camel - Users mailing
object
from(...)
.choice()
.when("object != null")
.to(...)
.otherwiese()
.to(...)
.end();
The aim of this is to dynamicly enable or disable parts of the route by
using boolean expressions based on created objects ...
... DRy
--
View th
LBeans). The
onException(UnmarshalException.class) handled the exception - even if there
is a onException(Throwable.class).
... DRy
--
View this message in context:
http://old.nabble.com/Exception-handling-...-onException-tp26215607p26322069.html
Sent from the Camel - Users mailing list archive at Nabble.com.
11, 2009; 09:33am" ... this snapshot zip is dated
"Wed Nov 11 10:28:51 GMT+00:00 2009" ... so I thing it's included - but I'm
not sure.
... DRy
--
View this message in context:
http://old.nabble.com/Exception-handling-...-onException-tp26215607p26303211.html
Sent from
tends Exception {
...
}
so the hierachy is
UnmarshalException
Exception
Throwable
Serializable
... DRy
--
View this message in context:
http://old.nabble.com/Exception-handling-...-onException-tp26215607p26297084.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
Claus Ibsen-2 wrote:
>
> I had a look and created a ticket to improve/fix this issue
> https://issues.apache.org/activemq/browse/CAMEL-2158
>
> The current code did stop to eagerly instead of finding better
> candidates longer up the exception hierarchy.
>
Nice! Thx
o the intended
UnmarshalException will endup in onException(Exception.class).
Why does camel test "from the bottom (nested caused by) and recursive up in
the exception hierarchy" and not vise versa ... ?
... DRy
--
View this message in context:
http://old.nabble.com/Exception-hand
e needed jars (from camel 2.1 snapshot or other
needed projects). We do this, because we start with activemq and than add
some camel functionality.
DRy
--
View this message in context:
http://old.nabble.com/Exception-handling-...-onException-tp26215607p26271839.html
Sent from the Camel - Users
Hi,
any ideas so far ... ?
DRy
--
View this message in context:
http://old.nabble.com/Exception-handling-...-onException-tp26215607p26240885.html
Sent from the Camel - Users mailing list archive at Nabble.com.
Hi,
we use one of the latest 2.1 snapshots (I will have a look at the exact date
tomorrow).
We use the onException-expressions (from the example below) in a
RouteBuilder-class with one defined route. Both onException are placed
before the route definition. So far the scope is global.
DRy
it over network.
>
I used an old version of the object from our CVS-Repository that did not
implement Serializable ... :wistle:
But ... I could not see any exceptions when camel tries to put the message
to the jms queue ... ?
... DRy
--
View this message in context:
http://old.nabble.co
m.itellium.eai.camelexample.entity.custo...@509bfc(oid=1,name=Name1,oversion=1)]
I had tryed to use a route definition without any ben-call ... same effect
...
Im not sure ... but this may be a problem in the latest snapshot?
... DRy
--
View this message in context:
http://old.nabble.com/JPA%
you.
>
>
Sorry, but that didn't help at all ...
I want to know how to pass a parameter for a namedQuery-based jpa consume in
something like that
from("jpa:com.test.entity.Customer?consumer.namedQuery=findByOid)
where findByOid is defined in my orm.ml
SELECT c FROM Cust
Hi,
I defined two named-queries in my orm.xml:
SELECT c FROM Customer c
SELECT c FROM Customer c WHERE c.oid = :oid
I can use the "findAll" named-query to consume customer-objects
from("jpa:com.test.entity.Customer?consumer.namedQuery=findAll&delay=1&consumeLockEntity=t
same
cases). But setting the route-id in a global onException (defined in the
RouteBuilder) does not work ...
... DRy
DulmerLucsly wrote:
>
> I created a JIRA for the id problem
>
> https://issues.apache.org/activemq/browse/CAMEL-2109
>
> What still bothers me is the last
hange. You have to get hold of it from a property
>
> Exception cause = exchange.getProperty(Exchange.EXCEPTION_CAUGHT,
> Exception.class);
>
Yes, this is implemented in LogEceptionBean.
If I do not use handled(true) I endup in DeathLetter-ErrorHandler ...
... DRy
--
View this messa
re.schema.entity.Customer,
Body:com.itellium.eai.store.schema.entity.custo...@1e335d7(oid=1,name=Name1,oversion=1),
Exception: org.apache.camel.CamelExecutionException: Exception occurred
during execution on the exchange: Exchange[Message:
com.itellium.eai.store.schema.entity.custo...@1e335d7(oid=1,name=
Hi,
having a user defined id is very important if you plan to use JMX-based
administration (done by non-developers "dummies") for your application (as
I/we do). We must be able to identify and start/stop routes via call to JMX
or JConsole.
I would prefer the "route(...)" solution ... but does t
25 matches
Mail list logo
