I'm running an experiment with classpaths & classloaders.
Although my conventional tapestry setup works well, I'm getting this
exception in my test and would like to understand it's cause.
java.lang.RuntimeException: No service implements the interface
org.apache.tapestry5.hibernate.HibernateSessionManager.
at
org
.apache
.tapestry5.ioc.internal.RegistryImpl.getService(RegistryImpl.java:560)
at
org
.apache
.tapestry5
.ioc.internal.ObjectLocatorImpl.getService(ObjectLocatorImpl.java:44)
at org.apache.tapestry5.ioc.internal.services.MasterObjectProviderImpl
$1.invoke(MasterObjectProviderImpl.java:56)
at
org
.apache
.tapestry5
.ioc.internal.OperationTrackerImpl.invoke(OperationTrackerImpl.java:68)
... 92 more
From my own experience & reading up on this exception on the lists, I
gather that there is an issue with finding the tapestry-hibernate (or
hibernate) classes at runtime because they have not registered
themselves in the ioc registry. Is this correct?
If so, how does a service technically get into the registry? b/c the
initial startup appears to work (and lists application-specific
services!).
If not, what makes HibernateSessionManager different from tapestry's
built-in services or those of the web-app?
--
Robert Hailey
