commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (JELLY-150) j:forEach tag not properly using varStatus attribute
Date Mon, 04 Oct 2004 19:40:32 GMT
The following comment has been added to this issue:

     Author: Ben Anderson
    Created: Mon, 4 Oct 2004 12:40 PM
The interface is defined here:

There was some discussion following this on the mailing list. Personally, I don't see why
it can't go in javax.servlet, but it should be fine to put it in some other package.  Does
your "unified format" comment pertain to the diff file I posted?  This is the first patch
I've ever submitted.  I wasn't sure what to do with the new files, so I appended them to that
file.  I'm assuming this is not the way to do it, but I didn't know how.  If someone will
let me know how I'm supposed to do it, I'll resubmit the correctly formatted file.

View this comment:

View the issue:

Here is an overview of the issue:
        Key: JELLY-150
    Summary: j:forEach tag not properly using varStatus attribute
       Type: Bug

     Status: Unassigned
   Priority: Major

    Project: jelly
             core / taglib.core

   Reporter: Ben Anderson

    Created: Fri, 24 Sep 2004 4:57 AM
    Updated: Mon, 4 Oct 2004 12:40 PM
Environment: win2k / cygwin

According to the jstl specification 1.1, the varStatus attribute of the forEach tag should
create a variable with type javax.servlet.jsp.jstl.core.LoopTagStatus.  Currently a variable
is set with type Integer which contains the index of the current iteration.  I created a test
case (I don't think any existed for forEach) that demonstrates this.  I also began making
the fix, but it doesn't fully work.  I am submitting my patch along with the test cases. 
The comments I placed in the code should be enough to tip someone off as to why it's not working
(I hope).  I am relatively new to jelly (been using the standard taglibs for awhile) and have
never opened the source before.  I am willing to complete the patch, but will probably need
some guidance because I messed with it for awhile before determing I couldn't complete without
some help.  Thanks! :-)

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message