-----Mensagem original----- De: Sylvain Wallez [mailto:[EMAIL PROTECTED]
> One of the big advantages of newer containers are the fact that there's > no container-specific API that components must adhere to, thus > theoretically allowing cross-container reusability. The viral nature of > Avalon APIs is something many people are reluctant with when I explain > them how to develop new components in a Cocoon environment I second that, and I think everyone else will do as well. So we should concur about the first principle that should be applied to a new generation of containers: supporting POJOs. How to do that is a secondary problem. > and also some > kind of selector-like mechanism (yes, it's sometimes needed). And there is something I need to agree. In complex system you'll have to face it eventually. Like having a ConnectionService (which provides connection management to different data sources). How to ask for a ConnectionService singleton instance for a particullar database/datasource ? I'd like to use something like: LookupCriteria criteria = new LookupCriteria( ConnectionService.class ); criteria.put( "supports", "dbf-files" ); Cocoon could use something similar when asking for serializers/transformers/et al: LookupCriteria criteria = new LookupCriteria( Serializer.class ); criteria.put( "accepts", "xls" ); But in a POJO world, how to give this kinda hint/condition to the container? Cheers, hammett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Apache Excalibur Project -- URL: http://excalibur.apache.org/
