On Sunday 02 November 2003 14:05, Stephen McConnell wrote: <snip/>
> Mapping from MyStateValueType (an interface) to a home is not the same > as service to provider resolution. Instead, what you want to locate is a > component that implements a home interface for the MyStateValueType - > e.g. MyStateValueTypeHome is the home interface and > MyStateValueTypeHomeProvider is the component implementation that > provides creation, retrival and destruction of instance of > MyStateValueType. > > At the meta-data level would would need something like: > > <component class="MyDemoComponent" name="whatever"> > <identity> > <key>12345</key> > </identity> > </component> > > The container on creation of an identifiable component resolves the home > factory (an implicit lifecycle dependency) and if the meta-data declares > a key, then a persistent value is retrieved and supplied to the > component via a context entry. If no identity is supplied, a new state > value is created and supplied. > > Any thoughts? I'm not sure to understand clearly your approach. Tell me if I'm wrong You suggest 3 parts 1/ compenent: implementing home interface (2) 2/ home: interface that define persisted data 3/ provider: impl that provides custom finder for home interface of the component (1) but I dont get clearly identity/home purpose. Should home define method that will be used by provider to establish persitence? (if yes, then this sounds nice ,)) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
