[jira] Resolved: (CAMEL-1301) NPE in FactoryFinder.findClass when context classloader is null

2009-01-30 Thread Claus Ibsen (JIRA)
[ https://issues.apache.org/activemq/browse/CAMEL-1301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-1301. Resolution: Fixed Fix Version/s: 2.0.0 1.5.1 NPE in

Re: [HEADS UP] - File component changes in Camel 2.0

2009-01-30 Thread Jon Anstey
Yeah, great work on all the improvements to the file component Claus. I think it will warrant a blog post of its own when Camel 2.0 comes out :) Not sure about this suggestion though... I kinda like having defaults in place so you don't always have to provide configuration. Like, having a default

Re: [HEADS UP] - File component changes in Camel 2.0

2009-01-30 Thread James Strachan
So long as files are written in some directory and they are unique and preserve order - does it matter if they are generated (from the message ID say) or the user explicitly gives some name? Like Jon I'd be tempted ot leave the default behaviour? 2009/1/30 Claus Ibsen claus.ib...@gmail.com: Hi

Re: [jira] Commented: (CAMEL-1302) Documentation - Add camel-bindy documentation

2009-01-30 Thread William Tam
BTW, I am curious about the name bindy. What does it mean? On Fri, Jan 30, 2009 at 1:28 AM, Claus Ibsen (JIRA) j...@apache.org wrote: [

Re: [HEADS UP] - File component changes in Camel 2.0

2009-01-30 Thread Aaron Crickenberger
I would hesitate if only because requiring a particular header seems off, are there other components that do the same? I haven't looked much at Camel 2.0's code, but it looks like camel-1.x's file component's expression property could support both scenarios. Use a default ${id} expression, but

[jira] Commented: (CAMEL-1299) Property language just as the Header language

2009-01-30 Thread Jonathan Anstey (JIRA)
[ https://issues.apache.org/activemq/browse/CAMEL-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49059#action_49059 ] Jonathan Anstey commented on CAMEL-1299: Put in support for this in revs 739340,

[jira] Commented: (CAMEL-1299) Property language just as the Header language

2009-01-30 Thread Jonathan Anstey (JIRA)
[ https://issues.apache.org/activemq/browse/CAMEL-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=49060#action_49060 ] Jonathan Anstey commented on CAMEL-1299: Wiki docs here

[jira] Resolved: (CAMEL-1299) Property language just as the Header language

2009-01-30 Thread Jonathan Anstey (JIRA)
[ https://issues.apache.org/activemq/browse/CAMEL-1299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Anstey resolved CAMEL-1299. Resolution: Fixed Fix Version/s: 2.0.0 Property language just as the Header

RE: Components setting data on OUT

2009-01-30 Thread Andi Abes
Took a while, and Roman I think you made great points. I think that throughout that thread there seems to have been a bit of confusing use of terms For example, the bit below: JBI, WSDL and WS stacks like CXF / JAX-WS support the idea of IN, OUT, FAULT messages. So its mostly there to

RE: Components setting data on OUT

2009-01-30 Thread Andi Abes
After a quick chat with William a quick clarification: The important point here is not how many messages are carried in the exchangebut rather how is the message to operate on is selected. Inspecting org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(Message) in CXF, which is more or