[Webmacro-devel] Error handling improvement in WMServlet

[Marc P. <ma...@an...>]

Hi,

Ugh I am having some fun :(

I have a template spewing a PropertyException. I can solve the cause of it 
later, but right now I need to trap it.

Using WMServlet as your base class I think this is impossible. Basically, 
all my error handling produces an email sent to an admin address. Except 
for template errors, because I can't trap PropertyException etc.

The WMServlet.error method is final, so I cannot override it. Damn those 
final methods in WMServlet. They've dogged us for a long time. Why don't we 
get rid of most/all of them, instead of just doGet (a recent modification, 
for example).

My options are:

1. Use my own modified build of WM (not desirable)

2. Write a custom evaluation handler that does the emailing (also not 
desirable)

3. Abandone extending WMServlet and encapsulate a WM instance myself.

None of these are filling me with glee right now! How easy it would have 
been to just override error() and do my emailing in there.

Anyone else think removing these final modifiers on many of the methods in 
WMServlet is a good idea?

Marc