Petals Studio

Be able to change the service name in provider SU

Details

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

    When you import several web services in Petals, you sometimes need to override the default service name (e.g. to make a difference between instances of the same WS that would be deployed on a different application server).

    The studio should allow two things:

    • In the SU wizard, be able to change the local part of the service name and update the WSDL accordingly at the end of the wizard.
    • In the JBI editor, add a helper or update an existing one for the same use case.
    Show
    When you import several web services in Petals, you sometimes need to override the default service name (e.g. to make a difference between instances of the same WS that would be deployed on a different application server). The studio should allow two things:
    • In the SU wizard, be able to change the local part of the service name and update the WSDL accordingly at the end of the wizard.
    • In the JBI editor, add a helper or update an existing one for the same use case.
  • Environment:
    All

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Zurczak added a comment - Thu, 21 Jul 2011 - 13:33:40 +0200

Already asked by the past.
And after thinking about it:

  • Exposing several instances of a same web service in Petals should be achieved with the end-point auto-generation.
  • If web services are deployed on different kinds of servers, this is not a matter for Petals. From an architecture point of view, a load-balancer would be better here and Petals would only reference the load-balancer.
  • This feature already exists as a refactoring mechanism on SU projects.
Show
Vincent Zurczak added a comment - Thu, 21 Jul 2011 - 13:33:40 +0200 Already asked by the past. And after thinking about it:
  • Exposing several instances of a same web service in Petals should be achieved with the end-point auto-generation.
  • If web services are deployed on different kinds of servers, this is not a matter for Petals. From an architecture point of view, a load-balancer would be better here and Petals would only reference the load-balancer.
  • This feature already exists as a refactoring mechanism on SU projects.
Vincent Zurczak made changes - Thu, 21 Jul 2011 - 13:33:40 +0200
Field Original Value New Value
Resolution Won't Fix [ 2 ]
Status New [ 10000 ] Resolved [ 10004 ]
Vincent Zurczak made changes - Thu, 21 Jul 2011 - 13:34:04 +0200
Priority Minor [ 4 ]
Vincent Zurczak made changes - Thu, 21 Jul 2011 - 13:34:09 +0200
Status Resolved [ 10004 ] Closed [ 10005 ]
Fix Version/s 1.2.0 [ 10079 ]
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 ]
Transition Status Change Time Execution Times Last Executer Last Execution Date
New New Resolved Resolved
17d 1h 12m
1
Vincent Zurczak
Thu, 21 Jul 2011 - 13:33:40 +0200
Resolved Resolved Closed Closed
29s
1
Vincent Zurczak
Thu, 21 Jul 2011 - 13:34:09 +0200

People

Dates

  • Created:
    Mon, 4 Jul 2011 - 12:21:02 +0200
    Updated:
    Fri, 19 Aug 2011 - 10:11:03 +0200
    Resolved:
    Thu, 21 Jul 2011 - 13:33:40 +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.