I think the reasoning might be because of how simple / easy it is to replace StateObjectFactory itself. Perhaps this area could use some work though. Not sure.
On 11/28/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
I was wondering why the tapestry.state.StateObjectContribution does not support the use of the more feature rich factory services available in hivemind via the <invoke-factory> element? Is this to avoid muddling the ASO scope with the service model associated to a service point. Carlos --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
