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.0.2.GA, 2.1.0.A1 Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.1.0.BETA1, 2.0.2.SP1 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.

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.1.0.A1, 2.0.2.GA 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.

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, NonHibernatePersistenceProvider.java 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.

Don't be so hostile to alternate JPA providers when attempt is made to use manual flush mode -------------------------------------------------------------------------------------------- Key: JBSEAM-3030 URL: https://jira.jboss.org/jira/browse/JBSEAM-3030 Project: Seam Issue Type: Bug Components: Platform interoperability Affects Versions: 2.0.2.GA, 2.0.3.CR1, 2.1.0.A1, 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.0.3.CR2, 2.1.2.CR1, The future Attachments: JBSEAM-3030-branch20-v1.txt, JBSEAM-3030-trunk-v1.txt, NonHibernatePersistenceProvider.java 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.

Don't be so hostile to alternate JPA providers when attempt is made to use manual flush mode -------------------------------------------------------------------------------------------- Key: JBSEAM-3030 URL: https://jira.jboss.org/jira/browse/JBSEAM-3030 Project: Seam Issue Type: Bug Components: Platform interoperability Affects Versions: 2.0.2.GA, 2.0.3.CR1, 2.1.0.A1, 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.0.3.CR2, 2.1.2.CR1, The future Attachments: JBSEAM-3030-branch20-v1.txt, JBSEAM-3030-branch20-v2.txt, JBSEAM-3030-trunk-v1.txt, JBSEAM-3030-trunk-v2.txt, NonHibernatePersistenceProvider.java 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.

Don't be so hostile to alternate JPA providers when attempt is made to use manual flush mode -------------------------------------------------------------------------------------------- Key: JBSEAM-3030 URL: https://jira.jboss.org/jira/browse/JBSEAM-3030 Project: Seam Issue Type: Bug Components: Platform interoperability Affects Versions: 2.0.2.GA, 2.0.3.CR1, 2.1.0.A1, 2.1.1.GA Reporter: Dan Allen Assignee: Dan Allen Fix For: 2.0.3.CR2, 2.1.2.CR1, The future Attachments: JBSEAM-3030-branch20-v1.txt, JBSEAM-3030-branch20-v2.txt, JBSEAM-3030-trunk-v1.txt, JBSEAM-3030-trunk-v2.txt, NonHibernatePersistenceProvider.java 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.