JiBX

After specific error condition, server returns response with missing SOAP namespace

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: JiBX/WS 0.9
  • Fix Version/s: None
  • Component/s: JiBX/WS
  • Labels:
    None
  • Number of attachments :
    0

Description

The scenario is triggered by sending a SOAP payload to the server where the server has a valid JiBX binding for the payload, but does not have a web service configured for the payload.

Subsequent requests to the server generate response messages with no SOAP namespace defined, ie. the root element is <SOAP:Envelope>.

Activity

Ascending order - Click to sort in descending order
Nigel Charman made changes -
Field Original Value New Value
Fix Version/s JiBX/WS 0.9.1 [ 15889 ]
Original Estimate 0 minutes [ 0 ]
Remaining Estimate 0 minutes [ 0 ]
Nigel Charman made changes -
Status Open [ 1 ] Closed [ 6 ]
Resolution Fixed [ 1 ]
Hide
Permalink
Nigel Charman added a comment -

Fixed the immediate issue in JiBX/WS server. However the underlying cause of namespace state not being reset can be reproduced on the JiBX/WS client. Have raised separate issue JIBX-344 for the underlying cause.

Show
Nigel Charman added a comment - Fixed the immediate issue in JiBX/WS server. However the underlying cause of namespace state not being reset can be reproduced on the JiBX/WS client. Have raised separate issue JIBX-344 for the underlying cause.

People

  • Assignee:
    Nigel Charman
    Reporter:
    Nigel Charman
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: