(cf: http://wiki.apache.org/jakarta-taglibs/Standard_1%2e1%2e3 )

There are 13 issues left open now:

Performance:

17700 - Someone wants caching for MessageFormat. This one would be
tricky I think as it would need a proper pooling mechanism to exist.
One avenue we could take is to allow for extension here via a
StandardTaglibPool interface that people could implement.

27717 - x:forEach is slow. There are various solutions here, Kris was
involved back in 2004 so maybe you have more thoughts on which
direction we should take here Kris?

32311 - Someone wants Calendar.getInstance caching. Same issue as
17700 basically, though it would be less damaging to implement dumb
caching here (I think) as Calendar patterns are _much_ more likely to
repeat than message formats. We could use the same StandardTaglibPool
extension interface here, I'm pretty sure both cases are a
lookup(String pattern) approach.

Leaks:

17388 - Various closing issues. Looks like you've got this one taken
care of Kris. I hadn't clicked it was this issue when I suggested unit
tests - might be painful to try and recreate this stuff so I'm +1 to
charge on without trying to test for this.

25623 - Potential memory leak in tag closing in c:forEach. I think we
should go with Justyna's reply here and WONTFIX it. However....

33934 - Similar to the last one. Tag closing in c:set. Tim Burrell
suggests a general approach that would help with 25623 too (by the
sounds of it). Thoughts on these two?

31789 - Interesting one - leak in ELEvaluator. Are you still around
Felipe? Seems that this is an issue where we already have a dumb
pooling strategy and it needs to improve. Anyone have thoughts on
solutions?

34896 - Leak in TransactionTagSupport. Looks like a problem, I suggest
removing the conn = null; line in init();.

Misc:

39438 - Change to use VariableResolver. I've not looked into this one
yet - it seems a valid request but I don't know if we can just change
things and have it still work.

31084 - Bug in formatting. Anyone here used the LocalizationContext
setting? It seems pretty simple in that "localtext" isn't applicable
as a String as far as I can tell, so it must be a reference to a
LocalizationContext object. The code looks good in BundleSupport for
that, so I can only assume there was a configuration error in setting
that up. I'm +1 for WONTFIX, but not experienced with this feature.

22765 - first()/last() not working as desired. Deep in the XPath
innards - suggest we a) make a unit test that WARNs rather than fails,
b) FAQ it, and c) leave it open. Should probably do a) for 33032 too.

39195 - JBoss specific bug. Seems right and an easy fix, though I
disagree with the original posters fix. Seems to me that an empty
enumeration should be returned. Thoughts?

41221 - Fix source headers. I'll take care of this when the time comes.

Any opinions very much appreciated,

Hen

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

Reply via email to