[Bug 54338] Class cast exception in tagPlugin Set generated code

2013-01-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=54338 Mark Thomas changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 54338] Class cast exception in tagPlugin Set generated code

2013-01-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=54338 --- Comment #4 from Mark Thomas --- It is not a question of what is appropriate or what is best, the JSTL specification requires that an EL coerce is used. I'm looking at this now. The test case is going to need some work. -- You are rec

[Bug 54338] Class cast exception in tagPlugin Set generated code

2013-01-04 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=54338 Mark Thomas changed: What|Removed |Added Attachment #29786|application/octet-stream|text/plain mime type|

[Bug 54338] Class cast exception in tagPlugin Set generated code

2013-01-03 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=54338 --- Comment #3 from Sheldon Shao --- Yes. The problem isn't only from primitive types. Perform a "coerce" is a better choice. (In reply to comment #2) > Is it appropriate to perform a "coerce" instead of a simple cast? (I don't > know whe

[Bug 54338] Class cast exception in tagPlugin Set generated code

2013-01-02 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=54338 --- Comment #2 from Christopher Schultz --- Is it appropriate to perform a "coerce" instead of a simple cast? (I don't know whether the spec covers this case). If the only problem is primitive types, I think this can be solved without the c

[Bug 54338] Class cast exception in tagPlugin Set generated code

2012-12-21 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=54338 --- Comment #1 from Sheldon Shao --- Created attachment 29787 --> https://issues.apache.org/bugzilla/attachment.cgi?id=29787&action=edit Patch for Set.java -- You are receiving this mail because: You are the assignee for the bug. -