cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stephen McConnell <mcconn...@apache.org>
Subject Re: Getting rid of deprecated Interfaces/Classes/Methods
Date Tue, 24 Sep 2002 22:39:14 GMT


Carsten Ziegeler wrote:

>Ok, I think we should have a look at a features list of fortress
>and merlin compared to the ECM.
>

The closest thing I can point you to is the Merlin FAQ which provides a 
summary of the differences between Merlin and other related work in 
Avalon land.

  http://jakarta.apache.org/avalon/excalibur/merlin/faq.html

>
>Is this somewhere available?
>

In addition to the above, the Merlin documentation inlcudes:

  The general Merlin 2.0 documetation
  http://jakarta.apache.org/avalon/excalibur/merlin/

  Merlin 2.0 APIs.
  http://jakarta.apache.org/avalon/excalibur/merlin/api/

   Excalibur Container
   http://jakarta.apache.org/avalon/excalibur/container/
   (Merlin 2.0 provides full support for the lifestyle - refer 
attributes page)
   and lifecycle extension mechanisms

  Excalibur Meta (the meta info layer)
  http://jakarta.apache.org/avalon/excalibur/meta

>
>I learned by this thread that some marker interface are not
>available anymore and have to be configured somewhere for fortress.
>Is this right? 
>

Yep - instead of defining these sort characteristics through a maker 
interface, the Merlin 2 approach enables component authoris to declare 
this information in the meta-mode for the type.  For example, you can 
declare a atttrtibute "avalon:lifestyle" with a value of "pool", 
"transient", "thread", etc.  Details on attribute values related to 
lifestyle are included under the link 
http://jakarta.apache.org/avalon/excalibur/container/attributes.html 
(end of page).

>
>So which marker interfaces are concerned? C
>How much effort is it to still support those marker interfaces without
>needing the extra configuration?
>  
>

It is possible in Merlin providing you declare a customer lifestyle 
manager.  The default lifestyle manager does not support the lifestyle 
marker interrfaces but it wouldn't be a big thing to create a manager 
that checked for marker interfaces.  This could declare at the system or 
container level.  

Cheers, Steve.

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

-- 

Stephen J. McConnell

OSM SARL
digital products for a global economy
mailto:mcconnell@osm.net
http://www.osm.net




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


Mime
View raw message