|
From: Darren D. <da...@da...> - 2003-10-20 21:03:33
|
On Monday 20 October 2003 16:50, j=C3=BCrgen h=C3=B6ller [werk3AT] wrote: > I'm inclined to go the "bean" / "local" / "external"(deprecated) route > again... Votes please! Given this decision, I vote for "local" instead of > "internal"; Colin obviously does too. It's likely I'm missing something obvious, maybe due to not using Spring on= =20 projects where I'd see the advantage of this, but what exactly is the=20 real-world advantage of having the distinction? I know it lends weight to= =20 the DTD validation for local beans, which means my IDE can tell me that I=20 made a typo in a <ref bean=3D"foo" /> tag before the logging output does, b= ut=20 is there something more? Or is there more of an advantage than I can see=20 from the additional validation - performance, or caching or something? Just a bit curious since part of the discussion relates to what is the=20 simplest concept and it seems as though it would be simplest all round if=20 <ref bean=3D"foo" /> was the only attribute, which worked for both local an= d=20 external. If there are good reasons to keep the distinction, then I'm +1 for the=20 bean/local option. TIA for any insight.. Regards, =2D-=20 Darren Davison Public Key: http://www.davison.uk.net/key.jsp |