Hi Samuel,
I'm not sure why the input couldn't accept pages and forwards within one
application. That's probably a good question for the major contributors to
the framework. For the struts-config.xml file Ted Husted's book, "Struts
in Action", is a good reference that I have used . The book has a chapter
completely dedicated to the struts-config API. The chapter really just has
the dtd information formatted in a more readable layout. In terms of
examples, I have looked at the examples included with the struts downloads
and other random learning opportunities, like this mailing list. Sorry I
don't really have a good answer for either question.
Nick
|---------+------------------------------>
| | Samuel Rochas |
| | <[EMAIL PROTECTED]|
| | nasoft.com> |
| | |
| | 05/17/2004 03:33 PM|
| | Please respond to |
| | "Struts Users |
| | Mailing List" |
| | |
|---------+------------------------------>
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: Struts Users Mailing List <[EMAIL PROTECTED]>
|
| cc:
|
| Subject: Re: Server side validation
|
>------------------------------------------------------------------------------------------------------------------------------|
Hello Nicholas,
Ok, thank you very much for the explanation, it makes the things a bit
clearer and less magical to me.
I have two questions:
-Why making that difference once for all? I mean, why not just accept
everything here (page, action, forward)?
-Where is a good and complete documentation with examples about
config-struts.xml to find (except struts-config_1_1.dtd)?
Sincerly
Samuel
--- andinasoft SA - Software y Consulting ---
Mariano Aguilera 276 y Almagro - Quito, Ecuador
Tel. +593 2 290 55 18 ---- Cel. +593 9 946 4046
--------- http://www.andinasoft.com ---------
---------------------------------------------------------------------
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]
