Chris Laprun <chris.laprun> made a comment on jira GTNWSRP-295

Martin Weiler <mweiler> made a comment on [bug 835369|https://bugzilla.redhat.com/show_bug.cgi?id=835369]

Description of problem:
Using EPP as producer, the getServiceDescription request is not returning the supportedOptions element in the response.

Version-Release number of selected component (if applicable):
WSRP 2.1.0.GA

How reproducible:
Always

Steps to Reproduce:
1. Using SoapUI, send a getServiceDescription request to EPP.
  
Actual results:
Response missing the supportedOptions element:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <env:Header/>
   <env:Body>
      <getServiceDescriptionResponse xmlns="urn:oasis:names:tc:wsrp:v2:types">
         <requiresRegistration>false</requiresRegistration>
         <offeredPortlets>
            <!-- SNIP -->
         </offeredPortlets>
         <requiresInitCookie>perUser</requiresInitCookie>
         <locales>en-US</locales>
         <locales>en</locales>
      </getServiceDescriptionResponse>
   </env:Body>
</env:Envelope>

Expected results:
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/">
   <env:Header/>
   <env:Body>
      <getServiceDescriptionResponse xmlns="urn:oasis:names:tc:wsrp:v2:types">
         <requiresRegistration>false</requiresRegistration>
         <offeredPortlets>
            <!-- SNIP -->
         </offeredPortlets>
         <requiresInitCookie>perUser</requiresInitCookie>
         <locales>en-US</locales>
         <locales>en</locales>
         <supportedOptions>wsrp:import</supportedOptions>
         <supportedOptions>wsrp:export</supportedOptions>         
      </getServiceDescriptionResponse>
   </env:Body>
</env:Envelope>

Additional info:
This is already fixed in WSRP 2.2.0: 
https://issues.jboss.org/browse/GTNWSRP-262

Chris Laprun <chris.laprun> made a comment on jira GTNWSRP-295

This was fixed by commit https://source.jboss.org/changelog/GateInWsrp?cs=85ecf852dc9072b600360f5bf17b45af1d3175dc

Chris Laprun <chris.laprun> updated the status of jira GTNWSRP-295 to Closed

Chris Laprun <chris.laprun> updated the status of jira GTNWSRP-295 to Reopened

This is a customer orginated ticket. It needs CCFR written for inclusion in the Release Notes for 5.2.2. Added placeholder text to fill in.

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
CAUSE:

CONSEQUENCE:

FIX:

RESULT:

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,7 +1,7 @@
-CAUSE:
+CAUSE: The WSRP Producer was ignoring several optional elements when returning a service description response to the consumer, including the supportedOptions element. 
 
-CONSEQUENCE:
+CONSEQUENCE: WSRP Consumers that were relying on this optional elements to tailor their communication with the producer could behave improperly based on wrong assumptions due to missing (though optional) information.
 
-FIX:
+FIX: The WSRP Producer now properly emit the supportedOptions element in its service description response, thus affording Consumers to properly tailor their behavior.
 
-RESULT:+RESULT: Improved interoperability with third-party consumers.

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,7 +1 @@
-CAUSE: The WSRP Producer was ignoring several optional elements when returning a service description response to the consumer, including the supportedOptions element. 
+The WSRP Producer was ignoring several optional elements when returning a service description response to the consumer, including the supportedOptions element. WSRP Consumers that were relying on these optional elements to tailor their communication with the producer could behave improperly based on wrong assumptions due to missing (though optional) information.  The WSRP Producer now properly emits the supportedOptions element in its service description response, which allows Consumers to properly tailor their behavior, and results in improved interoperability with third-party consumers.-
-CONSEQUENCE: WSRP Consumers that were relying on this optional elements to tailor their communication with the producer could behave improperly based on wrong assumptions due to missing (though optional) information.
-
-FIX: The WSRP Producer now properly emit the supportedOptions element in its service description response, thus affording Consumers to properly tailor their behavior.
-
-RESULT: Improved interoperability with third-party consumers.

Verified again at 5.2.2 CR01