On 8/10/07, Brian Kotek <[EMAIL PROTECTED]> wrote: > You shouldn't be instantiating the factory yourself. The plugin does this > automatically and makes the bean factory available
Heh, you have missed *so* much of the history of this topic :) Bryan is creating a security component that can be dropped into a number of frameworks both with and without ColdSpring and so he's trying to figure out a modular way of handling all these cases. I think he's on a bit of a hiding to nothing, personally, but he's giving it the old college try... My suggestion all along has been to write framework-specific adapters (that know where the framework's bean factory is) as well as a non-framework adapter (that creates its own ColdSpring factory - if one is not passed into it). -- Sean A Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "If you're not annoying somebody, you're not really alive." -- Margaret Atwood
