Induction

New support for error handlers. A new @<error-to-class-map>@ directive in the config XML to configure error handlers. New high-performance template output buffering. The output of a template is sent to the client only if the template completes without errors. Nothing is written to the client for a template that has errors, so users no longer see the messy stack trace generated by a templating engine. An error handler now has more options, such as returning a redirect or error code to the client (since no writing was started on the response).

Injecting the ControllerResolver.Resolution or ViewResolver.Resolution in a request interceptor incorrectly threw an exception if resolution objects were null; this has been fixed. The code now throws an exception when an attempt is made to access a session scope model from a context in which no session is available; previously this caused a NullPtrEx (in the ModelPool class).

Powerful new support was added for request interceptors backed by the same zero-config dependency injection used throughout Induction. ShortURL resolvers were enhanced to support a new <class-replace> directive in the <url-to-class-map> section of the Induction configuration. For example, this directive can be used to map a hyphen in a URL to, say, an underscore in a controller/view class name. Two minor bugs in version 1.2.0b were fixed.

This release supports direct mapping of URLs to views. Previously views could only be activated by controllers. It also includes powerful clean URL support via new regex-driven resolvers, support for controllers to return a view type in addition to the previous support for returning a view instance, a new <include-config ...> directive in the Induction configuration XML, a new <init-on-startup ...> directive to support initializing application scope models on startup, and enhancements to expand access to system level objects in controllers and views for use by specialized applications.