Good catch! 1.0's drop date has crashed and burned, but it's really
good that this came in before we let it loose! Thanks
On Mar 3, 2006, at 1:49 PM, Dave Ross wrote:
Qasim,
The init-method should only be called once on the "info" bean when it
is created (and it should only be created once).
I just made a test case and can confirm this as a bug. For some reason
we never checked to see if init-method was called previously before
calling it - how we missed this I have no idea - we have been using
init-method in various code for a while, I wonder if some of it is
firing multiple times...
Anyways, the ticket has been created
(http://project.fmdrl.org/browse/CSP-42) and the fix is already
checked into CVS. If you want to apply just these changes to your copy
of ColdSpring have a look at:
http://dev.fmdrl.org:9010/changelog/Coldspring2/?cs=MAIN:rossd:
20060303184532
thanks a ton for finding this one!
-Dave
On 3/3/06, Qasim Rasheed <[EMAIL PROTECTED]> wrote:
Hi,
I have following definition for my services
<bean id="info" class="info" singleton="true" init-method="configure"
lazy-init="false">
.......
</bean>
<bean id="manager1" class="manager1" singleton="true">
<property name="info"><ref bean="info" /></property>
<constructor-arg
name="managername"><value>manager1</value></constructor-arg>
</bean>
<bean id="manager2" class="manager2" singleton="true">
<property name="info"><ref bean="info" /></property>
<constructor-arg
name="managername"><value>manager2</value></constructor-arg>
</bean>
It seems that the configure method for "info" bean is invoked
everytime when
I call getBean for both manager1 and manager2. Is it a normal flow
for
Coldspring and if so how can I avoid such situation.
Thanks
Qasim
