Ha ha, I am a committer. The reason I have not committed it is that tapestry-hibernate is in common use and I would like to hear from everybody before committing any changes
regards Taha On Nov 15, 2011, at 4:07 PM, Ernesto Arroyo wrote: > I think is not a good idea to have "forks" > > Maybe better to contact the commiters to get this effort added to the trunk > > > ________________________________ > De: Taha Hafeez Siddiqi <tawus.tapes...@gmail.com> > Para: Tapestry development <dev@tapestry.apache.org> > Enviado: martes 15 de noviembre de 2011 11:30 > Asunto: Multiple database support > > Hi > > I have cloned tapestry project at > > https://github.com/tawus/tapestry5 > > and have added multiple database support. > > It is almost fully compatible with the previous version when using a single > database except for a few things > > 1) HibernateConfigurer has changed > > public interface HibernateConfigurer > { > /** > * Passed the configuration so as to make changes. > */ > void configure(Configuration configuration); > > /** > * Factory Id for which this configurer is meant for > */ > Class<? extends Annotation> getMarker(); > > /** > * Entity package names > * > * @return > */ > String[] getPackageNames(); > } > > > 2) There is no HibernatePackageEntityService and packages can be added using > HibernateConfigurer. > > > For multiple database, a marker is to be used for accessing Session or > HibernateSessionManager > > @Inject > @XDB > private Session session; > > @Inject > @YDB > private HibernateSessionManager sessionManager; > > @XDB > @CommitAfter > void myMethod(){ > > } > > > Would really appreciate your suggestions /comments > > regards > Taha --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
