> Additionally, it would provide an interesting research ground > for the JSTL people and provide some way in which Users can > really force home the fact that the <c:systemExit/> tag is essential.
You might laugh at this, but I've worked with high priced consultants from well respected companies who always managed to do something like System.exit(0); in a Servlet. :-) Or, better yet, the certified "web developer" from a 3-letter acronym company (not IBM) who liked to write all content to a temporary file before sending it back to the client. > We set things up for it last week, the developer list has a > chunk about it in the mail archives. Tim's put a bit of code > in there and Glenn and I have setup the infrastructure for > it, but I'm focusing on String 1.0.1 first at the moment. Unstandard was Henri's idea. So far it has been seen as a place to accomplish two things: 1. Provide a mechanism to "implement" around some issues in JSTL 1.0, 2. Provide a tag library in which people can explore the possibilities for EL tags not available (method invocation, sorting, etc.). We've got two tags so far, which provide *very* incremental additions to JSTL 1.0, and they address features that EL lacks. Specifically, the ability to compare two strings ignoring case, and an "instanceOf" tag. unstandard is very green and fully undocumented. I'd give it a few weeks to boil. -------- Tim O'Brien > -----Original Message----- > From: Henri Yandell [mailto:[EMAIL PROTECTED]] > Sent: Friday, February 14, 2003 11:20 AM > To: Tag Libraries Users List; [EMAIL PROTECTED] > Subject: RE: Problem with "empty" key word on a collection. > > > > It's mainly a set of ideas at the moment. People come to this > list a lot asking for features in JSTL. Rather than send them > away unsatisified, the idea is to implement them in the > Unstandard taglib and have happy users. > > We set things up for it last week, the developer list has a > chunk about it in the mail archives. Tim's put a bit of code > in there and Glenn and I have setup the infrastructure for > it, but I'm focusing on String 1.0.1 first at the moment. > > Website to come. > > Hen > > On Fri, 14 Feb 2003, Jerome Jacobsen wrote: > > > I'll bite. What's the Unstandard Taglib? Is there a website for > > this? > > > > > -----Original Message----- > > > From: O'brien, Tim [mailto:[EMAIL PROTECTED]] > > > Sent: Friday, February 14, 2003 11:45 AM > > > To: 'Tag Libraries Users List' > > > Subject: RE: Problem with "empty" key word on a collection. > > > > > > > > > > -----Original Message----- > > > > From: James Cook [mailto:[EMAIL PROTECTED]] > > > > Sent: Friday, February 14, 2003 8:17 AM > > > > To: Tag Libraries Users List > > > > Subject: Re: Problem with "empty" key word on a collection. > > > > > > > > > > > > > > > > On Thursday, February 13, 2003, at 05:04 PM, Pierre > Delisle wrote: > > > > > > > > > The change that Jeff is proposing, although of > interest, would > > > > > unfortunately break compatibility with the spec. (sorry > > > > guys, but the > > > > > Expert Group ain't perfect) > > > > > > > > > > > > > Why would extending the empty keyword to support > Collections break > > > > compatibility with the spec? > > > > > > > > > > Modifying the "empty" keyword to support Collections > doesn't break > > > anything per se, but it does exceed the definition of "empty" in > > > Section A.3.8 in the > > > JSTL 1.0 specification. I believe that the JSPA talks about > > > adhering to the > > > spec in independent implementations of a JSR. > > > > > > I'm very uninterested in starting a flamewar about JCP, but it is > > > important to note that adhering to the spec allows for > portability > > > over multiple implementations of JSTL and EL. > > > > > > I've already submitted a patch to commons-jexl to make > "empty" work > > > with Collection, but it won't be of any help to anyone using the > > > current Standard Taglib and JSTL 1.0. I think this is what the > > > nascent Unstandard Taglib what meant for, providing functionality > > > for little bits of functionality that might have been > inadvertently > > > overlooked by the first rev of JSTL in a > > > way that doesn't conflict with existing JCP specs. > > > > > > -------- > > > Tim O'Brien > > > > > > > > > > > > > > > ------------------------------------------------------------------ > > > > --- > > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > > - > > > To unsubscribe, e-mail: > [EMAIL PROTECTED] > > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
