[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3030) Don't be so hostile to alternate JPA providers when attempt is made to use manual flush mode

Mathias Walter (JIRA) jira-events at lists.jboss.org
Thu Jun 26 11:53:58 EDT 2008


    [ http://jira.jboss.com/jira/browse/JBSEAM-3030?page=comments#action_12419077 ] 
            
Mathias Walter commented on JBSEAM-3030:
----------------------------------------

Is there any progress on this issue?
I've read the discussion about setRenderFlushMode()  and setManualFlushMode() in the seam-dev mailing list.

I'm using EclipseLink with Seam and set

	<core:init debug="true" transaction-management-enabled="false"/>
	<transaction:no-transaction/>

Now, my dataTables won't work anymore and I get the UnsupportedOperationException: You must use Hibernate to use Manual Flush Mode.

> 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
>          Components: Platform interoperability
>    Affects Versions: 2.0.2.GA, 2.1.0.A1
>            Reporter: Dan Allen
>         Assigned To: Dan Allen
>             Fix For: 2.1.0.BETA1
>
>         Attachments: JBSEAM-3030-branch20-v1.txt, JBSEAM-3030-trunk-v1.txt
>
>   Original Estimate: 5 minutes
>  Remaining Estimate: 5 minutes
>
> 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