Hi, I am not using tapestry, but my application uses daos in the way you describe. If you don't need or don't care for declarative transaction control, there is no need to use HiveTranse. Just implement your DAOs as hivemind service points, and have them injected (with auto wiring) on the classes that need them. I prefer defining one interface for each DAO , but I don't think it's required by hivemind 1.1 any longer.
Regards, - Juliano. John Coleman wrote: >We have a tapestry project where POJOs are directly using DAOs. > >Obviously we would like to implement these DAOs as services through >hivemind, and ideally inject the service into the POJOs, rather than look >them up. > >Has anyone a simple example of this, should we use hivetranse? > >TIA >John > > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
