I have done something like this. The Factory and Singleton design
patters work perfectly for this type of thing. If you create an
abstraction layer, then there should be no problems....
On 9/28/05, Leon Rosenberg <[EMAIL PROTECTED]> wrote:
> still, spring can use the same factory.
> If not, use a container that can use factories :-)
>
> If nothing works, the hack would be:
>
> class MyObjectInstanceHolder{
> private static MyObject instance;
>
> public set/getInstance...
> }
>
> ?
> regards
> leon
>
> On 9/28/05, Darryl L. Pierce <[EMAIL PROTECTED]> wrote:
> > Leon Rosenberg wrote:
> > > Aehm, without looking deeper into context initialization, just a short
> > > guess:
> > > what about making your configuration objects a singleton with
> > > public static CLASSNAME getInstance()
> > > or
> > > provide a factory for them?
> >
> > Because the class in question is created by Spring's application context.
> >
> > --
> > Darryl L. Pierce <[EMAIL PROTECTED]>
> > Homepage: http://mcpierce.multiply.com/
> > "Bury me next to my wife. Nothing too fancy..." - Ulysses S. Grant
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
