[jira] Commented: (CAMEL-1224) BeanDefinitionParser - SPR-4599 is fixed

["James Strachan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/activemq/browse/CAMEL-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48458#action_48458 ] 

James Strachan commented on CAMEL-1224:
---------------------------------------

Loads of folks seem to have 2.0.x or 2.5.x of spring - so I'd be nervous zapping that code for a while.

Maybe at some point we can depend on (say) 3.0 of spring in which case we can zap the code?

I think we should maybe push this issue back until some point when we can depend on a fairly high version of spring as being the base - e.g. whenever we demand 3.0 or something? Or maybe push back a few more versions or something?

Its really a non essential change - more a case of retiring custom patches

> BeanDefinitionParser - SPR-4599 is fixed
> ----------------------------------------
>
>                 Key: CAMEL-1224
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-1224
>             Project: Apache Camel
>          Issue Type: Task
>          Components: camel-spring
>            Reporter: Claus Ibsen
>            Assignee: James Strachan
>             Fix For: Future
>
>
> This one is for James
> camel-spring class BeanDefinitionParser has some TODO that awaits bugs to be fixed in Spring. They are fixed in Spring 2.5.3.
> So if for instance Camel 2.0 requires Spring 2.5.6 or later then we can safely fix this code as well.
> But we could also consider staying Spring 2.0.x combatible and fix this in a later Camel release.
> Any thoughts?
>     // TODO the following code is copied from AbstractSimpleBeanDefinitionParser
>     // it can be removed if ever the doParse() method is not final!
>     // or the Spring bug http://jira.springframework.org/browse/SPR-4599 is resolved

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