|
From: Craeg S. <cs...@ar...> - 2003-04-16 22:54:52
|
That is a good question. It might be a historical detail. I can't think of a good reason, so it probably is better to be more standard. I guess its quite analogous to the situation when your Page Template doesn't compile. It throws an exception as soon as it is accessed. OK, let's simplify and eliminate the guts :) --Craeg > > Pretending to be the devil's advocate: why would you _not_ want > transform to raise an exception? If transformation fails, there is most > likely an error in your configuration or in your XSLT script. Also, Zope > provides a facility to customize the display of error messages > (standard_error_messages). Why should XSLTMethod try to go around that > and display the error message in plain text, or even worse, display > nothing. This makes debugging very hard. > > > Perhaps transformGuts() should instead be called > > transformOrRaiseException() or something? It might be > > simply a case of poor naming... > > Looks like it... > > > Is there a Zope3 convention that might be helpful here? > > Well, yeah. Exceptions are defined in the interface modules and are > being raised when appropriate. This is the convention ;) > > Philipp |
