On Monday 17 June 2002 08:28 pm, Stephen McConnell wrote:
> parsing of an XML doucment. A parameter from a properties file is far
> more efficient. I would prefer that these two stayed seperate (i.e. no
> change).
Would the ability to generate a Configuration from a properties file satiate
this need?
> >5) CM should at least look like this:
> >
> >interface ComponentLocater /* or ServiceLocator */
> >{
> > Object lookup(String role) throws ComponentException;
> > boolean hasComponent(String role);
> >}
>
> Which is basically equivalent to A4 ServiceManager assuming release() is
> depricated. As far as A4 is concerned I thinkk we should introduce this
> into the service package (renamed to ServiceLocator for package
> consistency), update ServiceManager to extend from ServiceLocator for
> backward compatability, and declare ServiceManager as a depricated
> interface. That provides a complete migration path now - now need to
> wait for A5.
+1
> >class ComponentException extends Exception
> >{
> > // ... skip constructors and impls.
> >
> > String getRole();
> > Throwable getCause();
> >}
>
> +1
> Could be added to the current A4 defintion of ComponentException and
> ServiceException without brreaking anything.
+1
> I think the main thing missing in the above is the work on getting a
> formal meta model in place as part of the framework. This can be viewed
> as an A4 activitiy because there are not obsticles and no changes needed
> to put it in place.
And a very important activity too!
-pete
--
peter royal -> [EMAIL PROTECTED]
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
