Petals BC SQL

Embedded WSDL is incorrect

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6.2
  • Fix Version/s: 1.6.3, 1.8.0
  • Component/s: None
  • Security Level: Public
  • Description:

    The embedded WSDL defining the service contract is wrong when defining the type 'columnType': the column value is not modeled.

  • Environment:
    -

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christophe DENEUX added a comment - Mon, 16 Oct 2017 - 14:16:55 +0200

Only attributes 'name' and 'type' are modeled

Show
Christophe DENEUX added a comment - Mon, 16 Oct 2017 - 14:16:55 +0200 Only attributes 'name' and 'type' are modeled
Hide
Permalink
Christophe DENEUX added a comment - Tue, 17 Oct 2017 - 08:41:28 +0200

Fixed in trunk

Show
Christophe DENEUX added a comment - Tue, 17 Oct 2017 - 08:41:28 +0200 Fixed in trunk
Hide
Permalink
Christophe DENEUX added a comment - Tue, 24 Oct 2017 - 17:53:01 +0200 - edited

Reopened because the replies of BC SQL are not aligned with their definitions in the WSDL.

<sql:result xmlns:sql="http://petals.ow2.org/components/sql/version-1">
   <row>
      <column>...</column>
   </row>
</sql:result>

instead of the expected one:

<result xmlns="http://petals.ow2.org/components/sql/version-1">
   <row>
      <column>...</column>
   </row>
</result>
Show
Christophe DENEUX added a comment - Tue, 24 Oct 2017 - 17:53:01 +0200 - edited Reopened because the replies of BC SQL are not aligned with their definitions in the WSDL. 
<sql:result xmlns:sql="http://petals.ow2.org/components/sql/version-1">
   <row>
      <column>...</column>
   </row>
</sql:result>
instead of the expected one: 
<result xmlns="http://petals.ow2.org/components/sql/version-1">
   <row>
      <column>...</column>
   </row>
</result>
Hide
Permalink
Christophe DENEUX added a comment - Tue, 24 Oct 2017 - 17:57:46 +0200

Fixed in trunk

Show
Christophe DENEUX added a comment - Tue, 24 Oct 2017 - 17:57:46 +0200 Fixed in trunk
Hide
Permalink
Christophe DENEUX added a comment - Wed, 6 Mar 2019 - 12:15:28 +0100 - edited

Reopened because operation names for INSERT, DELETE and UPDATE with response are incorrect, and also operation names relative to stored procedure.

Show
Christophe DENEUX added a comment - Wed, 6 Mar 2019 - 12:15:28 +0100 - edited Reopened because operation names for INSERT, DELETE and UPDATE with response are incorrect, and also operation names relative to stored procedure.
Hide
Permalink
Christophe DENEUX added a comment - Wed, 6 Mar 2019 - 17:04:25 +0100

Operation names fixed in trunk

Show
Christophe DENEUX added a comment - Wed, 6 Mar 2019 - 17:04:25 +0100 Operation names fixed in trunk

People

Dates

  • Created:
    Mon, 16 Oct 2017 - 14:16:21 +0200
    Updated:
    Wed, 6 Mar 2019 - 17:04:25 +0100
    Resolved:
    Wed, 6 Mar 2019 - 17:04:25 +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.