Peter Alfors typed the following on 09:37 AM 6/25/2001 -0500
>The name attribute is not required.
Aha, thanks, I had confused name and type.
>Kief Morris wrote:
>> It seems that the tag in struts-config.xml requires a form
>> bean for the name="" attribute.
Kief
On Mon, 25 Jun 2001, Kief Morris wrote:
> I'm making my first Struts application, and in keeping with MVC
> I want to load all of my JSP pages through actions: the Action sets
> up the data the JSP page needs to display.
>
> It seems that the tag in struts-config.xml requires a form
> bea
And, if you leave out the name tag, you should also leave out validate.
The minimum Action Mapping then becomes
Assuming ViewAction knows where to go afterwards. If not, you can add
local forwards, or use the input or parameter properties to pass more
information.
Just as an aside, if you ar
The name attribute is not required.
You can leave it out, however, if you are using the html:form taglib on
your page, then
it will want an actionform. So in that case, you will either need to have
an empty bean, or use the standard HTML tag --> without a bean.
HTH,
Pete
Kief Morris wrote
I'm making my first Struts application, and in keeping with MVC
I want to load all of my JSP pages through actions: the Action sets
up the data the JSP page needs to display.
It seems that the tag in struts-config.xml requires a form
bean for the name="" attribute. But what if I have a view
Pierre Métras wrote:
> Hi,
>
> I have to code a menu. Depending on the user interaction, different features
> will be executed. These features are Struts actions *.do URL with associated
> JSP files for the views. The menu is included on all the forms.
>
> Should I use an Action class to manage t
Hi,
I have to code a menu. Depending on the user interaction, different features
will be executed. These features are Struts actions *.do URL with associated
JSP files for the views. The menu is included on all the forms.
Should I use an Action class to manage the menu processing, knowing that n
7 matches
Mail list logo