There has been a lot of class reorganization going on and one way of minimizing the effect on user-developers has been to leave stubs in place of the moved file. However Turbine classes are updated to use the new location, so if a user has overridden a method that uses a moved class, the method is no longer overridden. It is possible that the user will not even suffer runtime exceptions due to the changes, but will get unexpected results. A small example: o.a.t.security.db.DBSecurityService has a method getGroups(o.a.t.services.db.util.Criteria) I overrode that back when it was getGroups(o.a.t.util.Criteria) Now the two method signatures are different, so my method never gets called. So it would seem that stubs may not be such a big help to a developer trying to upgrade to a newer version of Turbine. So should Turbine continue to point to the stubs? Should the stubs exist at all? john mcnally --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
