Following lots of discussion with regard to this change on james-dev currently going on, I feel I need to -1 this change until at least the next major release for Cornerstone (ie until 5.0), as it breaks backward compatibility.
Rationale --------- Some projects (ie JAMES) expose the ComponentManager interface, and hence the Component interface, as part of their API, while also depending on some of the cornerstone components and exposing these through the ComponentManager by contract. Hence, removing Component and ComponentManager from Cornerstone means that this client API breaks. We should be supportive of our fellow developers at JAMES -- and any other projects with a similar concern -- and give them the time to handle this issue gracefully. We should, however, formally deprecate the pieces in Cornerstone that depend on the Component (& friends) interfaces, and indicate that they will move to ServiceManager in the future, if we still want to continue with this change. Impact ------ This means that containers that want to be able to host the Cornerstone components (ie Phoenix, Merlin) need to keep supporting Component/Composable and friends. This is a good thing =) best regards, Leo Simons On Tue, 2002-09-24 at 14:21, Peter Donald wrote: > Applied - thanks! > > On Tue, 24 Sep 2002 08:58, Steve Short wrote: > > Following my email a few days ago - here is a patch to replace Component > > Classes with Service Equivalents in Cornerstone Store, RepositoryManager > > and AbstractFileRepository. Diff generated using cvs diff -u at top > > level jakarta-avalon-cornerstone directory. > > > > Regards > > Steve > > > > <<cornerstone.diff>> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
