The struts-config_1_1.dtd file that is included with the distribution has
pretty good definitions for each parameter that is used by each tag.

Jerry Jalenak
Team Lead, Web Publishing
LabOne, Inc.
10101 Renner Blvd.
Lenexa, KS  66219
(913) 577-1496

[EMAIL PROTECTED]


-----Original Message-----
From: Gregory F. March [mailto:[EMAIL PROTECTED]
Sent: Friday, June 13, 2003 7:30 AM
To: [EMAIL PROTECTED]
Subject: [REPOST] Understanging Path/Action/Forward/Parameter naming



[Sorry for the repost.  I'm doing it for two reasons.  First, I got no
response, and I'm wondering if it's because this is a really dumb
question or if nobody really knows. :-)  And second, because I think I
really need to understand this in order for me to make some decisions
about the architecture of my app.  So, any response would be
welcome... -gfm]

Please forgive the naive question that follows...

Is there a write up somewhere that explains how Struts deals with
names?

Specifically, I would like to understand the different syntaxs of
"path", "name" and "parameter" arguments.

In the following, what is "name" and "path":

    <forward name="aname" path="apath">
    <forward name="aname" path="/apath2">
    <forward name="aname" path="/apath3.do">

And the same thing in:

    <action path="/apath" input="apath2" parameter="apath3" ... >

... and all its variants.

How does one know if it is a real path, a name to be looked up, an
action, a tile definition, etc.?  What are the rules?

I think some of my past questions would have been avoided if I
understood these concepts.

Thanks,

/greg

--
Gregory F. March    -=-    http://www.gfm.net:81/~march    -=-    AIM:GfmNet

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


This transmission (and any information attached to it) may be confidential and is 
intended solely for the use of the individual or entity to which it is addressed. If 
you are not the intended recipient or the person responsible for delivering the 
transmission to the intended recipient, be advised that you have received this 
transmission in error and that any use, dissemination, forwarding, printing, or 
copying of this information is strictly prohibited. If you have received this 
transmission in error, please immediately notify LabOne at the following email 
address: [EMAIL PROTECTED]



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

Reply via email to