It seems the granularity of re-use you describe is at the application or
web-application level. Obviously, such objects must exist internally to
Orion. There may be reasons why they are not public, but I certainly would
love to see something like HttpApplication or WebApplication or whatever it
may be called exposed in order to persist values while a web-app is running.
Just checked - yes there is a com.evermind.server.http.HttpApplication class
... but the class isn't in the API
I assume that <resource-ref> in web.xml can be used for this purpose at
WebApp level, but I have not tried it.
There may be other custom stuff to persist at the OrionServer level, too,
i.e. shared by all apps - orion.properties is the place to put them
according to http://www.orionsupport.com/articles/properties.html -
com.evermind.server.ApplicationServer is the class, but how do I get the
props without an instance (or static method) - not in the API either, but
maybe I am missing out on something obvious?
--peter
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of elephantwalker
Sent: Saturday, March 24, 2001 8:40 PM
To: Orion-Interest
Subject: persistance
I have this problem with session beans. I have certain objects which I want
to be persistant across all session beans. One approach is to use an entity
bean. But that's a little overkill. These are several xml files which I use
to setup some of the session beans properties, but they are not expected to
change.
Parsing the xml files each time a session is created is another approach.
But that gives me the *lag time* during the parsing, and slows down my
application.
Is there another alternative? Can I load a bean each time the server is
restarted, or when an event occurs (say, the *datetime* changes on the
file)?
Has anybody else faced this problem and solved it?
regards,
Elephantwalker
