Petals Studio

CDK elements are not always sorted correctly in the JBI editor

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Fixed
  • Affects Version/s: 1.3.0
  • Fix Version/s: 1.3.1
  • Component/s: Petals Tools
  • Security Level: Public
  • Description:
    Hide

    When modifying a generated jbi.xml file with the JBI editor, the CDK elements are not always written in the right order.

    • SOAP Providers see the timeout element being inserted in the last position instead of the first one.
    • SOAP Consumers are handled correctly.

    This need to be fixed, and the CDK element ordering must be guaranteed.
    Otherwise, deployments in Petals will fail due to invalid jbi.xml files.

    Show
    When modifying a generated jbi.xml file with the JBI editor, the CDK elements are not always written in the right order.
    • SOAP Providers see the timeout element being inserted in the last position instead of the first one.
    • SOAP Consumers are handled correctly.
    This need to be fixed, and the CDK element ordering must be guaranteed. Otherwise, deployments in Petals will fail due to invalid jbi.xml files.
  • Environment:
    -

Activity

Descending order - Click to sort in ascending order
Hide
Permalink
Vincent Zurczak added a comment - Mon, 27 Feb 2012 - 11:01:10 +0100

Fixed.
Hack : EMF to DOM. Then DOM sorting. Then DOM to file.

Show
Vincent Zurczak added a comment - Mon, 27 Feb 2012 - 11:01:10 +0100 Fixed. Hack : EMF to DOM. Then DOM sorting. Then DOM to file.
Hide
Permalink
Vincent Zurczak added a comment - Fri, 24 Feb 2012 - 10:04:32 +0100

This can be fixed by preventing a feature name from being inserted twice.
However, if we do the following test, the JBI editor fails completely.

  • Open the jbi.xml file in the source editor. Remove a CDK element (e.g. forward-message-properties).
  • Open the jbi.xml file in the form editor. Set a value for the removed element.
  • Look at the sources now.

The new CDK element has been inserted at the end of the jbi.xml, after the component specific elements.
This issue requires a quick fix and requires a new version of the studio to be released as soon as possible.

Show
Vincent Zurczak added a comment - Fri, 24 Feb 2012 - 10:04:32 +0100 This can be fixed by preventing a feature name from being inserted twice. However, if we do the following test, the JBI editor fails completely.
  • Open the jbi.xml file in the source editor. Remove a CDK element (e.g. forward-message-properties).
  • Open the jbi.xml file in the form editor. Set a value for the removed element.
  • Look at the sources now.
The new CDK element has been inserted at the end of the jbi.xml, after the component specific elements. This issue requires a quick fix and requires a new version of the studio to be released as soon as possible.

People

Dates

  • Created:
    Fri, 24 Feb 2012 - 09:41:35 +0100
    Updated:
    Mon, 27 Feb 2012 - 11:01:15 +0100
    Resolved:
    Mon, 27 Feb 2012 - 11:01:10 +0100
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.