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
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
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?
regards
leon
On 9/27/05, Darryl L. Pierce <[EMAIL PROTECTED]> wrote:
> I have embedded T
I have embedded Tomcat 5.0.28 into an application I'm writing. Tomcat is
being used primarily as the configuration system. I would like to, from
the servlet running within Tomcat, access objects that are a part of the
main application itself, specific some configuration objects. Is there a
way,