Oh no, I understand the case sensitivity problem ( geez, do I seem like that much of a newbie? :-) )

I was just wondering where it figured out to pick up the proper bean, and you answered it with

<html:form name="blah blah"
and since I have:

<html:form action="Login" >

I don't see how it pertains to this, unless the action Login, which is defined like this:

<action path="/Login" type="net.sfeir.security.actions.LoginAction" name="loginForm" scope="request" validate="true" input="loginPage">
<forward name="Success" path="homePage"/>
<forward name="Failure" path="loginPage"/>
</action>
<form-bean name="loginForm" type="net.sfeir.security.forms.SecurityForm"/>

cascades all the way down the path to see that the name in the action definition is loginForm and that points to form-bean of type SecurityForm?

If this is the case, I am getting more and more impressed with Struts! Geez this thing is almost reading my mind... accidentally or not.

Also if this is the case, is there an advantage to 'naming' the form like this:

<html:form action="Login" name="net.sfeir.security.forms.SecurityForm">

I can see one advantage that it might override the default specified in the struts-config (just guessing here).

R

--
Robert S. Sfeir
Senior Java Engineer
National Institutes of Health
Center for Information Technology
Department of Enterprise Custom Applications
[EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to