[jira] [Updated] (CAMEL-4028) Simple language - Allow to configure prefix and suffix tokens
[
https://issues.apache.org/jira/browse/CAMEL-4028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Taariq Levack updated CAMEL-4028:
-
Attachment:
CAMEL-4028_Simple_language_-_Allow_to_configure_prefix_and_suffix_tokens_4.patch
This patch includes the global config using java and spring, but not yet the
namespace and the first groovy test I'd still be grateful for.
How do I handle the camel-spring for language?
The other JAXB changes I made work fine except for this, and I notice there's
already a 'language' in the model, see LanguageExpression, so I hope there
won't be a clash. Should I use language here as well, or what else?
I have temporarily named the new one language2, and I assumed I should add this
list of LanguageDefinition to CamelContextFactoryBean, but as you'll see after
building camel-core, you still cannot use language2 as I tried in
SimpleLanguageGlobalCustomTokensTest.
Thanks for the patience, I'm playing with many new toys for this ticket and
it's great and everything, but with current timing I'm hoping it's a few minute
job for someone to point me in the right direction while I dig around here and
there.
> Simple language - Allow to configure prefix and suffix tokens
> -
>
> Key: CAMEL-4028
> URL: https://issues.apache.org/jira/browse/CAMEL-4028
> Project: Camel
> Issue Type: Improvement
> Components: camel-core
>Affects Versions: 2.7.0
>Reporter: Claus Ibsen
>Priority: Minor
> Fix For: 2.9.0, Future
>
> Attachments:
> CAMEL-4028_Simple_language_-_Allow_to_configure_prefix_and_suffix_tokens1.patch,
>
> CAMEL-4028_Simple_language_-_Allow_to_configure_prefix_and_suffix_tokens_4.patch
>
>
> The simple language uses ${ } tokens by default. However groovy uses those
> for its GString. So we have a clash. Even if you use $simple{ } instead in
> Groovy then you have a clash.
> So we should add support for configuring the tokens so you can remedy the
> GString clash in Groovy.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4359) Exception thrown during JAXB marshalling will cause SedaConsumer to break
[ https://issues.apache.org/jira/browse/CAMEL-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4359. Resolution: Fixed Fix Version/s: 2.9.0 2.8.1 Thanks for the unit test. > Exception thrown during JAXB marshalling will cause SedaConsumer to break > - > > Key: CAMEL-4359 > URL: https://issues.apache.org/jira/browse/CAMEL-4359 > Project: Camel > Issue Type: Bug > Components: camel-jaxb >Affects Versions: 2.8.0 >Reporter: Dragisa Krsmanovic >Assignee: Claus Ibsen > Fix For: 2.8.1, 2.9.0 > > Attachments: CAMEL-4359.patch > > > Error handler tries to add message body to error log. If it tries to use JAXB > type converter and marshalling throws exception, the exception is thrown all > the way back to SedaConsumer. SedaConsumer will then retry to create error > message in the same way until the point where exception is not handled any > more and SedaConsumer loop breaks off. > One single bad message can stop Seda route. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (CAMEL-4359) Exception thrown during JAXB marshalling will cause SedaConsumer to break
[ https://issues.apache.org/jira/browse/CAMEL-4359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen reassigned CAMEL-4359: -- Assignee: Claus Ibsen > Exception thrown during JAXB marshalling will cause SedaConsumer to break > - > > Key: CAMEL-4359 > URL: https://issues.apache.org/jira/browse/CAMEL-4359 > Project: Camel > Issue Type: Bug > Components: camel-jaxb >Affects Versions: 2.8.0 >Reporter: Dragisa Krsmanovic >Assignee: Claus Ibsen > Attachments: CAMEL-4359.patch > > > Error handler tries to add message body to error log. If it tries to use JAXB > type converter and marshalling throws exception, the exception is thrown all > the way back to SedaConsumer. SedaConsumer will then retry to create error > message in the same way until the point where exception is not handled any > more and SedaConsumer loop breaks off. > One single bad message can stop Seda route. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [HEADS UP] Moving org.apache.camel.Main to org.apache.camel.main.Main
On Fri, Aug 19, 2011 at 4:54 PM, Christian Schneider wrote: > We could do something like that but the problem is the scope and dependency > rules for this new package. > Main needs access to all inner details of camel. So you only would like to > put classes in that package that also need such details. On the other hand > this package should > be accessed by nothing else as it would easily create tangles over most of > camel. > I guess main is a corner case and moving it to .main could make sense in that case. > For example the ServiceSupport class should not go in the same package as > Main as ServiceSupport will be needed by many other classes. > > Christian > > > Am 19.08.2011 16:43, schrieb Claus Ibsen: >> >> I am not sure moving Main to a main package is a good idea. >> As you would lock yourself into only having the Main class there. >> >> What about adding a org.apache.camel.support package. >> >> And then have more commonly used Camel classes by end users in there. >> Such as the Main class. >> But by naming it support we give us legroom to put in other useful >> classes. >> >> >> > > -- > -- > Christian Schneider > http://www.liquid-reality.de > > Open Source Architect > Talend Application Integration Division http://www.talend.com > > -- 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/
[jira] [Updated] (CAMEL-4360) Camel test - Debugger should be explicit enabled if end user want to leverage it
[ https://issues.apache.org/jira/browse/CAMEL-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen updated CAMEL-4360: --- Comment: was deleted (was: Need to update wiki page and release notes. cwiki is not responding currently.) > Camel test - Debugger should be explicit enabled if end user want to leverage > it > > > Key: CAMEL-4360 > URL: https://issues.apache.org/jira/browse/CAMEL-4360 > Project: Camel > Issue Type: Improvement > Components: camel-test >Affects Versions: 2.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.9.0 > > > The debugger adds a little overhead and silently enables tracer as well. We > should have the end user to explicit enable the debugger if he need to use it > from his unit tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CAMEL-4360) Camel test - Debugger should be explicit enabled if end user want to leverage it
[ https://issues.apache.org/jira/browse/CAMEL-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Claus Ibsen resolved CAMEL-4360. Resolution: Fixed > Camel test - Debugger should be explicit enabled if end user want to leverage > it > > > Key: CAMEL-4360 > URL: https://issues.apache.org/jira/browse/CAMEL-4360 > Project: Camel > Issue Type: Improvement > Components: camel-test >Affects Versions: 2.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.9.0 > > > The debugger adds a little overhead and silently enables tracer as well. We > should have the end user to explicit enable the debugger if he need to use it > from his unit tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CAMEL-4360) Camel test - Debugger should be explicit enabled if end user want to leverage it
[ https://issues.apache.org/jira/browse/CAMEL-4360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13088162#comment-13088162 ] Claus Ibsen commented on CAMEL-4360: Need to update wiki page and release notes. cwiki is not responding currently. > Camel test - Debugger should be explicit enabled if end user want to leverage > it > > > Key: CAMEL-4360 > URL: https://issues.apache.org/jira/browse/CAMEL-4360 > Project: Camel > Issue Type: Improvement > Components: camel-test >Affects Versions: 2.8.0 >Reporter: Claus Ibsen >Assignee: Claus Ibsen >Priority: Minor > Fix For: 2.9.0 > > > The debugger adds a little overhead and silently enables tracer as well. We > should have the end user to explicit enable the debugger if he need to use it > from his unit tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CAMEL-4360) Camel test - Debugger should be explicit enabled if end user want to leverage it
Camel test - Debugger should be explicit enabled if end user want to leverage it Key: CAMEL-4360 URL: https://issues.apache.org/jira/browse/CAMEL-4360 Project: Camel Issue Type: Improvement Components: camel-test Affects Versions: 2.8.0 Reporter: Claus Ibsen Assignee: Claus Ibsen Priority: Minor Fix For: 2.9.0 The debugger adds a little overhead and silently enables tracer as well. We should have the end user to explicit enable the debugger if he need to use it from his unit tests. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira
