Apologies
The session and request scope discrepency was in there by mistake - that
was me debugging. Originally all was set to request. Unfortunatley it
makes no difference whether it is all set to request or session.
So it's something else!
Brett
Hubert Rabago wrote:
The form you're populating in your action is not the same instance
you're accessing in your JSP. Your JSP is looking for the form in
session scope, but you've configured your action to receive its form
in request scope, so you're actually using two forms. Remove the
'scope="request"' in the "/apache_connection_stats" so it'll use the
default session scope and match what you're expecting in your JSP, or
change your JSP to look for the form in request scope.
Hubert
On 7/12/05, Brett <[EMAIL PROTECTED]> wrote:
<action-mappings>
<action
path="/apache_connection_stats"
type="com.ftid.mis.action.MisAction"
name="ApacheConnectionStats"
scope="request">
<forward name="success" path="/pages/display.jsp" />
</action>
...
</action-mappings>
Action:
public ActionForward execute(ActionMapping mapping, ActionForm form,
HttpServletRequest request, HttpServletResponse response) {
apache_connection_stats tempform = (apache_connection_stats) form;
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
