The correct approach is to create a customized implementation of org.apache.tapestry.engine.state.StateObjectFactory
This can be contributed into the tapestry.state.ApplicationObjects configuration point. Your implementation should probably be a HiveMind service that can have anything injected into it; it can create your ASO, setting properties and/or invoking a constructor to pass services into the ASO. On 10/4/05, Dan Adams <[EMAIL PROTECTED]> wrote: > Does anyone know how to inject a service into an ASO? I'm really havin > some trouble with this. > > -- > Dan Adams > Software Engineer > Interactive Factory > > > --------------------------------------------------------------------- > 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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
