ReloadableResourceBundleMessageSource broken in nightly

[GrantGochnauer]

I have been using the "ReloadableResourceBundleMessageSource" to load my message sources but it seems recently this has stopped working..

What I had before was:

    <bean id="messageSource" class="org.springframework.context.support.ReloadableResourceBundleMessageSource">
        <property name="basenames">
            <list>
                <value>com/vodori/dolce/web/resources/applicationResources</value>
            </list>
        </property>
        <property name="useCodeAsDefaultMessage" value="false"/> 
        <property name="cacheSeconds" value="3"/>
    </bean>

but that was not finding any of my messages and so just to see what would happen, I switched it to the normal "ResourceBundleMessageSource" and it's working just fine.. So this snip of code does work:

    <bean id="messageSource" class="org.springframework.context.support.ResourceBundleMessageSource">
        <property name="basenames">
            <list>
                <value>com/vodori/dolce/web/resources/applicationResources</value>
            </list>
        </property>
        <property name="useCodeAsDefaultMessage" value="false"/>
    </bean>

[GrantGochnauer]

Oops. I should have posted this under the "Web" forum. Sorry about that.

[GrantGochnauer]

Created JIRA issue to track:
http://opensource.atlassian.com/proj...rowse/SPR-2319

[Costin Leau]

Could you test your code against a stable build? If the error persists please raise an issue on jira. Thanks!

[Costin Leau]

You read my mind... over the wire! Thanks for the feedback - it is very important for us as we can't fix bugs we don't know about.

[GrantGochnauer]

I did test this with Spring 1.2.x and it does work fine. In fact, I actually took a web app based on 1.2.x, made a copy which included the Reloadable resource bean, put in Spring 2.0RC3 (nightly) and have been working on it for a few weeks only to recently start adding in resource bundles which is when I ran into this problem...

I'm not sure if any certain Spring 2.x build broke it unfortunately but I do know it worked just fine in 1.2.x

Thanks!