Comment below. Thanks.
On 8/24/06, Jim Marino <[EMAIL PROTECTED]> wrote:
On Aug 24, 2006, at 11:08 AM, Yang ZHONG wrote: > It has been one full day since Ant proposed a go for registry and Jim > agreed. If no one oppose, I'm going to contribute a registry. I think this would be great. > The registry will support > . different Symbol Spaces (type, top level element, message, > portType/interface, etc.) > . multiple scopings (ClassLoader, location, Eclipse IProject, > composite, > etc.) > . different scope delegations (no delegation, PARENT_FIRST, > PARENT_LAST) > . multi-dimension scopings (location vs. ClassLoader/IProject, etc) > and > registry aggregation (NameSpace aggregation) > . automatic locate on demand > . automatic load on demand > . automatic refresh on demand > . multi-threading > . weakly/softly referencing scopes (it's user's responsibility not > to strong > reference key from value directly or *indirectly*, it's recommended to > change such strong reference if any to weak/soft one if permanent > residency > isn't desired) > > I will also contribute a scoping(SPI) implementation for > ClassLoader and > Eclipse IProject, Could you explain how an IProject relates to this?
ClassLoader and IProject are just Scoping examples, I have no intention to use them for SCA at all, from that perspective, both ClassLoader and IProject are not related, they're not SCA specific. The reason I put them there is just to illustrate the registry is generic and can take any Scoping. Sorry didn't clarify that.
however we may need volunteer(s) to > contribute/integrate/register SCA (composite) scoping. Could you also explain a bit more about what you see as SCA composite scoping? I was thinking the system service would be "module" scoped (i.e. singleton per composite it is already deployed as), or associated on the CompositeComponent directly, in which case the classloader lookup is probably not necessary (the option of using the property extension mechanism).
I don't have much knowledge about SCA composite scoping yet, and I have no intention to impact that (yet). With generic registry hat on, I don't really count on if SCA uses module or CompositeComponent or ClassLoader or anything else for scope, as long as there's a SPI implementation telling the generic registry what parent scope is for delegation of a given scope. Sorry didn't clarify that.
I will contribute a refreshing checking(SPI) implementation based on > file/ZipEntry/URL timestamp, however we may need volunteers to > contribute/integrate/register locator(SPI) implementation and loader > (SPI) > implementation. > > I'll ask for help from Ant to change the Axis2 binding and JavaScript > container to use the registry. Thank Ant for the offer. > I'll also ask Jim for help with the system service part. Thank Jim > for the > offer. Np thanks for doing this. > > I'll try to roll out API and SPI for review as soon as possible. > > Thanks. > > -- > > Yang ZHONG --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Yang ZHONG
