Thanks for your replies. > Firstly, I'm not familiar with Cayenne.
Well, I've been working with Tapestry and Cayenne for only a few months now, so I'm not that familiar with it, either. > Secondly, I'm not 100% sure that this is a good idea. You mean passing the value as a parameter is not a good idea? Or something else? (sorry, I'm not a native speaker) > With that in mind, does Cayenne provide a hook to intercept object > creation? > Can you decorate some form of CayenneDataObjectFactory? If you can, > there's > nothing to stop you reflectively iterating the DataObject fields and > populating any fields annotated with @Symbol yourself. I'm not sure about this. In the beginning I used BeanEditForm and let Tapestry create the objects, then did cayenneObjectContext.registerNewObject(Object object); After I ran into some other problems I switched to Form mostly and created an object with cayenneObjectContext.newObject(persistentClass); then set the fields of the object. > NB. After tapestry is initialized, an instance of Registry is available > as a servlet context attribute under the key > TapestryFilter.REGISTRY_CONTEXT_NAME. Hm, I have to dig around some more to find out if there's a way to access the servlet context from cayenne. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
