Petals Sample Client

Endpoint selection does not work

Details

  • Type: Bug Bug
  • Status: Resolved Resolved
  • Priority: Critical Critical
  • Resolution: Fixed
  • Affects Version/s: 1.9.1
  • Fix Version/s: 1.9.2
  • Component/s: None
  • Security Level: Public
  • Description:

    When selecting an endpoint in the list of tab Query, the fields of tab Send are not correctly filled with the expected values.

  • Environment:
    Petals 5.0.0-RC-1

Activity

Hide
Christophe DENEUX added a comment - Thu, 26 May 2016 - 12:13:31 +0200

Fixed in trunk. Now Petals Sample Client used its own string representation of a service endpoint

Show
Christophe DENEUX added a comment - Thu, 26 May 2016 - 12:13:31 +0200 Fixed in trunk. Now Petals Sample Client used its own string representation of a service endpoint
Hide
Christophe DENEUX added a comment - Thu, 26 May 2016 - 12:06:44 +0200 - edited

The Petals Sample Client use the method ServiceEndpoint.toString() to fill the endpoint list. Next, it use the selected string to fill fields of tab Send.

As output of ServiceEndpoint.toString() has changed with svn#38990, the parsing does not work anymore.

The Petals Sample Client should use its own service endpoint string representation and parse it, to prevent from changes as service endpoint level.

Show
Christophe DENEUX added a comment - Thu, 26 May 2016 - 12:06:44 +0200 - edited The Petals Sample Client use the method ServiceEndpoint.toString() to fill the endpoint list. Next, it use the selected string to fill fields of tab Send. As output of ServiceEndpoint.toString() has changed with svn#38990, the parsing does not work anymore. The Petals Sample Client should use its own service endpoint string representation and parse it, to prevent from changes as service endpoint level.

People

Dates

  • Created:
    Thu, 26 May 2016 - 11:58:09 +0200
    Updated:
    Thu, 26 May 2016 - 12:13:31 +0200
    Resolved:
    Thu, 26 May 2016 - 12:13:31 +0200