Jared,
google for MethodInvokingFactoryBean
that's how spring handles it. Right now you could do it with an inner
bean and factory method of "get"... But you'd be redefining your
constants bean over and over again within each bean that needs it.
-dave
On 4/20/06, Jared Rypka-Hauer <[EMAIL PROTECTED]> wrote:
> Hey folks,
>
> I'm considering looking at implementing a way to make this work:
>
> <bean id="Verity" class="model.util.VerityController" singleton="true">
> <constructor-arg name="collection">
> <value>${Constants.get("verityCollection")}</value>
> </constructor-arg>
> </bean>
> <bean id="Constants" class="model.util.Collection" singleton="true">
> <constructor-arg name="values">
> <map>
> <entry key="verityCollection">
> <value>ci</value>
> </entry>
> </map>
> </constructor-arg>
> </bean>
>
> I think it needs to be done after the whole circular dependency
> problem is fixed (post-1.0?), but I'd be happy to figure it out.
>
> I actually had it working once, but Chris informed me that the way I
> was doing it was custom-engineered to make the circular references
> problem go wild, so I rolled back to the current repository... I had
> to chuck "working" code, but it was dangerous working code. ;)
>
> So, more than anything, does anyone think this is valuable enough to
> implement and, on another note, does anyone know how Spring handles
> this internally?
>
> Laterz,
> Jared Rypka-Hauer
>
> [EMAIL PROTECTED]
> http://www.cfobjective.com
>
>
>
>
