A lot of the reasons for sub-classing BaseEngine no longer apply; protected methods you used to override no longer exist. To get the same kind of effect, you would now override the implementation of services dedicated to handling exceptions (uncaught, stale link, stale session).
The APIs for engine services also changed quite a bit, and they are now true HiveMind services, as well as being engine services. The configuration of engine services is now done in the HiveMind module descriptor. The Workbench has examples of this. On Apr 11, 2005 8:01 PM, Andy Pahne <[EMAIL PROTECTED]> wrote: > > > > What's going to happen with extending BaseEngine and EngineServices. I > utilize both a lot and I am currently starting a new application. > > I had a look at all the Wiki pages about 3.1, but besides the > refactorings (new names, new package names), I could not find anything. > > Andy > > > Howard Lewis Ship wrote: > > It won't be perfectly backwards compatible, but I'm hoping the manual > > intervention will be limited to advanced uses: extending BaseEngine, or > > adding engine services. > > > > On Apr 11, 2005 5:17 PM, Phil Zoio <[EMAIL PROTECTED]> wrote: > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
