thanks, as we've mentioned this is a "feature" outside of transaction scope and you really need to know the potential consequences by using it. other than that i dont think its many issues, if you find any let us know
yes, the naming of the jira is not ideal, but the initial issue was targeted for collections only.
and yes, we will document this on hibernate.org, but i dont think we'll promote its usage since its not a feature we really think people should use without knowing the possible consequences.
thanks, as we've mentioned this is a "feature" outside of transaction scope and you really need to know the potential consequences by using it. other than that i dont think its many issues, if you find any let us know
yes, the naming of the jira is not ideal, but the initial issue was targeted for collections only.