Oct 26th, 2009, 01:51 PM
User addon/plugins and existing behavior
I'm looking forward to RC3 with the ability to write your own addon as demonstrated at Springone. I have some questions on how the plugins will work with existing roo behavior.
For example, I added two Jira tickets, one for the ability to change toString and the other for SoftDelete. If I wanted to implement these as addons, how would they interact with the core roo addons.
With those two examples, the toString would effectively replace the roo toString and provide a nicer web facing toString method when the system goes to production. Would I have to remove the Roo toString addon?
For the softdelete, it would add a field to the entity and also override the delete mechanism. It would also need to be aware of any finders so that by default it happened in the background. In this case, it would work alongside the current entity code instead of replacing it. Would I have to register the softdelete addon to watch for the metadata changes in the entity addon?