Except for the change of exception type (JellyTagException vs
SAXException), I see no real reason to have such instead of inserting
this validation within doTag.
Do you see one Marco ?
As for the exception types, we could maybe ease up propagation with
JellyException.asSAXException() (for use within doTag) and new
JellyException(SAXException) (for use in others, which would undress a
wrapped jelly-exception). Indeed, these long wraps of exceptions as
dumped to console sometimes, e.g. by maven, are quite ugly.
An alternative would be to have JellyException be a SAXException... not
sure it's a good idea but it would ease up things.
paul
Marco Tedone wrote:
May I suggest to add the method:
public void validate(XMLOutput output) throws JellyTagException to the
Tag interface? I'm writing some tags, and I realize that for the quite
totality of them I need to validate some data (like the attributes).
It would be nice if the Tag interface defined such method which could
be implemented by TagSupport without doing actually any behaviour, and
then concrete Tags could override the method providing a custom
implementation.
Marco
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
