The registry is initialized in tapestry's ApplicationServlet.init(). In
web.xml, you need to specify <load-on-startup>1</load-on-startup> for
the servlet configuration. This will force ApplicationServlet.init() to
run when the application is deployed instead of the first time a
tapestry page is hit.
-Steve
Norman Franke wrote:
I've been integrating Tapestry 4.0.x into my existing web application
based on JSP and servlets. It's all been going quite well so far.
I've been using Hibernate for database access in Tapestry, but was
using JDBC in the old servlet code. (Since it was developed
pre-hibernate.) Anyway, I want to start using Hibernate (via HiveMind)
in my servlet code. The question is, how do I get a reference to it?
I can do this via:
RegistryInfrastructure reg = (RegistryInfrastructure)
ServiceSerializationHelper.getServiceSerializationSupport();
And then call getService(MyDesiredDAO.class, null). That seems to
work. When Tomcat starts up, Tapestry doesn't initialize and
getService throws exception stating that HiveMind has not been
configured.
The question is, how can I force HiveMind to initialize or initialize
it myself and not mess up Tapestry?
Norman Franke
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
