[jira] Resolved: (CAMEL-1016) -a option in camel-spring Main class stopped working (caused by changes in camel-core)

["Jonathan Anstey (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/activemq/browse/CAMEL-1016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Anstey resolved CAMEL-1016.
------------------------------------

         Assignee: Jonathan Anstey
    Fix Version/s: 1.5.0
       Resolution: Fixed

> -a option in camel-spring Main class stopped working (caused by changes in camel-core)
> --------------------------------------------------------------------------------------
>
>                 Key: CAMEL-1016
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1016
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-core
>            Reporter: Bela Vizy
>            Assignee: Jonathan Anstey
>             Fix For: 1.5.0
>
>
> In the org.apache.camel.util.MainSupport class, the option "-ad" (aggregate-dot) conflicts with the option "-a" (applicationContext) defined in org.apache.camel.spring.Main. Both start with "a". See MainSupport.java:437: fullName.startsWith(arg) yields true with -a and aggregate-dot.
> I'm not sure if this is camel-spring or camel-core issue, it depends what was created first. It was working before so I guess the camel-core brought it in recently.
> One of the options should be renamed. I would rename the -a to -ac in the camel-spring Main class. So the apps that used -a would barf on the non-existing option so people will know what's going on. What happens now is it just silently ignores your spring config file. Let me know if you need a patch for the change.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.