[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3030) Don't be so hostile to alternate JPA providers when attempt is made to use manual flush mode
Dan Allen (JIRA)
jira-events at lists.jboss.org
Fri May 23 01:45:09 EDT 2008
Don't be so hostile to alternate JPA providers when attempt is made to use manual flush mode
--------------------------------------------------------------------------------------------
Key: JBSEAM-3030
URL: http://jira.jboss.com/jira/browse/JBSEAM-3030
Project: Seam
Issue Type: Bug
Affects Versions: 2.1.0.A1, 2.0.2.GA
Reporter: Dan Allen
Assigned To: Dan Allen
Fix For: 2.0.2.SP1, 2.1.0.BETA1
Attachments: JBSEAM-3030-branch20-v1.txt, JBSEAM-3030-trunk-v1.txt
Right now, alternate JPA providers (such as TopLink) are *unusable* in Seam. This is because, prior to the render response phase, Seam attempts to put the touched persistence contexts into manual flush mode. This trickles down to a call to setManualFlushMode() on the component returned by PersistenceProvider.instance(). The generic implementation (PersistenceProvider) throws an exception when this method is called.
Throwing an exception here is overkill and hostile. I propose a log warning message, which would allow the developer to tune the log settings to hush it, or if they really don't like the log message, they can provide their own implementation. But at least the damn thing will be usable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the seam-issues
mailing list