You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Gunnar Boström <Gu...@tietoenator.com> on 2008/01/21 13:29:17 UTC
Unable to verify action class
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.
regards
Gunnar
--
View this message in context: http://www.nabble.com/Unable-to-verify-action-class-tp14996495p14996495.html
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Unable to verify action class
Posted by Gunnar Boström <Gu...@tietoenator.com>.
Hi,
I've just found a way to do precisely what you proposed, hanks,
Regards
Gunnar
Laurie Harper wrote:
>
> 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: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/Unable-to-verify-action-class-tp14996495p15013677.html
Sent from the Struts - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org
Re: Unable to verify action class
Posted by Laurie Harper <la...@holoweb.net>.
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: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org