ution (using commons-exec)
>>>>> - LDAP BC : read and write from LDAP (using JNDI)
>>>>> - CICS BC : read and write messages from CICS mainframe
>>>>> - SAP BC : read and write messages from SAP
>>>>> - EJB BC : currently, I use CX
routes).
On 02/02/2009, James Strachan wrote:
> 2009/2/2 Guillaume Nodet :
>> It might be doable. I guess the way to do that would be to define the
>> JBI endpoint as a wrapper to a camel endpoint. When the JBI endpoint
>> would be initialized / started, a camel route wo
or maintaining the Camel codebase. Just as
> Gert if he was a bit puzzled how to do his StreamCache that uses the
> Async stuff.
> When we get it out of there the codebase is much easier to maintain
> and we have a greater chance to attract potential new committers.
>
> I vote +1 for
ublic/org/apache/camel/apache-camel/2.0-M2/
>
> Please vote to approve this release binary
>
> [ ] +1 Release the binary as Apache Camel 2.0-M2
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
> Here's my +1
>
> Hadrian
applications:
i.e. when you deploy a new application with a few new converters, this
could have side effects on another application, eventually breaking
it.
I wonder if we should have a more static way of configuring converters
for a given route.
Thoughts ?
--
Cheers,
Guillaume Nodet
bundle classloader to find
>> the converters. In old way, we can configure the which kind of converter we
>> want load by importing the converter's package in the camel context OSGi
>> bundle.
>>
>> Now if we want to this feature back, we can revert the change or i
boolean hasOut();
>>> Message getOut(boolean lazyCreate);
>>> void setOut(Message out);
>>>
>>> Message getFault();
>>> boolean hasFault();
>>> Message getFault(boolean lazyCreate);
>>> void removeFault();
>>> // removeFault() is only used in one place
>>
>> +1 to remove it. You can just do setFault(null) instead. I will fix it
>> asap.
>>
>>
>>
>>>
>>> Exception getException();
>>> T getException(Class type);
>>> void setException(Exception e);
>>> boolean isFailed();
>>>
>>> boolean isTransacted();
>>> boolean isRollbackOnly();
>>>
>>> CamelContext getContext();
>>>
>>> Exchange newInstance();
>>> Exchange copy();
>>> Exchange newCopy(boolean handoverOnCompletion);
>>> void copyFrom(Exchange source);
>>>
>>> Endpoint getFromEndpoint();
>>> void setFromEndpoint(Endpoint fromEndpoint);
>>>
>>> UnitOfWork getUnitOfWork();
>>> void setUnitOfWork(UnitOfWork unitOfWork);
>>>
>>> String getExchangeId();
>>> void setExchangeId(String id);
>>>
>>> void addOnCompletion(Synchronization onCompletion);
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> Apache Camel Committer
>>
>> Open Source Integration: http://fusesource.com
>> Blog: http://davsclaus.blogspot.com/
>> Twitter: http://twitter.com/davsclaus
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
e !
Also, any volunteer for upgrading and testing the discovery mechanism is
welcomed !
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****
> blog : http://cmoulliard.blogspot.com
>
>
> On Fri, Sep 4, 2009 at 10:22 AM, Guillaume Nodet wrote:
>
> > I've spotted a few problems in the way the O
h specific version.
>
>
Why ? This would prevent from upgrading one of those bundles without
upgrading the others.
> Willem
>
>
>
> Guillaume Nodet wrote:
>
>> I've spotted a few problems in the way the OSGi metadata for camel jars
>> are
>> compu
amel Committer
>
> *****
> blog : http://cmoulliard.blogspot.com
>
>
> On Fri, Sep 4, 2009 at 10:22 AM, Guillaume Nodet wrote:
>
> > I've spotted a few problems in the way the OSGi metadata for camel jars
> are
> > computed.
ifferent version of them is not recommended.
> Eg routing with XML depends on camel-spring where as the routing model
> is in camel-core etc.
>
> So it make most sense to support upgrading various other camel
> components such as for example camel-jetty, camel-http, camel-velocity
>
it would let us simplify & fix up the osgi
> metadata a bit?
>
> I guess some folks might wanna use osgi camel without spring; but
> maybe camel-osgi's spring dependency could be made optional?
>
>
> 2009/9/7 Guillaume Nodet :
> > No problems for me. Though
mer bundles.
>
> Full gory details here
>
> http://www.osgi.org/blog/2007/04/importance-of-exporting-nd-importing.html
>
>
> --oh
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
r releases often afaik and I'm not sure we really need to
make a decision about that.
>
> Hadrian
>
> Begin forwarded message:
>
>> From: Guillaume Nodet
>> Date: September 15, 2009 10:33:28 AM EDT
>> To: priv...@camel.apache.org
>> Subject
I'll work on backporting the OSGi fixes on the branch today and tomorrow.
This will allow me to test it in real as one of the goal is to be able
to deploy multiple versions of camel in the same OSGi container ...
On Tue, Sep 15, 2009 at 16:49, Guillaume Nodet wrote:
> On Tue, Sep 15, 20
>
>
>
> @@ -837,9 +846,9 @@
>
>
>
> - javax.mail
> - mail
> - 1.4
> + org.apache.servicemix.bundles
> + org.apache.servicemix.bundles.javax.mail
> + ${javax-mail-version}
>
>
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
ed to camel 2.1, but spring
was still using the 1.6 schema handler to load the route which was
failing because of a missing component.
I think we're missing some kind of versioning in the schema ...
Thoughts ?
On Fri, Sep 4, 2009 at 10:22, Guillaume Nodet wrote:
> I've spotted a
t; http://camel.apache.org/schema/spring
> http://camel.apache.org/schema/spring/camel-spring-2.1-SNAPSHOT.xsd
> ">
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *
> blog : http
claus.blogspot.com/
> Twitter: http://twitter.com/davsclaus
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
tivemq.apache.org/camel/schema/spring";
>
> Can you check if your camel context is updated to new camel namespace
> "http://camel.apache.org/schema/spring";
>
> Willem
>
> Guillaume Nodet wrote:
>>
>> Unfortunately, I doubt it will work. The reason is
and try there.
I'll first have a look at the spring-dm code and see what they do. The
most important question is wether they take into account the package
wires.
I'll also try to investigate adding a blueprint integration, which
should solve this very problem in a cleaner way.
>
>
;>
>> [INFO] Error(s) found in bundle configuration
>> [INFO]
>> --------
>> [INFO] For more information, run Mave
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> 2009/9/17 Guillaume Nodet :
>> Right, I missed that. So the point is moot.
>> But as Claus noted, the problem will also happen between 2.1.x and 2.2.x ...
>>
>> On Thu, Sep 17
On Thu, Sep 17, 2009 at 11:17, Claus Ibsen wrote:
> On Thu, Sep 17, 2009 at 10:55 AM, Guillaume Nodet wrote:
>> I've looked at both spring-dm and blueprint, and there is no way to
>> have a single schema namespace supported by two different handlers.
>> I mean, you c
mple copy paste).
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
es.blueprint.mutable.MutableBeanMetadata cannot be
> applied to (org.apache.aries.blueprint.mutable.MutablePassThroughMetadata)
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
test
FWIW, I had troubles setting up the routing logic with the irc
component, because the irc component sends to all connected channels
by default, which looks a bit weird.
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
print the fact that we need to wait until all of those are
available.
I'll try to prototype that this week and i'll keep the list up to date
about that.
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
Actually, for the component factory, the ComponentResolver interface
should be fine ... (forgot about that one).
On Tue, Nov 3, 2009 at 08:49, Guillaume Nodet wrote:
> Yesterday, I've been working again on the blueprint support for camel.
> While working on this, I found we're r
Just raised https://issues.apache.org/jira/browse/CAMEL-3490 for that
On Mon, Jan 3, 2011 at 18:22, Guillaume Nodet wrote:
> On Mon, Jan 3, 2011 at 17:55, Charles Moulliard wrote:
>> What you suggest (component=servlet) is by example what has been done in
>> this p
] [ ] [ 60] Jetty ::
> > Utilities (7.2.2.v20101205)
> > [ 270] [Active ] [] [ ] [ 60] Jetty :: Plus
> > (7.2.2.v20101205)
> > [ 271] [Active ] [] [ ] [ 60] Jetty :: JNDI
> > Naming (7.2.2.v20101205)
> >
> >
> >
> > Regards,
> >
> >
> > Charles Moulliard
> >
> > Sr. Principal Solution Architect - FuseSource
> > Apache Committer
> >
> > Blog : http://cmoulliard.blogspot.com
> > Twitter : http://twitter.com/cmoulliard
> > Linkedin : http://www.linkedin.com/in/charlesmoulliard
> > Skype: cmoulliard
> >
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
o the authentication.
Though forcing the use of JAAS may not be a good idea from a pure Karaf
perspective ...
On Fri, Jan 14, 2011 at 08:27, Guillaume Nodet wrote:
> Right, see how it's done in Karaf for the web console:
>
> http://svn.apache.org/repos/asf/karaf/trunk/webconsole/brandin
gt; [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
> Here's my +1
> Hadrian
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
l: cib...@fusesource.com
>>>> Web: http://fusesource.com
>>>> Twitter: davsclaus
>>>> Blog: http://davsclaus.blogspot.com/
>>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>>
>>>
>>
>>
>>
>> --
>> Claus Ibsen
>> -
>> FuseSource
>> Email: cib...@fusesource.com
>> Web: http://fusesource.com
>> Twitter: davsclaus
>> Blog: http://davsclaus.blogspot.com/
>> Author of Camel in Action: http://www.manning.com/ibsen/
>>
>
>
>
> --
> Claus Ibsen
> -
> FuseSource
> Email: cib...@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
is [1.5,2.0)
On Mon, Jan 31, 2011 at 17:25, Claus Ibsen wrote:
> On Mon, Jan 31, 2011 at 5:14 PM, Guillaume Nodet wrote:
>> Not sure what the issue is, but pax-logging 1.5.x only supports slf4j
>> <= 1.5.11, so you need to make sure the range of the package uses is
>> larg
t?
Not sure what you mean here, but the conversion should be 2.7-SNAPSHOT
-> 2.7.0.SNAPSHOT
>
> Christian
>
> --
>
> http://www.liquid-reality.de
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
> qualifier ::= ( alphanum | ’_’ | '-' )+
>
> So you are right.
>
> 2.7-SNAPSHOT in maven should be 2.7.0.SNAPSHOT in osgi.
>
> Christian
>
> Am 07.02.2011 10:11, schrieb Guillaume Nodet:
>>
>> Not sure what you mean here, but the conversion sh
Eclipse if
> you work with a target platform? Or is this not part of the bundle plugin?
>
> Christian
>
>
> Am 07.02.2011 11:31, schrieb Guillaume Nodet:
>>
>> The maven-bundle-plugin 2.3.4 has just been released, so we could try
>> upgrading to that one.
>&g
ains the id and version of the implementation bundle So Eclipse
> can show you the sources when both bundles are in the target platform.
>
> Christian
>
>
> Am 07.02.2011 11:55, schrieb Guillaume Nodet:
>
> I don't recall anything in the maven bundle plugin about that.
--
>
> It would of course be much nicer if the bundle plugin could also put that
> into the source jar. I do not know if it is possible though.
>
> Christian
>
> Am 07.02.2011 13:25, schrieb Guillaume Nodet:
>>
>> It seems that would require our sources jars to be pac
camel-servlet into
http://svn.apache.org/repos/asf/camel/trunk/platforms/karaf/
> On Fri, Jan 14, 2011 at 5:36 PM, Guillaume Nodet wrote:
>> Shouldn't the component be registered automatically using an activator ?
>> Registering a serlvet is not the standard way in OSGi,
?\$Revision: *[0-9]+ *\$//g'
>
>
>
> --
> Claus Ibsen
> -
> FuseSource
> Email: cib...@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibs
27;s
> opinion, as a Karaf/OSGi expert.
>
>
>
> I really dont understand why you would think its "no brainer" to make such a
> big change "seconds" before you cut the release.
> You are usually very good and careful when you do the releases.
>
> Willem
> --
> FuseSource
> Web: http://www.fusesource.com
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.javaeye.com (Chinese)
> Twitter: willemjiang
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
eft to right on the top row
>>>> and 4 for the one on the bottom row). If it matters my favorites are C3
>>>> and C1, in that order.
>>>>
>>>> If you believe something can be improved, like color, font (style, size
>>>> and placement), please feel free to add your suggestion. I believe the
>>>> original authors (or somebody) will be able to make the improvements.
>>>>
>>>> Thanks,
>>>> Hadrian
>>>>
>>>> [1] https://cwiki.apache.org/confluence/display/CAMEL/Site+Update+Ideas
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -
>>> FuseSource
>>> Email: cib...@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus
>>> Blog: http://davsclaus.blogspot.com/
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
> FuseSource
> Web: http://www.fusesource.com
> Blog: http://willemjiang.blogspot.com (English)
> http://jnn.javaeye.com (Chinese)
> Twitter: willemjiang
>
> Connect at CamelOne May 24-26
> The Open Source Integration Conference
> http://camelone.com
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
https://repository.apache.org/content/repositories/orgapachecamel-074/
>>> The tarballs are here
>>> https://repository.apache.org/content/repositories/orgapachecamel-074/org/apache/camel/apache-camel/2.7.1/
>>>
>>> Please review, test and vote to approve
nary as Apache Camel 2.8.0
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for at least 72 hours.
>
> Here's my +1
> Hadrian
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12316226
>
--
-
gt;
>
> I'll leave the vote open until at least Monday.
>
>
> --
> Daniel Kulp
> dk...@apache.org
> http://dankulp.com/blog
> Talend - http://www.talend.com
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
for at least 72 hours.
>
> Here's my +1
> Hadrian
>
> [1]
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12316226
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
If you want to use InOnly and consume the message and send it to another
>>>> > destination, you could use the following route:
>>>> >
>>>> > from("activemq:My.Queue").
>>>> >
>>>> > to("scalate:com/acme/MyResponse.scaml").
>>>> > to("activemq:Another.Queue");
>>>> >
>>>> > It's possible to specify what template the component should use
>>>> >
>>>> > dynamically via a header, so for example:
>>>> >
>>>> > from("direct:in").
>>>> >
>>>> > setHeader("CamelScalateResourceUri").constant("path/to/my/template.s
>>>> > caml"). to("scalate:dummy");
>>>> >
>>>> > It's possible to specify a template directly as a header the component
>>>> >
>>>> > should use dynamically via a header, so for example:
>>>> >
>>>> > from("direct:in").
>>>> >
>>>> > setHeader("CamelScalateTemplate").constant("<%@ attribute body:
>>>> > Object %>\nHi this is a scalate template that can do templating
>>>> > ${body}"). to("scalate:dummy");
>>>> >
>>>> > The Email Sample
>>>> >
>>>> > In this sample we want to use Scalate templating for an order
>>>> > confirmation email. The email template is laid out in Scalate as:
>>>> >
>>>> > <%@ attribute in: org.apache.camel.scala.RichMessage %>
>>>> > Dear ${in("lastName"}, ${in("firstName")}
>>>> >
>>>> > Thanks for the order of ${in("item")}.
>>>> >
>>>> > Regards Camel Riders Bookstore
>>>> > ${in.body}
>>>> >
>>>> > See Also
>>>> >
>>>> > - Configuring
>>>> > Camel<https://cwiki.apache.org/confluence/display/CAMEL/Configuri
>>>> > ng+Camel> -
>>>> > Component<https://cwiki.apache.org/confluence/display/CAMEL/Compo
>>>> > nent> - Endpoint
>>>> > <https://cwiki.apache.org/confluence/display/CAMEL/Endpoint> -
>>>> > Getting
>>>> > Started<https://cwiki.apache.org/confluence/display/CAMEL/Getting
>>>> > +Started>
>>> --
>>> Daniel Kulp
>>> dk...@apache.org
>>> http://dankulp.com/blog
>>> Talend - http://www.talend.com
>>>
>>
>>
>>
>> --
>> James
>> ---
>> FuseSource
>> Email: ja...@fusesource.com
>> Web: http://fusesource.com
>> Twitter: jstrachan, fusenews
>> Blog: http://macstrac.blogspot.com/
>>
>> Open Source Integration and Messaging
>>
>
>
>
> --
> Principle Technical Writer
> FuseSource
> Phone: (781) 280-4174
> E-Mail: ericjohn...@apache.org
> Blog: http://documentingit.blogspot.com/
> Twitter: finnmccumial
>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
change its route.
I'm not sure exactly all the SPI we'd need yet, but things like
InterceptStrategy, ProcessorFactory or EndpointStrategy may be needed.
So this email is just a heads up and to start any discussion ...
--
----
Guillaume Nodet
executorService(pool).callerRunsWhenRejected(false))
.delay(1000).to("mock:result");
rather than adding a new ThreadPoolProfileBuilder and a call to build ?
>
> Christian
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
>
ommit/a13b4fc19b7fd9a1f6b7e945353d1246151267af
Feedback welcome!
On Thu, Jul 21, 2011 at 11:22, Guillaume Nodet wrote:
> For ServiceMix, we are in need for having *global* interceptors, i.e.
> some kind of static list of interceptors and other strategies. The
> main use case is that user
or camel contexts and register with
> them.
>
> Christian
>
>
> Am 28.07.2011 10:14, schrieb Guillaume Nodet:
>>
>> I found another way which I think is cleaner. I've added a single
>> Container interface with a singleton which is called back whenever a
> that
>>>>> code into camel-core.
>>>>>
>>>> No.
>>>>
>>>> Its an abstract component which has base classes used by XML DSLs such
>>>> as camel-spring and camel-blueprint.
>>>> This ensures that code is r
in our "old" and
> beloved Camel 2.x product.
>
> From community point of view. Start a discussion about Camel 3.0, as
> we think the Camel 2.x product is "old and stable".
> But the community would like a brand new Camel 3.0 in early 2012.
>
>
>
>
>
e expriment
>>> (for example as I did with the simple language improvements project).
>>>
>>>
>>> From community point of view. Keep the API stable in our "old" and
>>> beloved Camel 2.x product.
>>>
>>> From community point of view. Start a discussion about Camel 3.0, as
>>> we think the Camel 2.x product is "old and stable".
>>> But the community would like a brand new Camel 3.0 in early 2012.
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Claus Ibsen
>>> -
>>> FuseSource
>>> Email: cib...@fusesource.com
>>> Web: http://fusesource.com
>>> Twitter: davsclaus, fusenews
>>> Blog: http://davsclaus.blogspot.com/
>>> Author of Camel in Action: http://www.manning.com/ibsen/
>>
>>
>
>
>
> --
> Claus Ibsen
> -
> FuseSource
> Email: cib...@fusesource.com
> Web: http://fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
apache.org/content/repositories/orgapachecamel-007/org/apache/camel/apache-camel/2.2.0/
>
> Please review and vote to approve this release binary
>
> [ ] +1 Release the binary as Apache Camel 2.2.0
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
res or major improvements should be scheduled for 2.4.
> >>>>
> >>>> All dependencies is also using a stable release which should be avail
> >>>> in public maven repos.
> >>>> So we should be good to go.
> >>>
her they are in an osgi environment or not would be transparent
Thoughts ?
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
Gert Vanthienen
>
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> On 7 May 2010 09:19, Claus Ibsen wrote:
> > On Fri, May 7, 2010 at 9:06 AM, Guillaume Nodet
> wrote:
> >> I'm working
ng to have camel-osgi,
camel-spring and camel-spring-osgi. I think camel-spring should be
sufficient...
On Fri, May 7, 2010 at 09:06, Guillaume Nodet wrote:
> I'm working on improving and refactoring the OSGi bits and I'd like to
> propose the following:
> * make camel-osgi a
On Fri, May 7, 2010 at 14:44, Claus Ibsen wrote:
> On Fri, May 7, 2010 at 2:26 PM, Guillaume Nodet wrote:
> > To be more clear and let room for discussion (and still be able to work),
> > i'll do the following:
> > * extract the xml / jabx logic in a separate maven m
anding about the purpose of this
api.
The goal was not to process things in another thread. The goal was to be
scalable.
The AsyncProcessor was only a tool to achieve that. Maybe not the best one,
but still it was working.
Now, the only implementation of AsyncProcessor is t
Sorry, the message has been sent before being finished.
On Tue, May 11, 2010 at 17:58, Guillaume Nodet wrote:
It's been a long time I ad not looked at the asynchronous support in
Camel.I had to do so today and I must say I'm a bit disapointed.
What's the way to have a scalable r
swer is conveyed back to the client ?
>From an api perspective, using the asyncCallback calls on the producer
template could make sense, the problem is that they just spawn a thread,
send the exchange, block for the answer and call the callback. That does
not really help scaling from a thr
On Wed, May 12, 2010 at 03:30, Claus Ibsen wrote:
> On Wed, May 12, 2010 at 9:25 AM, Guillaume Nodet wrote:
> > On Wed, May 12, 2010 at 00:53, Claus Ibsen
> wrote:
> >
> >>
> >> You can use the ToAsync
> >> http://camel.apache.org/toasync.html
On Wed, May 12, 2010 at 04:21, Claus Ibsen wrote:
> On Wed, May 12, 2010 at 10:57 AM, Guillaume Nodet
> wrote:
> > On Wed, May 12, 2010 at 03:30, Claus Ibsen
> wrote:
> >
> >> On Wed, May 12, 2010 at 9:25 AM, Guillaume Nodet
> wrote:
> >> &g
Great, thx. Any idea how that could be done ?
On Thu, May 13, 2010 at 03:51, Claus Ibsen wrote:
> I have created at ticket to track this
> https://issues.apache.org/activemq/browse/CAMEL-2718
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blo
1 Release the binary as Apache Camel 2.3.0
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
> Here's my +1
>
> Hadrian
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
res.xml
> (original)
> +++ camel/trunk/platforms/karaf/features/src/main/resources/features.xml Tue
> Jun 1 06:52:53 2010
> @@ -47,6 +47,8 @@
> spring-dm
> mvn:org.springframework/spring-tx/${spring-version}
> camel-core
> + mvn:org.apache.camel/camel-core-
On Tue, Jun 1, 2010 at 09:21, Claus Ibsen wrote:
> On Tue, Jun 1, 2010 at 9:14 AM, Guillaume Nodet wrote:
>> Those are not needed afaik. Those two jars are actually not bundles
>> and they are both included in camel-osgi / camel-spring and
>> camel-blueprint, so I don'
gi it's not a osgi bundle anymore, and camel-sprint
> doesn't includes the camel-core-xml's class, I think we need to update the
> pom.xml files for it.
>
> Willem
>
> Guillaume Nodet wrote:
>>
>> Those are not needed afaik. Those two jars are actually
> + org.apache.camel.osgi.*;${camel.osgi.version},
> org.apache.camel.spring.*;${camel.osgi.version},
> org.apache.camel.osgi.*;${camel.osgi.version},
>
> org.apache.camel.component;${camel.osgi.split.pkg};${camel.osgi.version},
>
>
web/pax-web-api/${pax.web.version}
> mvn:org.ops4j.pax.web/pax-web-spi/${pax.web.version}
> mvn:org.ops4j.pax.web/pax-web-runtime/${pax.web.version}
> @@ -51,7 +51,9 @@
>
>
> camel-core
> +
> mvn:org.osgi/org.osgi.compendium/${osgi.compendium.ve
t; org.osgi.service.cm;version="[1.2.0,2.0.0)"
>
> You can find out it by using "mvn clean install -Pvalidate".
>
> Willem
>
> Guillaume Nodet wrote:
>>
>> It's not usually a good idea to install
>> mvn:org.osgi/org.osgi.compendium/${osgi.compendi
>> public ExpressionClause> transform() {
>> ExpressionClause> clause =
>> - new
>> ExpressionClause>((ProcessorDefinition)
>> this);
>> + new ExpressionClause>(this);
>> TransformDefinition answer = new TransformDefinition(clause);
>> addOutput(answer);
>> return clause;
>>
>>
>>
>
>
> --
> Cheers,
> Jon
>
> Camel in Action: http://manning.com/ibsen
> Blog: http://janstey.blogspot.com
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
a used component is uninstalled (or stopped even). Should we stop
the camel context too ?
Feedback welcomed !
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
Sorry about that, wrong manip.
On Thu, Jun 17, 2010 at 19:10, wrote:
>
> Contributing<https://cwiki.apache.org/confluence/display/CAMEL/Contributing>
> Page
> *moved* by Guillaume
> Nodet<https://cwiki.apache.org/confluence/display/~gnodet>
>
&
(current only enabled if async routing has been kicked in) but we can
> do this in a general.
>
>
>
>
> --
> Claus Ibsen
> Apache Camel Committer
>
> Author of Camel in Action: http://www.manning.com/ibsen/
> Open Source Integration: http://fusesource.com
> Blog:
l - ServiceMix Committer
> ~~~
> Blog : http://cmoulliard.blogspot.com | Twitter :
> http://twitter.com/cmoulliard
> Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
gt; Apache Camel - ServiceMix Committer
> ~~~
> Blog : http://cmoulliard.blogspot.com | Twitter :
> http://twitter.com/cmoulliard
> Linkedin : http://www.linkedin.com/in/charlesmoulliard | Skype: cmoulliard
>
--
Cheer
> >> --- camel/trunk/parent/pom.xml (original)
> >> +++ camel/trunk/parent/pom.xml Wed Sep 22 13:10:16 2010
> >> @@ -35,7 +35,7 @@
> >>
> >> false
> >>
> >> -5.4.0
> >>
gt; problem with camel-ftp in the past days that may cause some
> > >>>>>>>>>>>> problem (i hope not), other than that we should be able to
> > >>>>>>>>>>>> start the vote today.
> > >>>>>&g
te to approve this release binary. Your vote counts!
>
> [ ] +1 Release the binary as Apache Camel 2.5.0
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
> Here's my +1
--
Cheers,
Guillaume Nodet
Blog: http://gnode
esign. I'm interested in helping Camel maintain its Web site
>>> as well. Are there any tasks that need tackling that I can get started
>>> on?
>>>
>>> --
>>> Principle Technical Writer
>>> Phone (781) 280-4174
>>> Skype finnmccumial
>
m
>> Web: http://fusesource.com
>> Twitter: jstrachan
>> Blog: http://macstrac.blogspot.com/
>>
>> Open Source Integration
>>
>
>
>
> --
> Principle Technical Writer
> Phone (781) 280-4174
> Skype finnmccumial
> E-Mail emjohn...@fusesource.com
> Blog http://documentingit.blogspot.com/
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
patch
and checking the box and pointing to the diff / commit. The point is
to make sure the user actually knows he grants the IP. Actually the
checkbox could be problematic as it apply to the whole issue, whereas
the user could only grant one attachment and not all the attachments.
>
s could make a *massive* difference to both getting contributions
>>>>> and more effectively applying them IMHO. Helping scm-novices
>>>>> contribute to documentation (which they've never really done so far on
>>>>> Camel anyway) seems quite irrelevant in comparison.
>>>> I don't know if this is a scm-novices issues. We had contributions from
>>>> not committers in the past.
>>>> Johan (before his commiter days) is one example, Steve Bate is another. I
>>>> would rather ask them how likely would it be to contribute to doc if they
>>>> had to co/edit/submit-patch, vs edit in-place wiki style.
>>>> I know they are not scm-novices.
>>>>
>>>> I am open to any alternative that would not raise the barrier to entry for
>>>> documentation contributors and that's acceptable to the ASF.
>>>>
>>>> Hadrian
>>>>
>>>>>
>>>>> --
>>>>> James
>>>>> ---
>>>>> FuseSource
>>>>> Email: ja...@fusesource.com
>>>>> Web: http://fusesource.com
>>>>> Twitter: jstrachan
>>>>> Blog: http://macstrac.blogspot.com/
>>>>>
>>>>> Open Source Integration
>>>>
>>>
>>
>>
>
>
>
> --
> Principle Technical Writer
> Phone (781) 280-4174
> Skype finnmccumial
> E-Mail emjohn...@fusesource.com
> Blog http://documentingit.blogspot.com/
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
rather use a system that helps the 99% be more
>> effective.
>> >>>>>>
>> >>>>>> Maybe you should just help out this one CXF person & show them how
>> to
>> >>>>>> fork & commit to github (its very easy), then you can easily pull
>> >>>>>> their commits from there?
>> >>>>>
>> >>>>> Umm.. no. Pulling branches from github is NOT, at this point, an
>> >> acceptable
>> >>>>> way of getting content into an Apache product. They would still
>> need
>> >> to
>> >>>>> create a patch and attach it to JIRA with the "grant" checkbox
>> >> checked.
>> >>>>
>> >>>> Whatever happens folks have to raise a JIRA and click the "grant"
>> >> checkbox.
>> >>>>
>> >>>> I fail to see why a link to a specific commit (i.e. a link to a number
>> >>>> of patches) is any less suitable than a number of patch files being
>> >>>> attached in place to the JIRA. Got anything specific to back this up
>> >>>> or is it just that we've not done it before?
>> >
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
Thx!
On Fri, Dec 10, 2010 at 08:06, Claus Ibsen wrote:
> On Fri, Dec 10, 2010 at 6:05 AM, Claus Ibsen wrote:
>> On Fri, Dec 10, 2010 at 12:46 AM, Guillaume Nodet wrote:
>>> I actually did, and it seems to work for me. What kind of errors do you
>>> have ?
>>
counts!
>
> [ ] +1 Release the binary as Apache Camel 1.6.4
> [ ] -1 Veto the release (provide specific comments)
> Vote is open for 72 hours.
>
> Here's my +1
>
> Hadrian
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
L-3431
>> [3]https://issues.apache.org/jira/browse/SMX4-707
>>
>> --
>> Willem
>> --
>> FuseSource
>> Web: http://www.fusesource.com
>> Blog: http://willemjiang.blogspot.com (English)
>> http://jnn.javaeye.com (Chinese)
>> Twitter: willemjiang
>
>
--
Cheers,
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
auto tool" that was used, it isn't hard to go
> > > through a lot of commits.
> > >
> > > Why is it embarrassing to me? Well, it's a silly little Java program
> > > that is doing the job of something SHOULD have been written in python
> > > or perl or even bash.I'll readily admit that. Best tool for the
> > > job was definitely not applied here.
> > >
> > >
> > > --
> > > Daniel Kulp
> > > dk...@apache.org
> > > http://dankulp.com/blog
> > > Talend - http://www.talend.com
> --
> Daniel Kulp
> dk...@apache.org
> http://dankulp.com/blog
> Talend - http://www.talend.com
>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
fusesource.com
> Twitter: davsclaus, fusenews
> Blog: http://davsclaus.blogspot.com/
> Author of Camel in Action: http://www.manning.com/ibsen/
>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
ou
>> want to use for existing in production Camel 2.8 projects. And then
>> also for new projects using Camel 2.9+. For that to work out, you
>> would need to maintain 2 branches of your custom stuff as its not
>> compatible with both 2.8 and 2.9+.
>>
> Yes that can
oo much effort to do a redesign for just a new feature. The result of this
> is declining quality. At first it is not really visible but I think we
> either are at a point or will soon be where innvation will slow down because
> of all the design issues.
>
>
> Christian
>
>
> --
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> Talend Application Integration Division http://www.talend.com
>
>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
then that could be a solution.
>> As the existing spi, and the new package can co-exists.
>>
>>
>> So if it is only a problem for very few people then I would opt for
>>> simply
>>> doing an incompatible change. But this is a really difficult question.
>>
I did sync CXF and Camel as much as possible a
little
>> while ago, but they will likely drift a bit.
>>
>> Anyway, Karaf 2.2.4, CXF 2.4.3, and Camel 2.8.2 will go a long way to
make it
>> a lot easier and more consistent.
>>
>> Dan
>>
>>
>>
>>>
>>>
>>> Cheers!
>> --
>> Daniel Kulp
>> dk...@apache.org
>> http://dankulp.com/blog
>> Talend - http://www.talend.com
>
>
--
Guillaume Nodet
Blog: http://gnodet.blogspot.com/
Open Source SOA
http://fusesource.com
1 - 100 of 375 matches
Mail list logo
