Hi All

We have a requirement to provide transport independant services within our
organization and thus have implemented some services using the SOAP messaging
provided by WSE 2.0 SP1.  Our services are exposed via a Service Inteface
Layer that runs on top of our Domain Object Model.  The Service Inteface
Layer instantiates the relevant DOM objects and use them to gather
information, execute validations etc.  The data contained within the DOM
represent our product rules and is read-only data.  Some rules are also
implemented as relationships between different DOM objects.  The same DOM
objects instances can thus be shared across all calls coming from the Service
Interface Layer.

To prevent from having to re-build the DOM with every service call, we would
like to be able to cache the parts of DOM as they are used for the first
time.  Subsequent service calls therefore will get the DOM objects out of the
cache and not have to spend time re-assembling the same object instances into
memory.

With ASP.NET web services this is possible using the HttpContext.Cache
object that you receive as the ASP.NET web service infrastructure.  However,
with WSE 2.0 that can be hosted outside IIS, this is obviously missing.  How
can one implement functionality like this using WSE 2.0?  What would be the
right way to design for this?

Regards