Petals Studio

Component type != Component ID

Details

  • Type: Improvement Request Improvement Request
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.2.0
  • Fix Version/s: 1.2.0
  • Component/s: Petals Tools
  • Security Level: Public
  • Description:
    Hide

    JBI components have a name, which identify them in the container.
    As an example, if you want to install 2 instances of the SOAP BC on a same container, you have to change the name of one of the instances. And you must make all the SA that target this second instance reference the right name.

    And if you change the target component in the studio for the SU / SA projects, then validation will be incomplete or fail.
    In fact, the studio should distinguish two properties which make one for the moment:

    • The component type (the original name of the component, e.g. petals-bc-soap).
    • The component ID (the name of the component to deploy, e.g. petals-bd-soap-2.4).


    If the component ID is not specified, the default component name will be taken.
    Otherwise, the component ID will be taken for the packaging.

    And we will have to see how the Maven plug-in is impacted when the component ID changes.

    Show
    JBI components have a name, which identify them in the container. As an example, if you want to install 2 instances of the SOAP BC on a same container, you have to change the name of one of the instances. And you must make all the SA that target this second instance reference the right name. And if you change the target component in the studio for the SU / SA projects, then validation will be incomplete or fail. In fact, the studio should distinguish two properties which make one for the moment:
    • The component type (the original name of the component, e.g. petals-bc-soap).
    • The component ID (the name of the component to deploy, e.g. petals-bd-soap-2.4).

    If the component ID is not specified, the default component name will be taken. Otherwise, the component ID will be taken for the packaging. And we will have to see how the Maven plug-in is impacted when the component ID changes.
  • Environment:
    All

Activity

Vincent Zurczak made changes - Fri, 8 Jul 2011 - 15:17:13 +0200
Field Original Value New Value
Status New [ 10000 ] Open [ 10002 ]
Priority Minor [ 4 ]
Vincent Zurczak made changes - Fri, 8 Jul 2011 - 15:17:15 +0200
Status Open [ 10002 ] In Progress [ 10003 ]
Vincent Zurczak made changes - Fri, 8 Jul 2011 - 15:48:55 +0200
Status In Progress [ 10003 ] Resolved [ 10004 ]
Fix Version/s 1.2.0 [ 10079 ]
Resolution Fixed [ 1 ]
Vincent Zurczak made changes - Fri, 8 Jul 2011 - 15:49:00 +0200
Status Resolved [ 10004 ] Closed [ 10005 ]
Vincent Zurczak made changes - Fri, 19 Aug 2011 - 10:11:03 +0200
Affects Version/s 1.2.0 [ 10079 ]
Affects Version/s 1.2.0-RC1 [ 10250 ]

People

Dates

  • Created:
    Mon, 4 Jul 2011 - 12:12:49 +0200
    Updated:
    Fri, 19 Aug 2011 - 10:11:03 +0200
    Resolved:
    Fri, 8 Jul 2011 - 15:48:55 +0200