Petals Studio

Extend the SU wizard from the preferences

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Blocker Blocker
  • Resolution: Won't Fix
  • Affects Version/s: 1.2.0
  • Fix Version/s: 1.3.3
  • Component/s: Petals Tools
  • Security Level: Public
  • Description:
    Hide

    Some components are not supported in the studio. That's a fact.
    Sometimes, you also develop your own component.

    It would be great to be able to register a new kind of Petals component through preferences. The preferences should help to define:

    • A new version of a known component.
      • Information required: is-provides, is-consumes, the directory of the XSD files for the wizard (optional).
    • A new component.
      • Information required: the component name, the component kind (BC, SE), one or several use case categories and one or several versions (at least one is required).

    Updating these preferences should make these components visible in the SU wizard. With this solution, there is no possible customisation of the wizard. For more options, you need to create a plug-in. If there is no XSD file, then the wizard will have to create a default jbi.xml with incomplete mark-ups.

    Show
    Some components are not supported in the studio. That's a fact. Sometimes, you also develop your own component. It would be great to be able to register a new kind of Petals component through preferences. The preferences should help to define:
    • A new version of a known component.
      • Information required: is-provides, is-consumes, the directory of the XSD files for the wizard (optional).
    • A new component.
      • Information required: the component name, the component kind (BC, SE), one or several use case categories and one or several versions (at least one is required).
    Updating these preferences should make these components visible in the SU wizard. With this solution, there is no possible customisation of the wizard. For more options, you need to create a plug-in. If there is no XSD file, then the wizard will have to create a default jbi.xml with incomplete mark-ups.
  • Environment:
    All.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Zurczak added a comment - Fri, 5 Oct 2012 - 17:06:59 +0200

The entire wizard system and ALL the Petals configurations (including the jbi.xml files) should change.
Then, this feature would not be required, a natural extensibility would be provided without using Eclipse preferences.

Show
Vincent Zurczak added a comment - Fri, 5 Oct 2012 - 17:06:59 +0200 The entire wizard system and ALL the Petals configurations (including the jbi.xml files) should change. Then, this feature would not be required, a natural extensibility would be provided without using Eclipse preferences.

People

Dates

  • Created:
    Wed, 20 Jul 2011 - 12:40:16 +0200
    Updated:
    Fri, 5 Oct 2012 - 17:07:03 +0200
    Resolved:
    Fri, 5 Oct 2012 - 17:06:59 +0200
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.