Petals SE Camel

Support broader naming scheme for service id to identify Camel endpoints

Details

  • Type: Improvement Request Improvement Request
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 0.5.1, 1.0.0
  • Fix Version/s: 0.5.2, 1.0.1
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    The Camel component should support a broader naming scheme to identify Camel endpoint (in Consumes serviceId and WSDL's operations)

    Let's define the following rule:

    A serviceId consists of one or more (letters | digits | _ | - | .) except for the first character that can only be a letter.

    Show
    The Camel component should support a broader naming scheme to identify Camel endpoint (in Consumes serviceId and WSDL's operations) Let's define the following rule:
    A serviceId consists of one or more (letters | digits | _ | - | .) except for the first character that can only be a letter.
  • Environment:
    -

People

Dates

  • Created:
    Wed, 3 Feb 2016 - 09:46:20 +0100
    Updated:
    Wed, 3 Feb 2016 - 10:56:55 +0100
    Resolved:
    Wed, 3 Feb 2016 - 10:56:55 +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.