3 sounds good to me too - could benefit other projects besides just Karaf
and Camel :]
~ Reuben
On Fri, Apr 6, 2012 at 13:04, Christian Schneider
wrote:
> We can do three things:
>
> 1. copy the table printer over to camel till 3.0 is out and generally in
> use
> 2. backport table printer to 2.2
We can do three things:
1. copy the table printer over to camel till 3.0 is out and generally in use
2. backport table printer to 2.2.x in karaf console jar
3. Create an independent jar in karaf for the table printer that camel
can depend on
All options have some good points and I am open to a
Sounds good.
Glen
On 04/06/2012 10:38 AM, Claus Ibsen wrote:
On Fri, Apr 6, 2012 at 3:34 PM, Glen Mazza wrote:
Hi, is there a reason why Camel maintains separate "iBatis" and "myBatis"
components--can we get rid of/deprecate the former? Ideally, the renaming
of a project should not need to t
By using a ByteArrayInputStream as payload, and a "warmed up" system (I
sent 100 messages before the measurement to warm up the system) I got the
following results with the payload of 2046 bytes:
testUnmarshallConcurrent() took 2202ms (5196ms by using a string as payload
and a cold system)
testUnm
On Fri, Apr 6, 2012 at 3:34 PM, Glen Mazza wrote:
> Hi, is there a reason why Camel maintains separate "iBatis" and "myBatis"
> components--can we get rid of/deprecate the former? Ideally, the renaming
> of a project should not need to trigger a second component in Camel,
> renaming the component
in light of feedback from Karaf committers [1], would it be okay to copy
Christian Schneider's table printer [2] into the Camel Karaf commands
project (org.apache.camel.karaf.commands.internal) as a private utility
class, at least until it's available in a Karaf release?
i strongly agree with Clau
Hi, is there a reason why Camel maintains separate "iBatis" and
"myBatis" components--can we get rid of/deprecate the former? Ideally,
the renaming of a project should not need to trigger a second component
in Camel, renaming the component (or aliasing it) should be sufficient.
Glen
--
Glen
