This message seems to have been lost - sorry for any dups
----
From: [EMAIL PROTECTED]
Subject: Federating ScopeContainer, was: Change to
PhysicalComponentDefinition
Date: March 12, 2007 11:47:18 AM PDT
To: [email protected]
On Mar 11, 2007, at 10:16 PM, Jeremy Boynes wrote:
Firstly, transporting Scope is not enough on its own as there is more
than one COMPOSITE scope. The builders used to get this from the
deployment context but with federation it will need to be passed to in
the PCD. I think instead we should treat ScopeContainers as resources
and give them IDs like ClassLoaders. For COMPOSITE scope the ID can be
the URI of the component implemented by the composite; for others we
can use well known IDs. Every component has a scope so I think we can
put scopeContainerID down in to PCD itself.
Following on with this I'm going to make the following changes to the
ScopeContainer SPI to externalize the idea of a instance of a scope
i.e a ScopeContext:
* add methods startContext(Object id) and stopContext(Object id)
this will place external code in control of the lifecycle of the
scope context so that it can be initiated
by the code that dictates the lifecycle. This will allow us to avoid
having the container register for and
receive events just to detect context lifetime.
* change get and return wrapper to also pass the contextId
* add a Map<Scope, Object> to the WorkContext to associate scope
context ids with the current work
* update the target invoker to get wrappers based on the current work
context and the component's scope
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
