cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Berin Loritsch" <blorit...@apache.org>
Subject RE: [RT] Cocoon Blocks and internal web services
Date Fri, 29 Mar 2002 13:49:17 GMT
> -----Original Message-----
> From: Stefano Mazzocchi [mailto:stefano@apache.org] 
> 
> > Do you mean here to replace ComponentManager/Selector with the CM 
> > interface discussed for future Excalibur release CM.select(String 
> > role,  Object query) where, in this case, query would be the URL?
> 
> I don't know. I'm currently not following Avalon development 
> due to lack of time and focus, the above isn't focused on 
> implementation but only on behavior and design.

The next-gen Framework is on hold.  We have an equivalent to CM/CS
called the ServiceManager and ServiceSelector (for lack of a better
name).  The only difference is that the Service** mechanisms do not
require your components to implement the Component interface.  This
was to address a need in several projects where the components used
were developed by third parties, and did not have the ability or
right to change the interfaces that the components/services used.

The ServiceManager/ServiceSelector mechanism works with Objects.
While you *can* use it a generic lookup service for any object,
it is not encouraged.  The purpose is for using components that
you have no access to the source code to change the interface.

Rest assured, in future versions of Framework, we will remove the need
for arbitrary marker interfaces--so that all interfaces actually have
a purpose.

Beyond that, there is not much you have to worry about.  Change is
slow in Avalon, because we want to make it useable for a wide audience.
We really don't want to break backwards compatibility if we can
help it.


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message