Re: Apidocs broken

I did generate the apidocs for 2.2.0 over the weekend and uploaded camel-core and camel-spring to apache. Now we have to wait for replication. The url will also change to include the version as well. I will post another message with the new url once it's all over. Hadrian On May 4, 2010, at 3:

Re: Apidocs broken

12:30 PM, Hadrian Zbarcea wrote: > I did generate the apidocs for 2.2.0 over the weekend and uploaded camel-core > and camel-spring to apache. Now we have to wait for replication. > The url will also change to include the version as well. I will post another > message with the new

Re: Testing existing routes using Camel Test

What about using properties for the endpoint uris? Hadrian On May 25, 2010, at 3:19 PM, Steve Holmes wrote: > > Hi All! > I was wondering if there was any way to mock out the endpoints for existing > routes (with existing endpoints). Or if there was some way to inject the > endpoint at run-time

[ANNOUNCE] Apache Camel 2.3.0 Release

A new release of Apache Camel [1] is out after a bit over 3 months of hard work. Our thanks and gratitude go to the vibrant and growing community and all the contributors who made Camel a stable, mature and production ready project. Special thanks go to the many other projects, open source or no

[ANNOUNCE] Apache Camel 1.6.3 Release

The older Camel 1.x [1] is still in use and very stable but a few issues have been fixed over the past six months since the last release. Therefore we thought appropriate to issue a new 1.6.3 maintenance release [2] which comes with 39 issues resolved (see release notes [3]) such as: •

Re: NullPointerException in ExchangeHelper.convertToType

Hi, You can try getting the source and building it locally as well. $ mvn install -Dtest=none will skip the tests making the build much faster. Hadrian On Jun 28, 2010, at 11:01 AM, Mikael Vik wrote: > > I have now double checked after running mvn -U clean install forcing a > download of the l

Re: Using Policy to alter Definitions before building

Should we continue the discussion here or in the jira? Not sure if I get your point. To me a policy is meant exactly for that: to wrap a part of a route and inject extra processing. The wrap method returns a Processor that does some stuff and at some point delegates to the inner Processor that

Re: Using Policy to alter Definitions before building

exchange.getIn().setHeader(name, "was wrapped"); > processor.process(exchange); >} >}; >} > >} > > > > > On Wed, Jul 7, 2010 at 8:18 AM, Claus Ibsen wrote: >> On Wed, Jul 7,

Re: Using Policy to alter Definitions before building

Fair enough, let's do that. I think beforeWrap is actually better though. And then we document how it could/should be used. On Jul 7, 2010, at 3:51 AM, Claus Ibsen wrote: > On Wed, Jul 7, 2010 at 9:46 AM, Hadrian Zbarcea wrote: >> That works quite well actually. What would be goo

Re: Using Policy to alter Definitions before building

Thanks Claus, I can do it in the morning. It got kinda late. Hadrian On Jul 7, 2010, at 4:17 AM, Claus Ibsen wrote: > On Wed, Jul 7, 2010 at 10:07 AM, Hadrian Zbarcea wrote: >> Fair enough, let's do that. I think beforeWrap is actually better though. >> And then we d

[ANNOUNCE] Apache Camel 2.4.0 Release

The Apache Camel project [1] celebrates the new 2.4.0 release [2]. This release comes a bit earlier than the usual once a quarter release, but the quantity and quality of the issues resolved surely prompted it, most notably the async support, osgi related improvements and the move to spring 3.0.

Re: Camel-QuickFIX jar issues

Thanks for reporting this. I created https://issues.apache.org/activemq/browse/CAMEL-3076. Unfortunately jars are not available in any m2 repo, so we'll have have to republish them in some public place. I will try to get in touch with Steve for the second part of your question. Cheers Hadrian

Re: Problem with cron expression configuration in camel-context with spring

Hi, Try this: uri="quartz://sample/trigger1?job.name=sampleJob&cron=0+0/5+*+?+*+1-7" or even: uri="quartz://sample/trigger1?cron=0+0/5+*+?+*+1-7" Note the double slashes after "quartz:" and the spaces replaced with '+'. it seems to me that the job name is not set properly anyway, and I am looking

Re: Problem with cron expression configuration in camel-context with spring

consistently wether the double slashes are present or not (with exceptions mandated by specs, such as "http://";). Hadrian On Aug 30, 2010, at 9:50 PM, Hadrian Zbarcea wrote: > Hi, > > Try this: > uri="quartz://sample/trigger1?job.name=sampleJob&cron=0+0/5+*+?+*+1-7

Re: Problem with cron expression configuration in camel-context with spring

Yeah, it's a parameter parsing and url normalizing issue, I'll have to look into. But you are correct, that is the wrong, unexpected but consistent and predictable outcome of not having the double slashes. Not nice, I know but it's easy to avoid it. Watch the CAMEL-3091 issue for more details (

Re: Camel-QuickFIX jar issues

Steve has not been involved, although he has made an offer around april to contribute significant improvements to the camel-quickfix component. He provided some hints about what he would change. I did write Steve a week or so ago, but did not get an answer yet. That said if there are any concr

Re: Apache Camel 2.5 Release inquiry

The short answer is yes, it will be released before Nov. Hadrian On Sep 15, 2010, at 12:55 PM, Claus Ibsen wrote: > On Wed, Sep 15, 2010 at 6:49 PM, kumaap wrote: >> >> Hi Just wondering when 2.5 will be released , will it be released before >> November ? > > Yes its being discussed at the Cam

Re: Camel-QuickFIX - JMX console to invoke quickfix server operations

Actually I hope to get it in this week, in time for camel-2.5.0. Hadrian On Sep 21, 2010, at 7:05 AM, Stephen Bate wrote: > Hello Vid, > > I'm not a Camel committer. I've made the code available to the Camel > developers and they are reviewing it and will probably want to make a few > changes.

Re: Camel Component for the OFTP2 protocol

Bruno, I couldn't find the code/jar/doc for the camel-oftp component. Odds are interested users won't either (easily). Your blog post does not show what jars are needed and where to find them either. Did I miss it? Could you please provide directed links? Thanks Hadrian On Sep 21, 2010, at 3

Re: Endpoint consumer created only on from()

The question is more what MEP does the remote server use. The choices you exposed seem to imply that the remote server would return incoming files, which would be an InOut. However, an ftp server or file system (an smtp server as well) use an InOnly pattern (on the producer side) so there is no

Re: Camel Exchange Patters

Let me try to clarify this a bit, because there are 2 or 3 things mixed up in this thread. Because "Working on IN is just much easier to explain and use for end users" doesn't necessarily mean that that is what you should do. And the "use" part is debatable anyway. Every node on the route is a

Re: Camel Exchange Patters

That's a bit extreme, but yes, that's the idea. More precisely, not when you want to change the Exchange, you cannot do that, but when you want the message processed by the remaining of the route to be different. One more thing to keep in mind is that there are 2 kinds of "headers", we call the

Re: Camel Exchange Patters

Let's not get there (again). The community agreed already at least twice that this api is a good abstraction of what we try to do. As any abstraction it has to be properly documented. If it's not clear enough, that's where I would focus. Hadrian On Sep 24, 2010, at 8:53 AM, Claus Ibsen wrote:

Re: Camel Exchange Patters

on again. Otherwise it's just a useless statement, that would bring more confusion to users than help anything. Or make such statement on the dev@ list rather than user@ (which is what I should have too). My $0.02, Hadrian On Sep 24, 2010, at 9:30 AM, Claus Ibsen wrote: > On Fri, Sep

Re: message not getting delivered

Yeah, there is still a lot of confusion. Unfortunately that page is bollocks and I'll have to get it cleaned up. Mark, I think you did the right thing actually, in a processor one should *not* modify the in, but produce an out, if needed. It's time to get that clarified! My $0.02, Hadrian On Oc

Re: Comma in email names

Yes, please create a jira. The problem is the simple parsing that doesn't account for commas (or semicolons) within quotes. We need to fix the parsing. Hadrian On Oct 5, 2010, at 4:27 AM, Claus Ibsen wrote: > Hi > > Yeah could be the alternative way of including a display name is not > support

[ANN] Apache Camel Survey (we need your help!)

With Apache Camel moving fast towards its 3.0 version we need to understand the areas where we need to focus our attention and efforts. We want to know you, our users, better and learn from your experiences and struggles using Camel so we can improve our project. Please fill out the short (25

Re: [ANN] Apache Camel Survey (we need your help!)

Ok, doing it now. On Oct 6, 2010, at 12:58 AM, Claus Ibsen wrote: > Hadrian > > I think you should post a news about this survey on the Apache Camel front > page. > > > On Tue, Oct 5, 2010 at 5:34 PM, Hadrian Zbarcea wrote: >> >> With Apache Camel movin

Re: Quartz Camel Spring Example?

Yes, it is fairly easy. You have to have a way though to communicate across instances in a cluster. So you will need a processor that sets the lock and a filter that will drop the quartz message (trigger event) if not the first. I hope this helps. Hadrian On Oct 6, 2010, at 8:57 AM, Russell, B

Re: Quartz Camel Spring Example?

nd setting up the quartz database > tables). > > Is this type of functionality not implemented yet in camel or do I need > to write the specific code to to this? Or am I missing something? > > Thanks for your help. > > > -Original Message- > From: Hadrian

Re: Camel Social component 'PoC' ready

Hi Bruno, I still didn't have a chance to look at it but I promise to do it this week. One question I have is if you are using opensocial for it or some other api? I am very curious to see if there's any oauth integration as well. This is more certainly a cool component which opens camel to a w

Re: The semantics of getIn and getOut (was: message not getting delivered)

which is not what I wanted. > > > On Mon, Oct 4, 2010 at 1:54 PM, Hadrian Zbarcea wrote: >> Yeah, there is still a lot of confusion. >> Unfortunately that page is bollocks and I'll have to get it cleaned up. >> Mark, I think you did the right thing actually, in a p

Re: Should we (could we?) make Exchanges serializable?

+1 fwiw, Hadrian On Oct 8, 2010, at 7:05 AM, Claus Ibsen wrote: > On Fri, Oct 8, 2010 at 12:21 PM, Ade wrote: >> >> I've never been a fan of Java serialization; however, I've been working with >> a Camel user who wants to be able to serialize an exchange and place the >> whole thing on a JMS qu

Re: Should we (could we?) make Exchanges serializable?

version of the > class to make Wicket really really happy. > That would help when sending the jpa event message through jms, > towards a jpa endpoint as well. > > Couldn't you at least make this class Serializable as it only contains > Strings and Date anyway? > > Regards &g

Re: The semantics of getIn and getOut (was: message not getting delivered)

Thanks Claus, will do. I think there's a lot to do to improve documentation and I want to make that one of my priorities. I hope the whole community will join :). Cheers, Hadrian On Oct 8, 2010, at 12:10 PM, Claus Ibsen wrote: > On Thu, Oct 7, 2010 at 3:51 PM, Hadrian Zbarcea wrot

Re: Should we (could we?) make Exchanges serializable?

Christian, That's the gist of it, yes. You have to decide if you want to marshal the properties as well. You are correct. The problem (stated another way) is that the exchange itself has no semantic outside of it's context, so what the holder does is to extract from the exchange the elements t

[REMINDER][ANN] Apache Camel Survey (we need your help!)

Many thanks to all who participated in the survey, we had great participation so far. For those who did not yet take the survey [1] please do so now, we want to hear your opinion! The Apache Camel PMC [1] http://s.apache.org/camel-survey On Oct 5, 2010, at 11:34 AM, Hadrian Zbarcea wrote

Re: XMPP pubsub

You could, but we cannot include it with a dependency on a snapshot. I am working on figuring out the best way to publish 3rd party releases in the central repo, so that we avoid such issues. It looks I also need to get in touch with the smack guys and see if they have any plans for new releases.

Re: XMPP pubsub

27;m willing to help. Hadrian On Oct 13, 2010, at 4:33 PM, Donald Whytock wrote: > Would they be the ones to supply osgi-ready bundles? Or could Camel > be bundled with an osgi'd version of the smack jars? > > Don > > On Wed, Oct 13, 2010 at 1:23 PM, Hadrian Zbarc

Re: TransformerProcessor doesn't deal with MEP, why? or a bug?

Does this [1] explain it? Hadrian [1] http://camelbot.blogspot.com/2010/10/should-you-getin-or-getout.html On Oct 13, 2010, at 11:51 PM, ext2 wrote: > The Transformer Processor always set Out Message as result and doesn't > care what MEP being;(At least until version camel 2.4.0, it being so,

Re: TransformerProcessor doesn't deal with MEP, why? or a bug?

Then there's something wrong with the aggregator, I'd say. The result of processing is always: out if present, otherwise in. Makes sense? I hope this helps, Hadrian On Oct 14, 2010, at 12:43 AM, ext2 wrote: > I still feel it's a bug; let's give a sample as following: > > > > >

Re: TransformerProcessor doesn't deal with MEP( Why we need InOnly?)

nOnly pattern? If > so, it's not worth. > > ========== > Hadrian Zbarcea wrote: >> Then there's something wrong with the aggregator, I'd say. >> The result of processing is always: out if present,

Re: Custom Router

Hi Sergey, Messages flow along a route that can be statically or dynamically configured. If I understand you correctly there are 2 things you could look at. One is the dynamic router [1] (and related routing slip [2]) that allows you to make decisions at runtime about how your messages flow. T

Re: Why the route's result is not correct?

Hi, I saw your previous mail, and from what you are saying the result seems to be incorrect. We are now trying to get the 2.5.0 release out. Will take a look as soon as I am done with the release. Thanks for the patience and for using camel, Hadrian On Oct 25, 2010, at 6:45 AM, ext2 wrote: >

Re: Abstracting Routes using Components

So the idea is to use route templates and in order to parameterized them use URIs the camel way. That's nice and consistent. Not sure though it a component is the best way to go. To me this is similar to another idea discussed a while ago, lightweight routes (sub-routes, routelets ?) that do not

Re: Abstracting Routes using Components

There are a few issues we need to sort out. One is that with something like this: > from("blackboxroute1://out")... You'd have to deal with naming. If everybody will define her "blackboxroute1" you'll have to deal with name clashes. You can do something like "route:blackboxroute1://out". Then the

Re: [ANN] Apache Camel Survey (we need your help!)

Thanks to all of you who took the survey. We had great participation and it is very helpful. For those of you who didn't take the survey yet still want to have your voice heard, the survey is still live until the end of this month (also known to some of you as Halloween). Results will be posted

Re: Endpoint construction

Hi Bruno, Your original question was: "Should I call a certain method in order to correctly build the Endpoint after setting the options ?". The answer to that is now. On your disagreement, what James meant (I think) is that we could for instance do a better job at resetting an endpoint url, b

Camel 2.5.0 released

The Apache Camel project [1] issued this week another minor release camel-2.5.0 [2]. We are extremely grateful to the community for the continued support and the contributions. The 2.5.0 release (see release notes for details [3]) includes approx 300 issues resolved (new features, improvements

Re: Camel 2.5.0 released

like that :) > > > > > On Mon, Nov 1, 2010 at 4:52 AM, Hadrian Zbarcea wrote: >> The Apache Camel project [1] issued this week another minor release >> camel-2.5.0 [2]. We are extremely grateful to the community for the >> continued support and the contrib

Re: Ambiguous method invocations in bean binding

It is a good improvement, +1 from me too. Christian, go for it! Hadrian On Nov 3, 2010, at 11:40 PM, Willem Jiang wrote: > It makes sense, +1 for the change. > > On 11/4/10 7:28 AM, Christian Müller wrote: >> Hello Rafal! >> >> Please provide more details like the Camel version you are using in

Re: OW2 JOnAS + Apache CAMEL integration version 1.5.5 is available

Thanks for the correction Norman. Personally I understand the LGPL analogy to free speech and beer like this: "You are free to speak as long as you pay for our beer". Nothing wrong with that though :). AL2 on the other hand I consider truly free. Enjoy using both projects, Hadrian On Nov 9, 201

Re: Wast performance? Instrument Interceptor is wrapped twice for each processor.

The InstrumentationProcessor is a delegate processor (aka interceptor) that allows you do do before and after processing. It is not really invoked twice (or I have to see a test case that does that, the unit tests in camel I am aware of don't). It is invoked once, takes a start timestamp, it del

Re: Wast performance? Instrument Interceptor is wrapped twice for each processor.

> > > > > But the trace result is : 2 of first bean, 2 of the "to" endpoint, > 2 of the second bean and 1 for route; > > -Origin - > Send

Re: [Serialization] CamelAuthentication is null

It is not normal, and reviewing the Camel code (2.6-SNAPSHOT, not the 2.4.0.fuse-00-00 you're using), I don't see where this could have happened. What do you use for authentication, spring-security? Is there a test case? Thanks Hadrian On Dec 3, 2010, at 9:23 AM, Olivier.Roger wrote: > > Hel

[ANNOUNCE] Camel 1.6.4 released!

The Apache Camel project [1] issued this week a new patch release camel-1.6.4 [2]. We are extremely grateful to the community for the continued support and the contributions. Development on the camel-1.x branch slowed down this year. The 1.6.4 release (see release notes for details [3]) includ

Re:

If you don't have the Camel in Action book (please don't interpret the previous answer as a request to buy the book) you can find more details about exception handling here: http://camel.apache.org/exception-clause.html. If you are curious to look at the code, look at how CatchProcessor.handles(

Re: Camel routes as graphs

Yes, routes in camel are directed graphs, trees most of the time. Not sure what you saw that indicates otherwise. Cheers, Hadrian On Jan 20, 2011, at 3:36 PM, unmarshall wrote: > > Hi, > > Are routes in camel represented as graphs? When i see the class > DefaultCamelContext then i do not fin

Re: Camel routes as graphs

Not sure I follow you. Are you saying that camel routes are not graphs, or you want us to confirm that it is, or you see an implementation problem? More comments inline. Hadrian On Jan 21, 2011, at 1:07 AM, unmarshall wrote: > > Hi Hadrian, > > Considering that a route is represented as a dir

Re: Character Encoding problem

Salut, We may if you give us more info about your route, configuration and a sample message. Putting together a small unit test would be ideal. Cheers, Hadrian On Jan 24, 2011, at 10:52 AM, Laurentiu Trica wrote: > Hi, > > I have the following situation: I do a unedifact D96A conversion in >

Re: Issues running Apache Camel Examples

Matt, could you please move this discussion to the fusesource forums? [1] This mailing list has a lot of traffic as it is and should be used for issues/questions related to the Apache distro, not a vendor's. Thanks, Hadrian [1] http://fusesource.com/forums/index.jspa On Jan 27, 2011, at 9:01 A

Re: Issues running Apache Camel Examples

Claus, is there a problem with the Apache Camel 2.6.0 release? Hadrian On Jan 27, 2011, at 9:36 AM, Claus Ibsen wrote: > Hi > > Yeah we should take this conversation at FuseSource. > > Just one last remark though. > > The problem you have is only in the latest 2.6.0 release. > > I have creat

Re: Issues running Apache Camel Examples

Perfect, thanks. Hadrian On Jan 27, 2011, at 11:23 AM, Claus Ibsen wrote: > On Thu, Jan 27, 2011 at 5:16 PM, Hadrian Zbarcea wrote: >> Claus, is there a problem with the Apache Camel 2.6.0 release? >> Hadrian >> > > No the Apache version is fine. > > Its t

Re: Timers stop firing after certain unpredictable interval

Can you reproduce this consistently? Hadrian On Feb 4, 2011, at 7:15 PM, s2010in wrote: > > Still not sure where the bug is, Used Camel timer, then Quartz timer, and > finally created a separate TimerTask with java.util.Timer > > All of them do same, to get around have created my own daemon th

Re: ETL: how to monitor the end of processing ?

Hi Xavier, I suspect camel did the right thing. Camel waits for in-flight messages to complete [1]. I don't know how you set up your routes, but I suspect that you stop the consumer in one of the steps while there are still messages to consume. Since the consumer didn't grab them yet, and hence

Re: Event driven FTP consumer?

Not sure if I didn't misread your request. I believe that what you need is actually a file/ftp producer and then you would do: > from("servlet://my/web/service").to("ftp://f...@bar.com/baz";) See: https://issues.apache.org/jira/browse/CAMEL-3397 Hadrian On Feb 8, 2011, at 12:27 PM, Richard K

Re: Event driven FTP consumer?

Richard, the way you phrased it, having an event driven consumer, effectively means having camel act as an FTP server (or a proxy for an ftp server). That could be done with camel-mina, I am pretty sure, but I don't see the need. More work and no gain really. Cheers, Hadrian On Feb 8, 2011, at

Re: How widely used in Camel?

I doubt you'll get a lot of feedback, most of the commercial companies are sworn to secrecy. We encourage users who have a story to tell to either add (or submit on the list giving us permission to add) their story on the camel site [1]. There were questions recently questions on the mailing lis

Re: From the validity of using Camel+Bindy as a super lightweight ETL tool to evolving it to support a data management system?

Hi Grant, Quite a few questions here. Thanks for taking the time and evaluating Apache Camel. Yes, Camel is ideal for such scenarios, because: 1. It's specifically designed for that, systems integration. 2. It's simple to use and requires minimal coding 3. It supports out of the box a large num

Re: Consumer Multiple Messages

Hi Roshan, Do you mean N internal Camel exchanges, or N replies to the 1 caller request? The former is relatively easy to do. The second is a bit tricky with of the request/reply model, but if your protocol is async it could be done. See for instance the mail or jms components and the role of r

Re: Producer Multiple Messages

You are probably looking for a splitter or a loop. Most likely splitter/aggregator. Hadrian On Feb 21, 2011, at 12:17 PM, Roshan A. Punnoose wrote: > Sorry got the terminology incorrect, I meant Producer instead of Consumer. > > I want to be able to do something like the following: > > from.

Re: Producer Multiple Messages

gt; Or would it only work if the splitter is defined in the route after the > to("mycomp..") statement? > > Roshan > ________ > From: Hadrian Zbarcea [hzbar...@gmail.com] > Sent: Monday, February 21, 2011 12:27 PM > To: users@camel.apache

Re: Can Camel be used to define Business Process Routes ?

Hi Vishal, These are valid patterns and Camel is used like that in productions by many users already. You can think of Camel as a lightweight BPEL if you want. I'd encourage you to confidently go ahead and if you have any questions in the future post them here. Cheers, Hadrian On Feb 24, 2011

Re: building the trunk fails for me

I started a new build (clean svn checkout), and I got another failure, probably timing related. Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 6.112 sec <<< FAILURE! testShutdownCompleteAllTasks(org.apache.camel.component.seda.FileSedaShutdownCompleteAllTasksTest) Time elapsed

Re: Camel Mail issue with unsupported charset

If Camel encounters an exception it will invoke on the error handler which by default in 1.x tries to reprocess. If all that fails, the message remains unprocessed. What you need is to handle the exception yourself and process it any way you want, either delete it or move it to some other fol

Re: synchronization between separate from() paths

You should use camel-bam for such requirements. Hadrian On Aug 7, 2009, at 9:05 AM, arhan wrote: I have 2 routes defined as follows: configure(){ from("sourceA").to("processorA"); from("sourceB").to("processorB"); } sourceB content is produced by processorA. I have now a requirement that

Fwd: Sign up for ApacheCon US by 14 August and save up to $500!

This promises to be a huge anniversary event. The Early Bird registration ends next week, if you plan to attend, go sign up now. See you there :) Hadrian Begin forwarded message: From: Sally Khudairi Date: August 7, 2009 9:55:10 PM EDT To: annou...@apache.org, annou...@apachecon.com Subject

Re: Creating a full Camel route with scripts

This question sounds like one of those Radio Yerevan jokes [1] :) Hadrian [1] http://en.wikipedia.org/wiki/Radio_Yerevan On Aug 12, 2009, at 12:29 PM, S. Ali Tokmen wrote: Hello Is it possible to use Camel's Groovy scripting capabilities for creating a route? Cheers -- S. Ali Tokmen s

Re: Bug in documentation: methodName should be method in bean: uri

Hi Olaf, Because we rely on people like you to spot such issues and alert us. Many thanks for pointing it out. The http://camel.apache.org/ bean.html does document the correct syntax. Fixed, thanks, Hadrian On Aug 19, 2009, at 6:01 PM, Olaf Bergner wrote: Using Camel 2.0 M3 and follow

[ANN] Apache Camel 2.0.0 Released

The Camel riders are pleased to introduce the Apache Camel 2.0.0 release [1]. This is a major overhaul of Camel that took more than a year of efforts and is coming with about 760 issues resolved. We are grateful to the entire community for its involvement. Your hard work and constant atten

Re: 2.0.0 specific version of the camel-spring.xsd?

Actually the scripts require quite a bit of rework after the nexus move. I will take care of the schema and the scripts, thanks for pointing it out. Hadrian On Aug 26, 2009, at 9:08 PM, Willem Jiang wrote: I think it is caused by we switch to use maven nexus for the release work which

Re: Garceful shutdown bug in 2.0M3?

I think there was an issue about daemon threads that sounded quite similar. Hadrian On Aug 27, 2009, at 3:52 AM, Claus Ibsen wrote: On Wed, Aug 26, 2009 at 5:08 PM, dadoc wrote: Claus Ibsen-2 wrote: If you do it by pure java, eg not letting spring handle the lifecycle you have contro

Re: endpoint not found after 2.0.0 upgrade

They are copied on the minotaur, they should propagate shortly. I'll keep an eye on it. Hadrian On Aug 27, 2009, at 2:03 PM, Claus Ibsen wrote: Hi Yeah its because of https://issues.apache.org/activemq/browse/CAMEL-1947 The 2.0 xsd files have not been published to apache maven servers.

Re: endpoint not found after 2.0.0 upgrade

The xsd files are available on the camel site: http://camel.apache.org/schema/ Please let us know if you still encounter issues. Thanks, Hadrian On Aug 27, 2009, at 2:03 PM, Claus Ibsen wrote: Hi Yeah its because of https://issues.apache.org/activemq/browse/CAMEL-1947 The 2.0 xsd files have

Re: endpoint not found after 2.0.0 upgrade

Rental: http://tahoe.baselogic.com --- On Thu, Aug 27, 2009 at 1:37 PM, Hadrian Zbarcea wrote: The xsd files are available on the camel site: http://camel.apache.org/schema/ Please let us know if you still encounter issues. Thanks, Hadrian On Aug 27, 2009, at 2:03 PM, Claus Ibsen wrot

Re: [ANN] Apache Camel 2.0.0 Released

I am looking into that. Hadrian On Aug 28, 2009, at 9:28 AM, frapien wrote: Claus Ibsen-2 wrote: On Wed, Aug 26, 2009 at 2:43 PM, S. Ali Tokmen> wrote: The PDF Manual links are also broken http://camel.apache.org/manual.html Thanks Frank -- View this message in context: http://www.n

Re: Can't download or build Camel 2.0

This link [1] points you to a page that shows available mirrors. You can navigate to one of them and download the binaries. Source availability is an issue I am working on correcting. The sources used for the 2.0.0 release are also tagged [2] so you can use your subversion client of choice,

Re: Can't download or build Camel 2.0

rian On Sep 16, 2009, at 2:57 AM, Willem Jiang wrote: Hi Hadrian, I noticed that current trunk's apache-camel assembly-src profile[1] is commented out. Do you have any idea about it? [1] https://svn.apache.org/repos/asf/camel/trunk/apache-camel/pom.xml Willem Hadrian Zbarcea wrote: This

Re: Zip format problem

Hi Vladimir, Thanks for pointing this out. Would you care to submit a patch for this? On the custom data format topic, of course you can. You'd have to write your own component with your data format code (class extending org.apache.camel.spi.DataFormat). You can find a more isolated exam

Re: Zip format problem

What about unpack in a temp dir and after unpacking is complete mv the temp dir to the destination (tempCacheFolder in this case)? My $0.02, Hadrian On Oct 5, 2009, at 6:03 PM, Christian Schneider wrote: Hi Vladimir, looks almost good. The problem is though that the second route already

Re: Presenting Camel Twitter at ApacheCon

I'll be there, and most curious to see it. If you don't bump to me in the hallways send me an email and we'll setup something. Cheers, Hadrian On Oct 27, 2009, at 8:24 AM, Bruno Borges wrote: Hi everyone. I'll be attending ApacheCon US (SF, CA) this

[ANNOUNCE] Apache Camel 1.6.2 Release

Welcome to a new maintenance release of Apache Camel. The camel-1.6.2 release comes with approx 101 issues resolved (new features, improvements and bug fixes such as...) • Fixes for OSGi bundles. • Support multiple camel versions in OSGi containers. • Fixed Karaf fea

Re: No camel-clock? How does one test?

There are two abstractions of a clock. One is the camel-timer, the other one camel-quartz. The model is not as sophisticated as the Drools one, and I wonder if it should be. It sounds interesting though. If you host camel in servicemix (which we recommend) there is a servicemix-drools comp

[ANNOUNCE] Apache Camel 2.1.0 Release

After a bit over three months of hard work we are pleased to introduce the Apache Camel 2.1.0 Release [1]. This is another major effort featuring an impressive 303 issues resolved. The Camel community is growing at a faster pace and we see a lot of involvement and contributions. The featu

Re: Call local application

You may just want to use a bean for that. http://camel.apache.org/bean-integration.html Hadrian On Dec 10, 2009, at 5:12 AM, SwenVogel wrote: Yes that's right, i just thought perhaps there is already some kind of "camel - way" to do this. So, i will write a consumer component that is capa

Re: The latest camel java archetype (2.1.0) is not working correctly

Hi Ryadh, Thanks for pointing that out. Yes, a jira should be created, please mark it as a bug. If you know what the cause is and could submit a patch, even better. Thanks, Hadrian On Dec 23, 2009, at 1:29 PM, Ryadh Amar wrote: Hello Community, When I run the following mvn archetype:g

Re: 2.1.0 Manual?

Yes, there was a problem with the generation of the pdf. I will upload it manually. Thanks Hadrian On Jan 7, 2010, at 3:26 PM, /U wrote: Is the manual for 2.1.0 available? The link http://camel.apache.org/manual/camel-manual-2.1-SNAPSHOT.pdf is broken. Regards, /U -- View this message

[ANNOUNCE] Apache Camel 2.2.0 Release

After a bit over two months of hard work we are pleased to introduce the Apache Camel [1] 2.2.0 Release [2]. Many thanks and our gratitude to all the contributors who made this release possible. This Valentine's Day edition of Apache Camel was officially released on Feb 14th. During the past day

Re: Quartz confusion

Yes, that is the camel jira, also linked from the "Contributing" page [1] (issue tracker) on the official site. To be able to create an issue you need to have an account and log in. To get an account you need to file an icla (individual Contributor License Agreement) with apache. You can find m

Re: Windows build completely working now

I would also like to see a more aggressive testing strategy, probably using 'once' instead of 'pertest'. The only major offender is indeed jmx which does not cleanup properly on shutdown, you are correct. We should definitely look into the jmx cleanup, because we cannot always assume the lifeti

  1   2   3   >