Uploaded image for project: 'Application Server 7'
  1. Application Server 7
  2. AS7-1273

Applications (or their libraries) containing persistence units with the connection defined inline via properties cause deployment failure.

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • 7.0.2.Final
    • 7.0.0.Beta1, 7.0.0.Final
    • JPA / Hibernate
    • Hide

      Deploy JBPM5 gwt-console-server war, it has jbpm-human-task as a library which contains such a persistence.xml

      Show
      Deploy JBPM5 gwt-console-server war, it has jbpm-human-task as a library which contains such a persistence.xml
    • Hide

      Editing the offending persistence unit to use a <non-jta-data-source> (which you have created in AS 7) and have transaction-type="RESOURCE_LOCAL" works around the problem but its not really practical for most users.

      Show
      Editing the offending persistence unit to use a <non-jta-data-source> (which you have created in AS 7) and have transaction-type="RESOURCE_LOCAL" works around the problem but its not really practical for most users.

    Description

      Persistence units defined as follows https://github.com/droolsjbpm/jbpm/blob/master/jbpm-human-task/src/main/resources/META-INF/persistence.xml causes deployment to fail due to the fact that no <jta-data-source> or <non-jta-data-source> is present, but none should be present as the datasource has been defined via the properties.

      Attachments

        Activity

          People

            smarlow1@redhat.com Scott Marlow
            justinwyer_jira Justin Wyer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: