Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOAP 1.1 Web service request to SOAP 1. Provider acting as gateway fails when wsAtomicTransaction feature is enabled #24938

Closed
djmatthews opened this issue Apr 5, 2023 · 0 comments · Fixed by #24946
Labels
release bug This bug is present in a released version of Open Liberty release:23004

Comments

@djmatthews
Copy link

Describe the bug
A SOAP 1.1 JAX-WS Web service request to SOAP1.2 Provider - ie implements Provider and has @BindingType(SOAPBinding.SOAP12HTTP_BINDING) - acting as gateway fails when wsAtomicTransaction feature is enabled. It does not fail for SOAP 1.2 requests and does not fail for either SOAP 1.1 or SOAP1.2 requests when the wsAtomicTransaction feature is not present.

If there is a stack trace, please include the FULL stack trace (without any [internal classes] lines in it). To find the full stack trace, you may need to check in $WLP_OUTPUT_DIR/messages.log

No stack - causal failure is silent.

Steps to Reproduce
Set up a SOAP 1.2 Provider web service eg

@ServiceMode(value = Service.Mode.MESSAGE)
@WebServiceProvider() //(wsdlLocation="WEB-INF/wsdl/Something.wsdl")
@BindingType(SOAPBinding.SOAP12HTTP_BINDING)

public class Something implements javax.xml.ws.Provider {

@Override
public SOAPMessage invoke(SOAPMessage request) {
    ...
   }

}

Send in a SOAP 1.1 Message eg

<soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope" xmlns:dan="http://wssec.basic.cxf.fats/types">
soapenv:Header/
soapenv:Body
dan:getVer

WIBBLE

</dan:getVer>
</soapenv:Body>
</soapenv:Envelope>

NOTE the SOAP Message does NOT contain top-level element in the SOAP Body of invoke.

Expected behavior
The SOAP 1.1 Message should be delivered to the Web Service just as it is when the wsAtomicTransaction featuire is not present.

Diagnostic information:

  • OpenLiberty Version: [Any eg 22.0.0.9]
  • Affected feature(s) [e.g. wsAtomicTransaction-1.2]
  • Java Version: [not specific]
  • server.xml configuration (just need javaee-8.0 and wsAtomicTransaction-1.2 features)
  • If it would be useful, upload the messages.log file found in $WLP_OUTPUT_DIR/messages.log

Additional context
Investigation shows NPE occurs because BindingOperationInfo passed by WSCoorUtil to PolicyEngine.getEffectiveServerRequestPolicy is null

@djmatthews djmatthews added the release bug This bug is present in a released version of Open Liberty label Apr 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release bug This bug is present in a released version of Open Liberty release:23004
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants