Eric Pugh wrote:
Hi all,
I am looking at the Avalon wrapper for Hibernate (available at http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/hibernate/HibernateExt/avalon /src/java/net/sf/hibernate/avalon/ ) and there is a bit of confusion. I was always under the impression that to use a component with Avalon, you need to have the interface implement the Component interface.
Can you verify this? I am trying to close a bug in Hibernate and want to doublecheck the fix. And extend my knowledge of Avalon.. I have been happily putting Component in all my interfaces everywhere... But maybe I don't have to?
You can safely remove all Component interfaces if you using Fortress, Merlin or Phoeinix. The Component interface was depricated some time ago with no replacement.
From the javadoc for the component interface:
Deprecated: /Deprecated without replacement. Should only be used while migrating away from a system based on Composable/ComponentManager. A generic |java.lang.Object| can be used as a replacement. /
Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED] http://www.osm.net
Sent via James running under Merlin as an NT service. http://avalon.apache.org/sandbox/merlin
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
