Petals Distribution

Introduce a WSDL Binding for Petals

Details

  • Type: Improvement Request Improvement Request
  • Status: Open Open
  • Priority: Major Major
  • Resolution: Unresolved
  • Affects Version/s: 4.2.4
  • Fix Version/s: None
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    Currently, we use WSDLs to describe the Petals services, but our WSDLs are actually not conforming to the WSDL standard: there is no bindings that actually specify that Petals is used for transport and data.

    It would make sense to introduce a binding (as with SOAP and HTTP,etc transports) for Petals.

    This binding should be extensible so that a SE like BPMN or Camel could have its specific settings (note: is that actually the right place to specify implementation specific things such as the bpmn process or the camel route to use???).

    It would be useful from a governance point of view, and we then could also introduce tools to ease the manipulation of WSDL.
    This would go hand in hand with the effort to make Petals full-SOA.

    Show
    Currently, we use WSDLs to describe the Petals services, but our WSDLs are actually not conforming to the WSDL standard: there is no bindings that actually specify that Petals is used for transport and data. It would make sense to introduce a binding (as with SOAP and HTTP,etc transports) for Petals. This binding should be extensible so that a SE like BPMN or Camel could have its specific settings (note: is that actually the right place to specify implementation specific things such as the bpmn process or the camel route to use???). It would be useful from a governance point of view, and we then could also introduce tools to ease the manipulation of WSDL. This would go hand in hand with the effort to make Petals full-SOA.
  • Environment:
    -

People

Dates

  • Created:
    Fri, 27 Mar 2015 - 12:07:46 +0100
    Updated:
    Fri, 27 Mar 2015 - 12:08:06 +0100