On 22.10.2008, at 14:31, Oliver Scheel wrote:
I have a simple custom error page with a form inside to send an
error mail with user comments. When the exception occurs inside a
form WO complains about a nested form and the error form tag is not
generated. The error page is called via handleException() in the
application class.
To solve it, I do (in handleException):
context.setInForm(false);
Is this the intended way?
This is a Wonder thing (not necessarily a bug). Wonder tracks whether
the current context is inside a form. So if an exception happens
within a form rendering, the current context thinks it is inside a
form and you probably use the given context to return your error page
- this has still the not closed form handling.
I think what you are doing is good enough to solve the problem. But
I'm not sure about unintended side behaviour.
It might be better to create a new context with the current request
and use that to create your error page. Not sure whether that is the
best solution. As long as what you do works, I don't see the need to
change it.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
