> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]] > > Hi Berin, > > where do you have classcast exceptions - inside Cocoon the > old version was > successfully running - with your changes Cocoon is not running anymore > becase we don't have a ServiceSelector right now for the > source factories > and afaik there is now implementation like the > ExcaliburComponentSelector > for a ServiceSelector right now, right?
In Fortress we were having problems. The issue was this: SourceResolverImpl.java implements Serviceable, where it used to implement Composable. When the change was made, the code was not updated to reflect that Serviceable components can have ServiceSelectors, not ComponentSelectors. Fortress correctly applies this contract, where ECM might not. We have proper wrappers so that a ComponentSelector can be turned into a ServiceSelector--its just that it needs to be done in the container. The contract is (or should explicitly be) this: * Composable can return ComponentSelector or Component * Serviceable can return ServiceSelector or service (as an Object) No Serviceable should ever return a ComponentSelector, and vice versa. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
