Hide Forgot
Description of problem: quickstart test output fomr mvn exec:java does not comply to what is stated as expected output in Readme.md Version-Release number of selected component (if applicable): FSW 6.0.0 ER3 How reproducible: 100% Steps to Reproduce: 1. follow Readme file Actual results: SOAP Reply: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"><SOAP-ENV:Header><ns:conversationId xmlns:ns="http://www.jboss.org/cid">12345</ns:conversationId><ns:exampleHeader xmlns:ns="http://www.jboss.org/header">Outbound</ns:exampleHeader></SOAP-ENV:Header><SOAP-ENV:Body><requestResponse xmlns="http://example.com/loan-approval/loanService/"> <tns:accept xmlns:tns="http://example.com/loan-approval/loanService/">yes</tns:accept> </requestResponse></SOAP-ENV:Body></SOAP-ENV:Envelope> Expected results: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> <SOAP-ENV:Header/> <SOAP-ENV:Body> <requestResponse xmlns="http://example.com/loan-approval/loanService/"> <tns:accept xmlns:tns="http://example.com/loan-approval/loanService/">yes</tns:accept> </requestResponse> </SOAP-ENV:Body> </SOAP-ENV:Envelope>
Gary - note the addition of conversationId in the reply. Running this by you to make sure it's cool before we update the README.
Hi Keith, yes the two header values (conversationId and exampleHeader) are now valid in the response.
verified in ER6