Hi, We have been trying to modify tapestry to allow us to - Override templates at runtime (e.g. load them from a CMS) - Override templates at runtime DEPENDING on page data
We have pretty much achieved this but only by customising Tapestry Core to a degree that is going to make it hard to maintain. Has anyone got any suggestions as to what we could do to make this easier? We have had to customise the some IOC services - these aren't too hard to override. The ones we are really finding hard to deal with are the follow that don't appear to be services but are quite tightly linked in - org.apache.tapestry5.internal.services.ComponentEventDispatcher - org.apache.tapestry5.internal.services.MessagesSourceImpl As a suggestion :) things that will make overriding services easier would be - Some way to replace contributions (as opposed to just add) - Some way to replace listeners to the event hubs - Always use services - Try and make services friendly for extension (BTW I know this is all our fault for messing around with the internals of tapestry) Ben Gidley www.gidley.co.uk b...@gidley.co.uk
