On Thu, Apr 07, 2005 at 10:06:38PM +0200, Philipp von Weitershausen wrote: > Albertas Agejevas wrote: > >Currently, in the generic case, Zope 3 raises a ComponentLookupError > >in zope.app.publication.http line 74, and a 500 response is served. > > I can't find that particular line of code. Are you talking about > HTTPPublication.callObject where it looks up the view > (zapi.getMultiAdapter) which might result in a ComponentLookupError in > case the adapter can't be looked up?
Sorry, I had a dirty sandbox. Yes, I was talking about that line. > Well, maybe that should change then. These views could easily raise > MethodNotAllowed, couldn't they? If they can't find the necessary > adapters, the their functionality is obviously not available and they > should raise an appropriate error. They could, but the problem is with introspection of which methods are availble, for the mandatory Allow: header. Albertas _______________________________________________ Zope3-dev mailing list Zope3-dev@zope.org Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com