Uploaded image for project: 'Seam 2'
  1. Seam 2
  2. JBSEAM-3030

Don't be so hostile to alternate JPA providers when attempt is made to use manual flush mode

    Details

    • Affects:
      Compatibility/Configuration
    • Estimated Difficulty:
      Low

      Description

      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.

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  dan.j.allen Dan Allen
                  Reporter:
                  dan.j.allen Dan Allen
                • Votes:
                  2 Vote for this issue
                  Watchers:
                  3 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Time Tracking

                    Estimated:
                    Original Estimate - 5 minutes
                    5m
                    Remaining:
                    Remaining Estimate - 5 minutes
                    5m
                    Logged:
                    Time Spent - Not Specified
                    Not Specified