On Thu, Jul 9, 2009 at 8:43 AM, alloyer wrote:
>
>
> all right. I saw the deadLetter DSL have used "direct://start".
> Will this enforcemnt be applied before long?
Its in there now. So yes it will be standard in Camel 2.0.
This is the ticket about it
http://issues.apache.org/activemq/browse/CAMEL-
all right. I saw the deadLetter DSL have used "direct://start".
Will this enforcemnt be applied before long?
Claus Ibsen-2 wrote:
>
> On Thu, Jul 9, 2009 at 7:47 AM, alloyer wrote:
>>
>> Have the endpoint URIs been changed to "direct://start" from
>> "direct:start" ?
>> I haven't updated my c
On Thu, Jul 9, 2009 at 7:47 AM, alloyer wrote:
>
> Have the endpoint URIs been changed to "direct://start" from "direct:start" ?
> I haven't updated my camel-core source for several days. Maybe I have to
> update it now.
Yes the endpoint registry in Camel will enforce a // after the scheme.
This al
Have the endpoint URIs been changed to "direct://start" from "direct:start" ?
I haven't updated my camel-core source for several days. Maybe I have to
update it now.
JIRA j...@apache.org wrote:
>
> groovy renderer
> ---
>
> Key: CAMEL-1392
> URL:
Hi,
Comments inline.
Hadrian
On Jul 9, 2009, at 12:54 AM, Claus Ibsen wrote:
On Wed, Jul 8, 2009 at 9:52 PM, Hadrian Zbarcea
wrote:
Hi,
As we approach the 2.0, there is one more hanging issue I would like
addressed, if possible. It's the thorny issue of Faults and
Exceptions that
start
On Wed, Jul 8, 2009 at 9:52 PM, Hadrian Zbarcea wrote:
> Hi,
>
> As we approach the 2.0, there is one more hanging issue I would like
> addressed, if possible. It's the thorny issue of Faults and Exceptions that
> started in
> http://issues.apache.org/activemq/browse/CAMEL-316 (see also the relate
[
https://issues.apache.org/activemq/browse/CAMEL-1789?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang updated CAMEL-1789:
Fix Version/s: (was: 2.1.0)
2.0.0
Summary: Let the Camel Route
[
https://issues.apache.org/activemq/browse/CAMEL-1813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-1813.
-
Resolution: Fixed
trunk
http://svn.apache.org/viewvc?rev=792381&view=rev
> HttpProducer does
On Thu, Jul 9, 2009 at 12:14 AM, Hadrian Zbarcea wrote:
> Currently the Exchange has the following 4 apis that I think can be
> consolidated into 1 or 2 methods:
>
> Exchange newInstance();
+1 to remove
> Exchange copy();
+1 to keep
> Exchange newCopy(boolean handoverOnCompletion);
-1 = m
Remove debug interceptor as it was newer implemented
Key: CAMEL-1815
URL: https://issues.apache.org/activemq/browse/CAMEL-1815
Project: Apache Camel
Issue Type: Task
Components:
Missing debug.xml in 2.0-M2
---
Key: CAMEL-1814
URL: https://issues.apache.org/activemq/browse/CAMEL-1814
Project: Apache Camel
Issue Type: Bug
Components: camel-core
Affects Versions: 2.0-M2
En
HttpProducer doesn't copy the in message header to out message
--
Key: CAMEL-1813
URL: https://issues.apache.org/activemq/browse/CAMEL-1813
Project: Apache Camel
Issue Type: Bug
Currently the Exchange has the following 4 apis that I think can be
consolidated into 1 or 2 methods:
Exchange newInstance();
Exchange copy();
Exchange newCopy(boolean handoverOnCompletion);
void copyFrom(Exchange source);
I think both copyFrom(Exchange) and newInstance() could eas
I hope I didn't jump the gun here, but given the consenus:
https://issues.apache.org/activemq/browse/CAMEL-1812
+1
Hadrian
On Jul 7, 2009, at 2:54 AM, Claus Ibsen wrote:
Hi
I want to propose that we remove the @author tags in the source code
for Apache Camel.
We only have about 20 files with
[
https://issues.apache.org/activemq/browse/CAMEL-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52752#action_52752
]
Hadrian Zbarcea edited comment on CAMEL-1812 at 7/8/09 2:47 PM:
---
[
https://issues.apache.org/activemq/browse/CAMEL-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea resolved CAMEL-1812.
Resolution: Fixed
> Remove @author tags in java code
>
[
https://issues.apache.org/activemq/browse/CAMEL-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hadrian Zbarcea updated CAMEL-1812:
---
Fix Version/s: 2.0.0
1.6.2
> Remove @author tags in java code
> --
[
https://issues.apache.org/activemq/browse/CAMEL-1812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=52752#action_52752
]
Hadrian Zbarcea commented on CAMEL-1812:
r792319 (trunk)
> Remove @author tags in ja
Remove @author tags in java code
Key: CAMEL-1812
URL: https://issues.apache.org/activemq/browse/CAMEL-1812
Project: Apache Camel
Issue Type: Task
Affects Versions: 2.0-M2, 1.6.1
Reporter: Hadr
Hi,
As we approach the 2.0, there is one more hanging issue I would like
addressed, if possible. It's the thorny issue of Faults and
Exceptions that started in
http://issues.apache.org/activemq/browse/CAMEL-316 (see also the
related nabble thread linked in the issue description).
I am le
[
https://issues.apache.org/activemq/browse/CAMEL-1811?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen resolved CAMEL-1811.
Resolution: Fixed
trunk: 792166.
> SpringInjector - Support letting spring do constructor IoC
[
https://issues.apache.org/activemq/browse/CAMEL-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang resolved CAMEL-1810.
-
Resolution: Fixed
Fix Version/s: 2.0.0
Applied patch with thanks to Seumas, also fixed
SpringInjector - Support letting spring do constructor IoC
--
Key: CAMEL-1811
URL: https://issues.apache.org/activemq/browse/CAMEL-1811
Project: Apache Camel
Issue Type: Improvement
[
https://issues.apache.org/activemq/browse/CAMEL-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Willem Jiang reassigned CAMEL-1810:
---
Assignee: Willem Jiang
> Using camel-cxf component requires service class even in PAYLOAD
Yeah, that could be done pretty easily. The ability to convert Groovy text
into RouteDefintions and vice versa is in Xueqiangs latest patch. Would just
need a new interface and some refactoring, etc.
Still on the issue of predicates needing language specific names, I think my
suggestion before wou
[
https://issues.apache.org/activemq/browse/CAMEL-1810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Seumas Soltysik updated CAMEL-1810:
---
Attachment: camel-1810.patch
Attaching patch for 1810.
> Using camel-cxf component requi
[
https://issues.apache.org/activemq/browse/CAMEL-1392?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xueqiang Mi updated CAMEL-1392:
---
Attachment: camel-web-20090708.patch
Add a bundle of test cases to demonstrate which DSL have
Using camel-cxf component requires service class even in PAYLOAD or MESSAGE mode
Key: CAMEL-1810
URL: https://issues.apache.org/activemq/browse/CAMEL-1810
Project: Apache
2009/7/8 Gert Vanthienen :
> L.S.,
>
> I wonder if we should not make this a bit more pluggable. It might
> make sense to be able to represent the same xxxDefinition in Groovy
> DSL, Java DSL, XML, Scala, ... so people can see the same route
> definition in multiple languages. Perhaps we can (ab)
Neato idea but probably a bit overkill? Also, when adding say Groovy
specific predicate text to the metadata, we would still need an identifier
for the anonymous class to look up in the registry (otherwise we'd have to
add the Groovy specific metadata in camel-core at creation time). I still
think
On Wed, Jul 8, 2009 at 2:11 PM, Jon Anstey wrote:
> That does make a lot of sense :) Though, just to be clear, all
> Groovy-specific work done up until now has been in separate classes and not
> part of the core. So its not affecting any future Scala renderer. The
> predicate builder stuff we're di
That does make a lot of sense :) Though, just to be clear, all
Groovy-specific work done up until now has been in separate classes and not
part of the core. So its not affecting any future Scala renderer. The
predicate builder stuff we're discussing here will so yeah, we need to fix
it... since all
Usually @author tag shows the class creator - not the actual
maintainer of the class. Of course one person can have both roles, but
in general I believe it is useless for Camel. My +1
Roman
2009/7/7 Claus Ibsen :
> Hi
>
> I want to propose that we remove the @author tags in the source code
> for
+1
On Tue, Jul 7, 2009 at 4:24 AM, Claus Ibsen wrote:
> Hi
>
> I want to propose that we remove the @author tags in the source code
> for Apache Camel.
> We only have about 20 files with author tags and for 2 persons.
>
> As I understand its not common at Apache to have @author tags in the
> sou
L.S.,
I wonder if we should not make this a bit more pluggable. It might
make sense to be able to represent the same xxxDefinition in Groovy
DSL, Java DSL, XML, Scala, ... so people can see the same route
definition in multiple languages. Perhaps we can (ab)use the type
converter thing for this,
+1
Charles Moulliard
Senior Enterprise Architect
Apache Camel Committer
*
blog : http://cmoulliard.blogspot.com
On Tue, Jul 7, 2009 at 8:54 AM, Claus Ibsen wrote:
> Hi
>
> I want to propose that we remove the @author tags in the source code
> for Apache Camel.
> We
Not that I'm an active contributor, but I find @author tags only
annoying +1 to removing them.
david jencks
On Jul 6, 2009, at 11:54 PM, Claus Ibsen wrote:
Hi
I want to propose that we remove the @author tags in the source code
for Apache Camel.
We only have about 20 files with author
2009/7/7 Bruce Snyder :
> On Tue, Jul 7, 2009 at 12:54 AM, Claus Ibsen wrote:
>> Hi
>>
>> I want to propose that we remove the @author tags in the source code
>> for Apache Camel.
>> We only have about 20 files with author tags and for 2 persons.
>>
>> As I understand its not common at Apache to ha
38 matches
Mail list logo
