JBoss Enterprise Application Platform 4 and 5
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8084

Update farmed Application Deployment (EAR/WAR) results in org.jboss.seam.RequiredException: @Out attribute requires non-null value: updateBackingContentAction.packageType

    Details

    • Affects:
      Release Notes
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      1. Undeploy first version and deploy second one as new;

      Show
      1. Undeploy first version and deploy second one as new;
    • Release Notes Text:
      Hide
      When using the administration console to update an application (EAR or WAR) deployed to the farm directory, the target application would be removed from the farm directory and deployed to the deploy directory. This will result in the farmed attribute value being null when the administration console UI expected it to be set to true. This issue has been resolved by ensuring that existing applications that are marked as farmed continue to be deployed in the farm directory which ensures <literal>farmed=true</literal> on the updated deployment.
      Show
      When using the administration console to update an application (EAR or WAR) deployed to the farm directory, the target application would be removed from the farm directory and deployed to the deploy directory. This will result in the farmed attribute value being null when the administration console UI expected it to be set to true. This issue has been resolved by ensuring that existing applications that are marked as farmed continue to be deployed in the farm directory which ensures <literal>farmed=true</literal> on the updated deployment.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW
    • Similar Issues:
      Show 9 results 

      Description

      1. Setup an EAP instance;
      2. Deploy an application (EAR/WAR) to the above instance using "Deploy Farmed" option;
      3. Verify that the application is properly deployed;
      4. Update the application using the same EAR/WAR (From admin-console, expand and select the deployed EAR/WAR, select it's Content tab and then click Update)

      Actual Result:
      Deployment fails with the following Exception:

      16:49:35,946 ERROR [UpdateBackingContentAction] ResourceType[id=0, category=Platform, name=Linux, plugin=Platforms] has no associated creation package type.
      16:49:35,999 ERROR [Exceptions] handled and logged exception
      javax.el.ELException: org.jboss.seam.RequiredException: @Out attribute requires non-null value: updateBackingContentAction.packageType

      Expected Result:
      The updated deployed application is properly deployed and no exception is thrown.

        Issue Links

          Activity

          Hide
          RH Bugzilla Integration
          added a comment -

          John Mazzitelli <mazz@redhat.com> changed the Status of bug 646631 from ON_DEV to ON_QA

          Show
          RH Bugzilla Integration
          added a comment - John Mazzitelli <mazz@redhat.com> changed the Status of bug 646631 from ON_DEV to ON_QA
          Hide
          RH Bugzilla Integration
          added a comment -

          John Mazzitelli <mazz@redhat.com> made a comment on bug 646631

          git commit to master 951ddce

          Show
          RH Bugzilla Integration
          added a comment - John Mazzitelli <mazz@redhat.com> made a comment on bug 646631 git commit to master 951ddce
          Hide
          RH Bugzilla Integration
          added a comment -

          Mike Foley <mfoley@redhat.com> made a private comment on bug 646631

          Show
          RH Bugzilla Integration
          added a comment - Mike Foley <mfoley@redhat.com> made a private comment on bug 646631
          Hide
          Larry O'Leary
          added a comment -

          This issue was resolved in upstream EMBJOPR-366 and the fix is included in EmbJopr 1.3.4.SP6.

          Show
          Larry O'Leary
          added a comment - This issue was resolved in upstream EMBJOPR-366 and the fix is included in EmbJopr 1.3.4.SP6.
          Hide
          Jan Martiska
          added a comment -

          verified fix presence in EAP 5.2.0.ER2, it works

          Show
          Jan Martiska
          added a comment - verified fix presence in EAP 5.2.0.ER2, it works

            People

            • Assignee:
              Larry O'Leary
              Reporter:
              Biljana Kramer
              Writer:
              Russell Dickenson
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: