Petals Studio

Improve XSLT and Validation WSDL

Details

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

    XSLT and Validation suffer from the same problem.
    The default WSDL is too restrictive.
    It is possible to remove these constraints by setting the type of the message parts, instead of an element name.

    It drastically simplify the usage of WSDL of XSLT and XSD, although I'm not sure it will be really usable with BPEL.
    Anyway, it would also simplify the documentation of the tooling for these components.

    Show
    XSLT and Validation suffer from the same problem. The default WSDL is too restrictive. It is possible to remove these constraints by setting the type of the message parts, instead of an element name. It drastically simplify the usage of WSDL of XSLT and XSD, although I'm not sure it will be really usable with BPEL. Anyway, it would also simplify the documentation of the tooling for these components.
  • Environment:
    All.

Activity

Hide
Vincent Zurczak added a comment - Fri, 12 Nov 2010 - 16:02:14 +0100

Commit # 1899
The WSDL have two warnings, but valid Java clients can be created from them (with CXF).
WSDL do not need to be always modified now. They can remain as it, or be customized if required.

Show
Vincent Zurczak added a comment - Fri, 12 Nov 2010 - 16:02:14 +0100 Commit # 1899 The WSDL have two warnings, but valid Java clients can be created from them (with CXF). WSDL do not need to be always modified now. They can remain as it, or be customized if required.

People

Dates

  • Created:
    Tue, 9 Nov 2010 - 13:56:22 +0100
    Updated:
    Fri, 12 Nov 2010 - 16:02:19 +0100
    Resolved:
    Fri, 12 Nov 2010 - 16:02:14 +0100