Petals Studio

Possible conflicts in croquis export (EIP)

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.2.0
  • Fix Version/s: 1.3.0
  • Component/s: Petals Tools
  • Security Level: Public
  • Description:
    Hide
    • Create an EIP croquis.
    • Make sure all the EIP nodes have the same service name.
    • Export it.


    The same project is proposed for every EIP node.
    It means only one SU project will be created, instead of one per EIP node.

    The export wizard should check that every project has a different name.

    Show
    • Create an EIP croquis.
    • Make sure all the EIP nodes have the same service name.
    • Export it.

    The same project is proposed for every EIP node. It means only one SU project will be created, instead of one per EIP node. The export wizard should check that every project has a different name.
  • Environment:
    Windows 7

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Zurczak added a comment - Thu, 19 Jan 2012 - 19:47:07 +0100

Fix the validation for EIP chains.
Force the EIP nodes of a same chain to have a different service name (local part) - export constraint.
Add a validation rule in the export wizard too to not create projects with the same name.

Show
Vincent Zurczak added a comment - Thu, 19 Jan 2012 - 19:47:07 +0100 Fix the validation for EIP chains. Force the EIP nodes of a same chain to have a different service name (local part) - export constraint. Add a validation rule in the export wizard too to not create projects with the same name.

People

Dates

  • Created:
    Fri, 7 Oct 2011 - 17:04:47 +0200
    Updated:
    Thu, 19 Jan 2012 - 19:47:14 +0100
    Resolved:
    Thu, 19 Jan 2012 - 19:47:07 +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.