commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (JELLY-13) Jelly should throw an exception if an unknown tag is used in a TagLibrary
Date Sun, 12 Sep 2004 22:02:38 GMT
The following comment has been added to this issue:

     Author: Hans Gilde
    Created: Sun, 12 Sep 2004 3:00 PM
Yes, it would be optional and entirely controlled by the library.

There are two cases under which XML is output: 

1) the parser can't find a tag library for the namespace of the tag.
2) the tag library doesn't find a tag for the element name and returns null to the parser.

In both cases, the parser creates a text script with the contents of the tag.

Each library has the option to, rather than return null, throw an exception (causing a parse
failure) or return a Tag that throws an exception at runtime (causing a runtime failure).

In fact, rather than having the parser create a text script when the tag lib returns a null
tag, the library itself could return a Tag that outputs the XML.

I'm actually just starting to use maven myself, what do maven users output as XML? Sorry to
be so naive.

View this comment:

View the issue:

Here is an overview of the issue:
        Key: JELLY-13
    Summary: Jelly should throw an exception if an unknown tag is used in a TagLibrary
       Type: Improvement

     Status: Open
   Priority: Major

    Project: jelly
             core / taglib.core
   Fix Fors:

   Assignee: james strachan
   Reporter: james strachan

    Created: Tue, 12 Nov 2002 5:24 AM
    Updated: Sun, 12 Sep 2004 3:00 PM

Many tag libraries only have a strict number of tags defined. So default behaviour for these
libraries should be that if a typo is made on a tag name, then an exception is thrown.

Some libraries, like the Ant library, are more soft-coded and will try their best to instantiate
whatever they are given. However the default case is typically known at compile time.

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