We are using TaglibHelper for more than 1.5 years now. It has always been mainly my colleagues who are writing the taglibs, and they have quite many times come to me with a problem they couldn't solve. The problem is then that in most cases the error message was just an error in the generated perl code. It then always takes (for me who didn't write the code :) quite some patience to find out what's wrong. This makes TaglibHelper seem quite fragile.
Today my colleague got such an error because he misspelled the taglibfunction definition in his taglib. (See example below). Seems like having a tag <mytaglib:myfunction/> in an .xsp file without a corresponding definition in @EXPORT_TAGLIB breaks TaglibHelper.
Shouldn't TaglibHelper stop building code right when it encounters a tag that has no definition?
The problem is caused by the fact that TLH can't know if a particular tag is a function tag or an attribute/parameter tag. This could probably be handled a lot better than it is right now, it's just a matter of programming after all.
Matt.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
