On Fri, 1 Nov 2002 07:15, Olaf Bergner wrote: > >Since a few days we are switching our Project from ECM to Phoenix 4.0.1. > > The > > >first components we tested worked just fine but now we seem to hit some > >subtle semantic differences that cause us some trouble: > > This implies, that your problem is NOT rooted in a a general > incompatibility with the concepts endorsed by the Avalon Framework, but > rather Phoenix specific. Is that right?
Or ECM specific ;) > So we are talking components, not blocks, right? (Referring to one of your > latter postings) In Phoenix there is no difference between the two. Historically there was but that is no more. > 2. Instead of writing a factory for those expensive components, why not let > them be managed by the Excalibur Component Manager (or a custom derivative, > if more applicable), which is - after all - a component that could, in > turn, be managed by Phoenix? Thats what most people do. However it may be better to use Fortress which has a similar style but which is not deprecated. -- Cheers, Peter Donald "The ability to quote is a serviceable substitute for wit." -- Maugham -- To unsubscribe, e-mail: <mailto:avalon-users-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:avalon-users-help@;jakarta.apache.org>
