On Tue, Mar 17, 2009 at 10:44 AM, Willem Jiang wrote:
> +1 for using the Executor to support the managed thread.
Hi
I have fixed this now and will commit a fix in short time on trunk.
>
> Willem
>
> Claus Ibsen wrote:
>> Hi
>>
>> Another minor note.
>>
2009 at 7:22 AM, Claus Ibsen wrote:
>> Hi
>>
>> Any thoughts on this one?
>>
>> It all boils down to a suggestion to add 1 methods to the
>> org.apache.camel.Message API
>>
>> new method:
>> - tryGetBody(Class type)
>>
>> or overlo
Thu, Mar 19, 2009 at 10:37 AM, Claus Ibsen wrote:
> Hi
>
> I had a chat with James about it, and we came to a conclusion.
> See the JIRA for summary.
>
> I am running final unit tests now on the change. Will commit later
> today if all passes.
>
>
>
> On Wed, Mar
greatly appreciated! Thanks...
>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://www.nabble.com/Camel-XMPP-1.6-2.0---OutOfMemoryError%3A-Java-heap-space-tp22485629p22562234.html
>>>> Sent from the Camel Development mailing list archive at Nabble.com.
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> James
>>> ---
>>> http://macstrac.blogspot.com/
>>>
>>> Open Source Integration
>>> http://fusesource.com/
>>>
>>>
>>
>>
>
> --
> View this message in context:
> http://www.nabble.com/Camel-XMPP-1.6-2.0---OutOfMemoryError%3A-Java-heap-space-tp22485629p22601446.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
#x27;ll see the
>> editor. There's currently something a bit wonky with the XML thats
>> generated for some reason though :) but at least the editor looks
>> really cute :)
>>
>> --
>> James
>> ---
>> http://macstrac.blogspot.com/
>>
ryType()
that will throw NoTypeConversionAvailableException
>
> willem
>
> Claus Ibsen wrote:
>> Hi
>>
>> Could you test on the SMX side?
>>
>> We have changed how the getBody(Class type) behaves. Now it returns
>> null if it cannot convert.
>> You should use
--
>> > [ERROR] BUILD ERROR
>> > [INFO]
>> >
>> > [INFO] An error has occurred in JavaDocs report generation:Exit code: 1 -
>> > javadoc: error - invalid flag
your JAVA_HOME to the 1.5se directory?
Yeah it should point to the JRE directory.
>
> Willem
>
> Claus Ibsen wrote:
>> On Mon, Mar 23, 2009 at 11:56 AM, Gary Jones
>> wrote:
>>> On Mon, Mar 23, 2009 at 10:14:26AM +, James Strachan wrote:
>>>>
On Mon, Mar 23, 2009 at 7:31 PM, Marat Bedretdinov
wrote:
> Claus,
>
> Could you give me Camel wiki edit karma so that I can document my latest
> patch?
What is your username on the wiki?
The search is really slow and can timeout if we search on name etc.
>
> Thanks,
>
On Mon, Mar 23, 2009 at 7:49 PM, Marat Bedretdinov
wrote:
> My username is 'marat'
Karma granted.
>
> Thanks,
> Marat
>
> On Mon, Mar 23, 2009 at 2:36 PM, Claus Ibsen wrote:
>
>> On Mon, Mar 23, 2009 at 7:31 PM, Marat Bedretdinov
>> wrote:
>>
he.org/content/repositories/snapshots.
>
>
> Regards,
>
> Gert Vanthienen
>
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
ticles/apache-camel-integration
>
> --
> Cheers,
> Jon
>
> http://janstey.blogspot.com/
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
camel-integration
>
> --
> Cheers,
> Jon
>
> http://janstey.blogspot.com/
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Hi
Thanks for reporting back. I added the note about 2.0.9 is currently used.
On Tue, Mar 24, 2009 at 10:41 AM, Gary Jones wrote:
> On Mon, Mar 23, 2009 at 12:02:08PM +0100, Claus Ibsen wrote:
>> On Mon, Mar 23, 2009 at 11:56 AM, Gary Jones wrote:
>> > On Mon, Mar 23, 2009 a
mq) mailing list archive at
> Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
View this message in context:
> http://www.nabble.com/Camel-1.6-2.0-MINA-UDP-issue-tp22426433p22714860.html
> Sent from the Camel - Development (activemq) mailing list archive at
> Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
k here
> } catch (Exception e) {
> LOG.error("Error while processing XMPP message", e);
> }
> }
>
>
> Is it possible to put this into the 1.6.1 and 2.0 codebase?
>
>
>
>
> Claus Ibsen-2 wrote:
>>
>> On Thu, Mar 19, 2009 at 4:20 PM, orton
-could-be-improved-tp22766622p22777494.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
components as well: JPA, JDBC, SQL.
Any thoughts?
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
drian
>>>
>>> [1] https://repository.apache.org/index.html
>>> [2] http://maven.apache.org/developers/release/releasing.html
>>> [3] https://issues.apache.org/jira/browse/INFRA-1950
>>>
>>>
>>
>>
>> --
>> James
>> ---
>&
rollback as this might
be OK.
>
> Willem
>
> Claus Ibsen wrote:
>> Hi
>>
>> As we work on the Camel 2.0 I would suggest that we start a discussion
>> what should be the preferred error handler defaults in Camel 2.0.
>> What we currently have is the DL
ionErrorHandler support onException.
Allowing you to catch certain exceptions and let it be handled so
there are no rollback.
>
> Roman
>
> 2009/3/31 Claus Ibsen
>
>> Hi
>>
>> As we work on the Camel 2.0 I would suggest that we start a discussion
>> what should
; to move the pom.xml and properties file that's currently at
>>
>> https://svn.eu.apache.org/repos/asf/servicemix/smx4/features/trunk/camel/camel-features/
>> to e.g. a /platform/servicemix-kernel directory in the Camel project.
>>
>> Any thoughs?
>>
>> G
with the tryBlock() name (CAMEL-1447)
As this is an API change I would like to get it in 2.0.
And finally we should have time to fix the community reports bugs and
minor new features to add that we usually
do on a daily basis.
Any thoughts?
--
Claus Ibsen
Apache Camel Committer
Open Source
Hi
The default error handler is now changed in Camel 2.0.
On Wed, Apr 1, 2009 at 11:58 AM, Claus Ibsen wrote:
> On Wed, Apr 1, 2009 at 11:51 AM, Roman Kalukiewicz
> wrote:
>> I would definitely support #1.
>>
>> #3 is not so good as a default one because it can cause s
Hi
Just an updated
#1: DONE
#3: DefaultErrorHandler = DONE
On Thu, Apr 2, 2009 at 7:18 AM, Claus Ibsen wrote:
> Hi
>
> We are in the final phase of Camel 2.0 and need to get the last
> features and fixes done. I have been looking at the JIRA tickets and
> moved stuff for 2.1.
On Fri, Apr 3, 2009 at 3:07 PM, Claus Ibsen wrote:
> Hi
>
> Just an updated
>
> #1: DONE
> #3: DefaultErrorHandler = DONE
#3: TransactionErrorHandler = DONE
#3: DONE
>
>
> On Thu, Apr 2, 2009 at 7:18 AM, Claus Ibsen wrote:
>> Hi
>>
>> We are in the
as well.
So I am in favor of option A.
CAMEL-1475 also hints some more improvements we can do with convention
over configuration, eg if there is only one SpringTransactionPolicy in
the XML then use that.
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog
On Mon, Apr 6, 2009 at 10:12 AM, Claus Ibsen wrote:
> Hi
>
> Background is CAMEL-1475, however the ticket title is a bit misleading
>
> This morning I got Camel to be able to use transacted routes without
> you have to remember to configure a transactedErrorHandler.
> This
, so Camel can lookup and find
the PlatformManager and default to required itself. Just like the JMS
component can do with transacted=true URI option.
On Mon, Apr 6, 2009 at 1:56 PM, Claus Ibsen wrote:
> On Mon, Apr 6, 2009 at 10:12 AM, Claus Ibsen wrote:
>> Hi
>>
>>
t; 4 sec on my laptop.
When we had that performance degrade in Camel 1.6.0 this tests would
take x10 but most of the other tests runs at usual speed.
So its q quick indicator if something is wrong if it suddenly takes
longer/much longer time.
--
Claus Ibsen
Apache Camel Committer
Open S
>>>
>>>
>>> On Apr 6, 2009, at 9:55 AM, 宓学强 wrote:
>>>
>>>
>>>> I wonder which dynamic language should we add for the Dynamic route
>>>> support,Groovy,Ruby,Python or Scala?
>>>> Hope every one can give the opinion and we can negotiate to decide that.
>>>>
>>>>
>>>> --
>>>> 宓学强 allo...@gmail.com
>>>>
>>>
>>
>>
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration
ng, to what the Spring TX
itself requires = NO XML configuration for Camel is needed at all.
Just remember to set the route as transacted using that's it!
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://t
, Apr 2, 2009 at 7:18 AM, Claus Ibsen wrote:
> Hi
>
> We are in the final phase of Camel 2.0 and need to get the last
> features and fixes done. I have been looking at the JIRA tickets and
> moved stuff for 2.1.
>
> There are 2 issues we must address:
> =
tooling work out of the box?
Jonathan, Hadrian you are good at this sort of problem?
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com
Tue, Apr 14, 2009 at 7:48 AM, Claus Ibsen wrote:
>>
>> Next step in improvement would be to handle that the
>> PROPAGATION_REQUIRED bean is optional, so Camel can lookup and find
>> the PlatformManager and default to required itself. Just like the JMS
>> component c
emq/browse/CAMEL-761
>
> Or maybe there is something simpler?
>
> Thanks
>
> --
> View this message in context:
> http://www.nabble.com/dev%40activemq.codehaus.org-bounces-tp23038094p23038094.html
> Sent from the Camel - Development (activemq) mailing list archive at
>
ease mail the
> d...@activemq.codehaus.org mail list with the email address you used to
> register with the issue tracker and we'll add you to the group.'
>
> I tried emailing that mail address but it bounces? I wanted to have a go at
> fixing an issue :)
>
> Jona
Hi Jonathan
You should have been granted karma in Camel JIRA so you should be able
to assign tickets to yourself.
On Tue, Apr 14, 2009 at 2:26 PM, Claus Ibsen wrote:
> Hi
>
> Ah the text was outdated. Camel graduated as a top level project at
> Apache in December 2008 so you should
good - the only missing feature is being
> able to use the project's pom to figure out what versions of things to
> use (like ServiceMix Kernel integration tests do).
> --
> James
> ---
> http://macstrac.blogspot.com/
>
> Open Source Integration
> http://fuse
Hi
Glad to report that we now have done all 4 issues on Camel 2.0 trunk.
So we can start focus on getting the remaining work done so we can get
ready for a release candidate.
On Thu, Apr 2, 2009 at 7:18 AM, Claus Ibsen wrote:
> Hi
>
> We are in the final phase of Camel 2.0 and need t
Hi
Looking at:
http://hudson.zones.apache.org/hudson/job/Camel/lastBuild/testReport/
The camel-jetty component is not tested. Is there a reason for this?
And the new camel-itest-osgi fails constantly.
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog
nyway its there. Just wondered if it was disabled for some reason.
>
> On Sun, Apr 19, 2009 at 5:33 AM, Claus Ibsen wrote:
>
>> Hi
>>
>> Looking at:
>> http://hudson.zones.apache.org/hudson/job/Camel/lastBuild/testReport/
>>
>> The camel-jetty component
or a M2 release. The time is
> also right for a Camel 1.6.1 maintenance release.
>
> Thoughts?
> Hadrian
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apa
http://www.nabble.com/Camel-1.6-2.0-MINA-UDP-issue-tp22426433p23201393.html
> Sent from the Camel - Development (activemq) mailing list archive at
> Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twi
the codebase is much easier to maintain
and we have a greater chance to attract potential new committers.
I vote +1 for this.
Any thoughts?
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/da
Hi
Just a quick info
The Channel ticket is here:
https://issues.apache.org/activemq/browse/CAMEL-1562
And first initial cut committed to trunk
rev: 768186
el-core API needs this
cleanup. You will get to this conclusion if you have been working 8h
around the clock in the camel-core code for as long as I have.
>
>
> Willem
>
>
> Claus Ibsen wrote:
>> Hi Camel riders
>>
>> As you know we are working on Came
sing is not on par with the
other API where we have one liners for most of it.
Commit rev: 768269.
http://svn.apache.org/viewvc/camel/trunk/camel-core/src/test/java/org/apache/camel/component/seda/SedaAsyncProcessorTest.java?view=markup&pathrev=768269
>
> On Fri, Apr 24, 2009 at 07:21
maintain the camel code and the end users using it.
We have timer thereafter to add a more powerfull and real Async
routing capablilites into Camel,
that more resemble what already in the JDK concurrency library.
On Fri, Apr 24, 2009 at 2:19 PM, Claus Ibsen wrote:
> On Fri, Apr 24, 2009 at
On Fri, Apr 24, 2009 at 2:36 PM, James Strachan
wrote:
> 2009/4/24 Claus Ibsen :
>> On Fri, Apr 24, 2009 at 11:23 AM, Guillaume Nodet wrote:
>>> The goal of the AsyncProcessor is to not block the calling thread when
>>> using an InOut exchange mostly.
>>> For
****
> blog http://cmoulliard.blogspot.com
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration
; Freelance Application Development Consultant
> LinkedIn Profile: http://www.linkedin.com/in/johnbekasjr
> http://www.linkedin.com/in/johnbekasjr
>
> --
> View this message in context:
> http://www.nabble.com/The-jmsMessage-is-not-set-yet%2C-call-the-super%27s-createMessageId-tp23283591p23283591.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration
gt; ---> assign this "1234" to a Header
>
>
> Thanks in advance,
> sailaja.
> --
> View this message in context:
> http://www.nabble.com/Facing-problems-while-using-Set-Header-camel-Processor-tp23290594p23290594.html
> Sent from the Camel - Development (activemq) mailing list archive at
> Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel Reference Card:
http://refcardz.dzone.com/refcardz/enterprise-integration
mes and I doubt it would have been so easy if the code was
split.
Isnt it possible to keep camel-test in sync by some copy script that
can copy the src from camel-core to camel-test so its automatic
updated.
>
> Willem
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration:
t
to do in the AsyncCallbacks that was invading the internals in Camel.
Then I would start experimenting with the new API and report findings.
Feedback here is much welcome.
Any thoughts?
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Hi
I have created a ticket to track this
https://issues.apache.org/activemq/browse/CAMEL-1572
And I have attached a patch to address item #1, #2 and #4.
All unit tests passes (core, components, tests, etc.)
On Thu, Apr 30, 2009 at 7:32 AM, Claus Ibsen wrote:
> Hi
>
> You might re
134 ms.
2009-04-30 10:43:58,835 [main ] DEBUG
aultAsyncProcessorTemplateTest - tearDown test: testRequestAsync
On Thu, Apr 30, 2009 at 7:32 AM, Claus Ibsen wrote:
> Hi
>
> You might remember my previous topic about the AsyncProcessor.
> http://www.nabble.com/-DISCUSS---Camel-
camel-core by the copying script.
Yeah its after all only 1 or 2 classes in camel-test.
>
> Thanks,
>
> Willem
>
> Claus Ibsen wrote:
>> On Wed, Apr 29, 2009 at 12:02 PM, Willem Jiang
>> wrote:
>>> Hi riders,
>>>
>>> I'm thinking to do so
change) throws
Exception {
assertEquals("Hello World",
exchange.getIn().getBody());
exchange.getOut().setBody("Bye World");
}
// and we use mocks for unit testing
}).to(&
tart", "Hello",
Future.class);
String response = future.get();
But then I guess this is impossible due to type erasure in java generics :(
No its not!!!
Okay time to hit the streets
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http:/
da.
>
> Thanks,
>
> Willem
>
> Claus Ibsen wrote:
>> Hi
>>
>> Just another update on #3. I had some more fun with Camel and
>> introduced a async() DSL in the route, to turn the route into async
>> from the point forward.
>> The unit
:01 AM, Willem Jiang wrote:
>
>> Hi Hadrian,
>>
>> Just a quick question, when will you cut the release ?
>>
>> Willem
>>
>> Hadrian Zbarcea wrote:
>>>
>>> If you know of any issues that *must* be fixed in these releases please
>>> let
a closer look at my experiments.
>
> Willem
>
> Claus Ibsen wrote:
>> Hi
>>
>> Its me again. Yeah I am due for a run in due time, but just wanted to
>> demo something that is either powerful or scary
>>
>> The code below uses the same route. But as
Hi
I have uploaded a 2nd patch at CAMEL-1572 - (the b patch)
I got the async API prototype also.
On Thu, Apr 30, 2009 at 5:39 PM, Claus Ibsen wrote:
> On Thu, Apr 30, 2009 at 4:00 PM, Willem Jiang wrote:
>> How about introducing Async requestBody API to the template?
>> I
fixed as well.
I have also attached a prototype for a patch for the new async API
experiment I have done. See CAMEL-1572.
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.com/davsclaus
Apache Camel
- camel-cxf
That can have this issue as well sometimes, eg as port 9080, 8080, or
what we use can cause the port number already in use issue.
For inspiration see the camel-ftp there is some base ftp unit test
classes that set ups the feature to use a new number each time.
Any thoughts?
--
Claus
ory: 105M/215M
[INFO]
channel stopped
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
finished: FAILURE
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.b
TestSupport.tearDown(OSGiIntegrationSpringTestSupport.java:58)
On Sun, May 3, 2009 at 11:22 AM, Willem Jiang wrote:
> Hi Claus,
>
> I just did a quick fix for that, it is caused by the changing of the
> Pax-Exam plugin 0.5.0.
> My bad, I should test it before I upgraded the Pax
on your mac?
Yes I can run it on you demand.
Is it just the camel-itest-osgi I need to run mvn clean install or do
you need me to run some other mvn goal?
>
> Willem
> Claus Ibsen wrote:
>> Hi Willem
>>
>> Its better now as the distribution can be bui
re is any different result.
And with regular mvn clean install I get
Results :
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0
So the problem could have been the repo being offline.
>
> BTW, it looks like ops4j.org is back, my local build is OK again.
>
> Willem
> Claus Ibsen wrote
che.org/CAMEL/tutorial-osgi-camel-part2.html
>
> Don't hesitate to provide me your remarks/comments before to distribute it !
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *
> blog :
routing in Camel.
If the user wants to use the regular Camel API (lookup endpoint,
create exchange, create producer, process etc.) there is a helper
method on AsyncProcessorHelper to initiate an async route as well.
Any thoughts?
On Fri, May 1, 2009 at 11:53 AM, Claus Ibsen wrote:
> I h
>> - Part 2d : web and
>> deployment<http://cwiki.apache.org/confluence/display/CAMEL/tutorial-osgi-camel-part2c>
>>
>> link : http://cwiki.apache.org/CAMEL/tutorial-osgi-camel-part2.html
>>
>> Don't hesitate to provide me your remarks/c
producer template so we have a single combined template for all
producer sync and async.
Its about 10 more methods.
On Tue, May 5, 2009 at 11:05 AM, Claus Ibsen wrote:
> Hi
>
> I had some more time to work on this.
> I have attached a 2nd patch on the JIRA ticket 1572.
>
> This
>>> org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358)
>>> > at
>>> >
>>> org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(Privil
turning route into async mode and support thread pools using JDK
executor service.
- Support Jetty continuation with async
Should we mark the old API in Camel 1.x as @deprecated?
On Tue, May 5, 2009 at 4:48 PM, Claus Ibsen wrote:
> Hi
>
> Just wanted to keep you posted.
>
> Had
euedThreadPool$PoolThread.run(QueuedThreadPool.java:522)
> Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.415 sec
>
>
> Kind regards,
> Christopher
> --
> View this message in context:
> http://www.nabble.com/Jetty-unit-https-test-mess
Hi
Status update
On Wed, May 6, 2009 at 9:17 AM, Claus Ibsen wrote:
> Hi
>
> I have committed first cut of the new Async API to Camel trunk.
> See ticket CAMEL-1572 for svn revision and details.
>
> The remaining work:
> - Migrate MulticastProcessor
DONE
> - Remo
way we program
today in Java.
Bug be careful James might read this and ask you to do some prototyping :)
>
> Regards,
>
> Gert Vanthienen
>
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> 20
; camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
>>>> (original)
>>>> +++
>>>> camel/trunk/components/camel-cxf/src/main/java/org/apache/camel/component/cxf/CxfHeaderFilterStrategy.java
>>&g
On Thu, May 7, 2009 at 6:29 AM, William Tam wrote:
> On Wed, May 6, 2009 at 11:55 PM, Claus Ibsen wrote:
>> On Thu, May 7, 2009 at 5:02 AM, William Tam wrote:
>>> On Wed, May 6, 2009 at 9:57 PM, Willem Jiang wrote:
>>>> Hi William,
>>>>
>>>&
uldn't have to worry about this.
>
> Regards,
>
> Gert Vanthienen
>
> Open Source SOA: http://fusesource.com
> Blog: http://gertvanthienen.blogspot.com/
>
>
>
> 2009/5/6 Claus Ibsen :
>> Hi
>>
>> Status update
>>
>> On We
}
>
> // for acceptor
> public Consumer createConsumer(Processor processor) throws Exception {
> this.processor = processor;
> return new QuickfixConsumer(this, processor);
> }
>
> Regards,
>
> Charles Moulliard
> Senior Enterpri
has to be splitted in two endpoints, one corresponding to
> each to avoid both IN/OUT ???*
>
> Regards,
>
> Charles Moulliard
> Senior Enterprise Architect
> Apache Camel Committer
>
> *****
> blog : http://cmoulliard.blogspot.com
>
>
> On Fri, May 8,
>> > class="org.apache.camel.component.quickfix.QuickfixInitiator"/>
>>> >
>>> >
>>> > http://camel.apache.org/schema/osgi";>
>>> >
>>> > >> uri="quickfix-server:META-INF/exam
org.apache.camel.spring.SpringRouteBuilder;
> import org.springframework.context.support.ClassPathXmlApplicationContext;
>
> @@ -30,7 +32,7 @@
> public class PassiveFixGateway extends SpringRouteBuilder {
>
> public void configure() throws Exception {
> -
> from
ring uri, CamelContext context, String
> configuration) {
> super(uri, context);
> this.configuration = configuration;
> }
>
> uri = endpointUri
> configuration = resourceUri
> *context is not equal to Component !!!*
>
>
> On Fri, May 8, 2009 at 2:45 PM, Claus
ExtractBody makes me think it's async method call, but in fact it
> will block the calling thread if the feature is not done yet.
Good idea willem, I was in doubt with a good name so I took the
internal extractBody name at first.
Your idea is much better, so lets use it.
>
> Willem
gt;>>> CamelTransport.
>>>>> The integration test of CustomerServicesTest shows the user case.
>>>>>
>>>>> Since there is no protocol header defined in Camel-xxx component, camel
>>>>> transport need to copy the content-type between the CXF mess
On Fri, May 8, 2009 at 8:52 AM, Claus Ibsen wrote:
> On Wed, May 6, 2009 at 3:41 PM, Gert Vanthienen
> wrote:
>> Hi Claus,
>>
>> Nice work on cleaning up the async API for Camel! Using well-known
>> java.util.concurrency classes to build the API is a goo
for the client API using the
ProducerTemplate there are no problem, as the transaction should
usually not span both the client + "camel".
But for sure that is something you should consider when doing transactions.
Everyting has its pros/cons. Also async messaging.
>
> Willem
>
>
is message in context:
> http://www.nabble.com/Handling-Exception-from-marshal-unmarshal-tp23494097p23494097.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: ht
he/camel/component/xslt/TestBean.java?rev=773781&r1=773780&r2=773781&view=diff
> ==
> ---
> camel/trunk/components/camel-spring/src/test/java/org/apache/camel/component/xslt/TestBean.java
> (original)
ike.
And we could consider having scope as well. So you can define
synchronization hooks at global level, so they apply for all.
Any thoughts?
--
Claus Ibsen
Apache Camel Committer
Open Source Integration: http://fusesource.com
Blog: http://davsclaus.blogspot.com/
Twitter: http://twitter.
dated the design page and moved
the UnitOfWork callbacks from 2.1 to 2.0.
>
> Willem
>
> Claus Ibsen wrote:
>> On Mon, May 11, 2009 at 9:32 AM, Willem Jiang wrote:
>>> Hi Claus
>>>
>>> I really enjoy to read the document that you write.
>
still exists.
Instructions on the Camel download page, how to get it.
On Tue, May 12, 2009 at 2:55 PM, Joe Gottman wrote:
>
>
>
> Claus Ibsen-2 wrote:
>>
>> On Tue, May 12, 2009 at 2:13 AM, Joe Gottman
>> wrote:
>>
>> Can you show the route DSL how you do
houghts?
On Tue, May 12, 2009 at 10:20 AM, Claus Ibsen wrote:
> Hi
>
> Now that the we had an internal API cleanup and the new Async API in place.
> I thought I will take a look at the UnitOfWork and its synchronization hooks.
>
> About synchronization
> =
>
Hi
I have just committed the first cut to trunk.
I decided that onCompletion was a better DSL keyword than synchronize.
I have added a wiki page that shows how to use it and some background on it:
http://cwiki.apache.org/confluence/display/CAMEL/OnCompletion
Any thoughts?
--
Claus Ibsen
obal on the component. But the endpoint can
override if it want to.
Or you can just set it on the endpoint. So you get the best from both worlds.
>
> [1] https://issues.apache.org/activemq/browse/CAMEL-1594
>
> Willem
>
--
Claus Ibsen
Apache Camel Committer
Open Source Integration:
101 - 200 of 2697 matches
Mail list logo
