|
From: Mark P. <mar...@co...> - 2004-08-27 16:09:53
|
Hi,
Actually there was some discussion started by Simon on what to do here, =
but
I don't think we got closure. =20
In anycase, this functionality sits in the PropertyPlaceholderConfiguer,
which isn't yet ported. This is declared in the spring objects xml file =
and
then later whenever a ${key} is listed as the value for a property it =
would
be converted to the value in that file.
The last trail of this on the mailing list is here - though I think some
emails weren't included in the thread somehow...
http://sourceforge.net/mailarchive/forum.php?thread_id=3D5308930&forum_id=
=3D4004
9
My last post there gave my opinion on the topic.... Simon any thoughts?
Cheers,
Mark
> -----Original Message-----
> From: Federico Spinazzi [mailto:f.s...@ma...]=20
> Sent: Friday, August 27, 2004 10:59 AM
> To: Mark Pollack
> Subject: Re: Started work on ProxyFactoryBean (was: from=20
> where to continue ...)
>=20
>=20
> Mark Pollack wrote:
>=20
> >Hi,
> >
> >Seems ok to me, can't have too many cooks in the Context package and=20
> >you already know you way around the AOP package.... If you have the=20
> >time I'd start kicking the tires on the existing codebase, is there=20
> >already enough functionality to use Spring to replace the home-grown=20
> >version you had made a while ago?
> > =20
> >
> I think so even if I didn't the switch: we make use of a 'proprietary=20
> extension": referring objects defined in another file
> <Property name=3D"Connection">
> <ExternalRef file=3D"DataConnections.xml" =
object=3D"connessione"/>
> </Property>
> <embarrassment>Maybe this is possible also with Spring=20
> ...</embarrassment> Federico
>=20
|