Skip navigation
ryan.qlc
ryan.qlc Calculating status...
Currently Being Moderated

Specifying Application version in WSDL definition

Feb 16, 2011 1:22 AM

Hi, 

 

Livecycle ES 2 SP2

WorkBench 9.5


In the WSDL definition, is it possible to refer to a service of a specific application version?


Currently we are able to specific the service's version and livecycle's version, but there is no mention of the use of application version.
 
http://<your_serverhost>:<your_port>/soap/services/<application_name>/[<folde rA>/.../<folderZ>/<service_name>?wsdl[&version=<version>][&async=true| false][&lc_version=<lc_version>]

 

Thanks

663 Views   5 Replies   Latest reply: Diego-Silva, May 25, 2011 8:32 PM
 
Replies
  • Jasmin Charbonneau
    Currently Being Moderated
    1. Jasmin Charbonneau,
    Feb 16, 2011 5:14 AM   in reply to ryan.qlc
    Report

    The [&version=] parameter refers to the version of the application.

     

    I just created a test process and looked at the wsdl, the version was 1.0.I then created a new version of the application and the version parameter was bumped to 2.0.

     

    Jasmin

     
    |
    Mark as:
  • ryan.qlc
    Currently Being Moderated
    2. ryan.qlc,
    Feb 16, 2011 11:49 PM   in reply to Jasmin Charbonneau
    Report

    Thanks for the reply.

     

    I retested the different scenarios, it seems to be working for the Application that was increased in the Major Version but not for Application that was only increased in the Minor Version. The WSDL will always belongs to the oldest version of the deployed Application of the same Major Version No.

     

    App/1.0 (Not Deploy)

    App/1.1 (Deploy)

    App/1.2 (Deploy)

    App/2.0 (Deploy)

     

    ...?wsdl&version=1.0

    WSDL belongs to App/1.1

     

    ...?wsdl&version=1.1

    WSDL belongs to App/1.1

     

    ...?wsdl&version=1.2

    WSDL belongs to App/1.1

     

    ...?wsdl&version=2.0

    WSDL belongs to App/2.0

     

    ...?wsdl

    WSDL belongs to App/2.0

     
    |
    Mark as:
  • Diego-Silva
    Currently Being Moderated
    3. Diego-Silva,
    May 23, 2011 2:49 AM   in reply to ryan.qlc
    Report

    He Ryan,

     

    I think I'm facing the same issue. So it doesn't matter how many minor versions you have, it will always call the oldest one.

     

    Anybody else can confirm this?

     

    Thanks!

     
    |
    Mark as:
  • ryan.qlc
    Currently Being Moderated
    4. ryan.qlc,
    May 25, 2011 8:27 PM   in reply to Diego-Silva
    Report

    Hi Diego,

     

    Yup, till now still encounting this issue. I believe even in LiveCycle ES (v8.2) you will also faced the same issue.

     

    If this is a big issue to you, you can try creating your new application by increasing only the major version instead of minor version. You will be able to retrieve the correct WSDL if all your application version is only different in its major version numeber.

     

    App/1.0 (Not Deploy)

    App/2.0 (Deploy)

    App/3.0 (Deploy)

    App/4.0 (Deploy)

     

    ...?wsdl&version=3.0

    WSDL belongs to App/3.0

     

    Ryan

     
    |
    Mark as:
  • Diego-Silva
    Currently Being Moderated
    5. Diego-Silva,
    May 25, 2011 8:32 PM   in reply to ryan.qlc
    Report

    Thanks Ryan!

     

    I'll try this.

     

    cheers.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points