Hi
I don't want to change anything that will cause a backward compatibility
problem. All options/annotations will work the way they used to, just, if an
annotation, say @Named("my_sf") is found, the options/annotations will
become specific to that session factory.
@Named("my_second_sf")
@Inject
private Session session;
or
@Named("my_second_sf")
@CommitAfter
Yes, in case of commit, we have to consider a situation where in we want to
commit two transactions from two different session factories. In that case
there is no simple solution. We may then have to check out jta integration
so something.
regards
Taha
On Wed, May 11, 2011 at 1:45 PM, antalk <[email protected]> wrote:
> I think it is a good 'partial' solution. You still have to implement the
> @CommitAfter and @PageActivation annotations for your module.
>
> At least you could mention your blog entry in the JIRA issue so that it
> does
> not get lost.
>
> Antal
>
> --
> View this message in context:
> http://tapestry.1045711.n5.nabble.com/Regarding-Multiple-Database-Support-in-tapestry-hibernate-module-tp4381212p4386751.html
> Sent from the Tapestry - Dev mailing list archive at Nabble.com.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
