Gunnar Boström wrote:
Hi,
How can I make the org.apache.struts2.dispatcher.FilterDispatcher NOT to
verify action classes when the Tomcat web server starts?
I use struts 2 together with spring and the actions classes communicate with
the server application with rmi.
The action classes are defined with lazy-init="true" because I would like to
be able to start the web application without the rmi server started, but it
looks like the filterDispatcher will try to instantiate the classes and then
the connection to the server fails.
I don't know if there is any way to turn off that behaviour. Your best
bet is probably to make your actions smarter, so that they can be
instantiated even when the RMI server is unavailable. In other words,
make the RMI connection initiation on demand rather than on action
instantiation.
L.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
