Use 'publication' view name for exception views in ZopePublication

[Steve Alexander]

At present, in ZopePublication, when an exception reaches the Publication component, the default view on an exception is rendered.

This should be changed so that the 'publication' view on an exception is rendered. Views registered for 'index.html' on exceptions should be changed to be registered for 'publication' instead.

This change may affect non-core products so an announcement should be made on zope3-dev.

This change is important because there will be other uses for views on exceptions when the next round of forms/widgets work is undertaken.

[Stephan Richter (srichter)]

Status: Pending => Rejected

I think now that we have "providing" interfaces for views this is a non-issue, and looking up the default view for an exception when it occurs seems for me the right thing to do.

If someone objects to this conclusion, feel free to reopen the bug.

[Jim Fulton (jim-zope)]

Status: Rejected => Accepted

 Supporters added: jim

The ability to specfy provided interfaces makes this no less an issue. Rather than a different name, perhaps a different interface should be used.

Still, it's unclear to me what other reasons there would be
to publish views on exceptions.

So, for example, we might pick a different interface (than
Interface) for things that are published. Then we would use this interface for exceptions. In this case, I think I would use an unnamed view. Perhaps we should pick a marker interface for the special case of handling errors.

[Fred Drake (fdrake)]

Changes: submitter email, edited transcript, new comment

Fixed three typos in other comments.

[Jim Fulton (jim-zope)]

The issue remains. I agree that we should look up a specific
interface, however, I suspect that it shouldn't be the
same interface used for pages, although I'm not sure. This
needs to be part of a refactoring of the application-publication apis that I'd love to see for 3.4.