Frank W. Zammetti wrote:
Laurie Harper wrote:
Why do you say that's a bad practice? It's actually both supported and
recommended; in fact, the 'name' attribute is deprecated in favour of
the 'id' attribute so 'id' is the only way to target CSS to a
particular page element rather than an
On Wed, September 14, 2005 6:35 am, Laurie Harper said:
I never said you *shouldn't* use 'class' to style elements :-)
True enough :)
That's the right answer when you want to apply the same set of styles to
multiple elements (although even without the 'class' attribute here,
you'd still only
On Wed, September 14, 2005 6:35 am, Laurie Harper said:
I never said you *shouldn't* use 'class' to style elements :-)
True enough :)
That's the right answer when you want to apply the same set of styles to
multiple elements (although even without the 'class' attribute here,
you'd still
I would say that the code that is yielded when you reference the form by
name is clearer and thus better regardless and I would throw away the
possibility of someone changing the name in the config file. It's more
important that the code be as explicit IMO.
I definitely like clean code
On Wed, September 14, 2005 10:15 am, Tamas Szabo said:
I definitely like clean code and if I'm looking at the generated HTML
I agree that it is cleaner if you reference the form by name.
But in the JSP it's just doesn't seem right to reference a form
name that will appear only in the generated
Frank W. Zammetti wrote:
If I don't want to use scripting I guess I could use something like
${requestScope['org.apache.struts.action.mapping.instance'].name}
But what if the Globals.MAPPING_KEY will change ... :-)
That's why you want to use the field in Globals... if the key under which
the
I think your 'semantics' arugment may be confusing two orthogonal sets
of semantics, but I do see where you're coming from.
We're well off-topic so I'm keeping this brief, but feel free to follow
up off-list if you want to discuss further.
L.
Frank W. Zammetti wrote:
On Wed, September 14,
On Wed, September 14, 2005 11:15 am, Laurie Harper said:
I think your 'semantics' arugment may be confusing two orthogonal sets
of semantics, but I do see where you're coming from.
Could be. Wouldn't be the first time :)
We're well off-topic so I'm keeping this brief, but feel free to follow
A tag would be handy for this ...
Indeed there is one, please take a look at bean:struts/
form name=next action=/jsp/awp/awpoutput.jsp target=display /
script language=javascript
document.next.submit();
/script
The problem I have is that the form tag in Struts has no name!
Why?
So how can I execute the java-script? Which name should I use instead?
Regards
Antonio
gollinger wrote:
form name=next action=/jsp/awp/awpoutput.jsp target=display /
script language=javascript
document.next.submit();
/script
The problem I have is that the form tag in Struts has no name!
Why?
So how can I execute the java-script? Which name should I use instead?
Regards
Message -
From: Jason King [EMAIL PROTECTED]
To: Struts Users Mailing List user@struts.apache.org
Sent: Tuesday, September 13, 2005 11:05 AM
Subject: Re: How to replace normal html-from through html:form in Struts?
Example
gollinger wrote:
form name=next action=/jsp/awp/awpoutput.jsp
, September 13, 2005 11:05 AM
Subject: Re: How to replace normal html-from through html:form in
Struts? Example
gollinger wrote:
form name=next action=/jsp/awp/awpoutput.jsp target=display /
script language=javascript
document.next.submit();
/script
The problem I have is that the form tag
: Tuesday, September 13, 2005 11:05 AM
Subject: Re: How to replace normal html-from through html:form in
Struts? Example
gollinger wrote:
form name=next action=/jsp/awp/awpoutput.jsp target=display /
script language=javascript
document.next.submit();
/script
The problem I have is that the form
Mailing List user@struts.apache.org
Sent: Tuesday, September 13, 2005 11:05 AM
Subject: Re: How to replace normal html-from through html:form in Struts?
Example
gollinger wrote:
form name=next action=/jsp/awp/awpoutput.jsp target=display /
script language=javascript
AM
Subject: Re: How to replace normal html-from through html:form in Struts?
Example
gollinger wrote:
form name=next action=/jsp/awp/awpoutput.jsp target=display /
script language=javascript
document.next.submit();
/script
The problem I have is that the form tag in Struts has no name!
Why
On 9/14/05, Frank W. Zammetti [EMAIL PROTECTED] wrote:
It's generally something to avoid because you may at some point change
the order of your forms and then find that your code no longer works.
Think of what happens if you put a form before this one later... now the
form you want is
Tamas Szabo wrote:
Isn't there a struts tag which for a given action path it gives me the
name of the associated form?
No there isn't, though it'd be trivial to write. What you can do,
though, is something like this:
bean:define id=formTag name=org.apache.struts.taglib.html.FORM/
Laurie Harper wrote:
Why do you say that's a bad practice? It's actually both supported and
recommended; in fact, the 'name' attribute is deprecated in favour of
the 'id' attribute so 'id' is the only way to target CSS to a particular
page element rather than an entire display class.
...
19 matches
Mail list logo
