Uploaded image for project: 'WildFly'
  1. WildFly
  2. WFLY-9132

Applications won't deploy if their persistence.xml have multiple persistence units

    XMLWordPrintable

Details

    • Bug
    • Resolution: Won't Do
    • Major
    • None
    • 10.1.0.Final
    • JPA / Hibernate
    • None
    • Hide

      Build application which has multiple persistence-unit in the persistence.xml
      Deploy on EAP 6.4
      Notice that application deploys
      Deploy on Wildfly 10.1.1
      Notice that application fails to deploy, with message indicating that each @PersistenceContext be tagged with 'unitName'

      Show
      Build application which has multiple persistence-unit in the persistence.xml Deploy on EAP 6.4 Notice that application deploys Deploy on Wildfly 10.1.1 Notice that application fails to deploy, with message indicating that each @PersistenceContext be tagged with 'unitName'

    Description

      Applications won't deploy if their persistence.xml have multiple persistence units. This was not a problem with EAP. Now, Wildfly requires that each @PersistenceContext have a 'unitName' parameter. WIth EAP 6.4, if a @PersistenceContext did not have a 'unitName' parameter, then the default PU was used. By requiring that @PersistenceUnit have 'unitName', developers are forced to unnecessarily bind Java code to configuration.

      Attachments

        Activity

          People

            smarlow1@redhat.com Scott Marlow
            rmoyersrfd Bobby Bassman (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: