For those who haven't read the Jira comments I posted about this bug, I have inlined them here:

--------------------------------
I agree that the Property tag shouldn't print when the "id" attibute is present. It would be uncommon that a person would both want to print the selected value and store it in a page attribute at the same time. Currently to supress the Property tags print functionality while using the "id" attribute you have to both a start and end tag with content between them. This is confusing and non-intuitive.

This will change the behavior of the tag, but I'm guestimating that the number of end users impacted will be low. Again, this is because the function of assigning to a page attribute and printing contents aren't usually combined.
--------------------------------

Is changing this behavior for 1.3 going to cause anyone tons of pain and misery? I know that maillist != userbase but, we need to find out if people are relying heavily on this "feature".

-Maurice


On Thursday, November 7, 2002, at 04:33 AM, Erik Beeson wrote:

http://jira.opensymphony.com/secure/ViewIssue.jspa?key=WW-79

Currently, if a ww:property tag doesn't have a body, it prints the value
of the value attribute, or "." if no value is provided. In the case of
setting a pageContext attribute (a bodyless tag), this isn't what you
want.

diff attached.

--Erik
<BasicPropertyTag.java.diff>


-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to