[jira] [Commented] (CXF-4583) When the logical handler return false processing the outbound message, the SoapMessage's body is always empty.
[ https://issues.apache.org/jira/browse/CXF-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481450#comment-13481450 ] Yi Xiao commented on CXF-4583: -- Hi Willem, I verify the path, it works fine. Thanks very much. > When the logical handler return false processing the outbound message, the > SoapMessage's body is always empty. > -- > > Key: CXF-4583 > URL: https://issues.apache.org/jira/browse/CXF-4583 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao >Assignee: Willem Jiang > Labels: handler > Attachments: CXF-4853.patch > > > According to the spec, when return false: > Normal message processing stops, close is called on each previously invoked > handler in the chain, the message is dispatched. > So the message returned by endpoint should be dispatched to client, not > always the empty body element. > In my case, the endpoint has built the soapMessage: > http://schemas.xmlsoap.org/soap/envelope/";> > > > xmlns:ns2="http://jaxws.samples.ibm.com/";> > 116 > > > > but the client receives： > http://schemas.xmlsoap.org/soap/envelope/";> > > > > I find the LogicalHandlerOutInterceptor does not set the SoapMessage correct > when the logicalHandler return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4583) When the logical handler return false processing the outbound message, the SoapMessage's body is always empty.
[ https://issues.apache.org/jira/browse/CXF-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13481132#comment-13481132 ] Yi Xiao commented on CXF-4583: -- Could someone take a look at the issue and review the patch? Thank you very much. > When the logical handler return false processing the outbound message, the > SoapMessage's body is always empty. > -- > > Key: CXF-4583 > URL: https://issues.apache.org/jira/browse/CXF-4583 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: handler > Attachments: CXF-4853.patch > > > According to the spec, when return false: > Normal message processing stops, close is called on each previously invoked > handler in the chain, the message is dispatched. > So the message returned by endpoint should be dispatched to client, not > always the empty body element. > In my case, the endpoint has built the soapMessage: > http://schemas.xmlsoap.org/soap/envelope/";> > > > xmlns:ns2="http://jaxws.samples.ibm.com/";> > 116 > > > > but the client receives： > http://schemas.xmlsoap.org/soap/envelope/";> > > > > I find the LogicalHandlerOutInterceptor does not set the SoapMessage correct > when the logicalHandler return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4583) When the logical handler return false processing the outbound message, the SoapMessage's body is always empty.
[ https://issues.apache.org/jira/browse/CXF-4583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated CXF-4583: - Attachment: CXF-4853.patch I also provide the patch for the issue, Could you please review the patch? Thanks a lot :) > When the logical handler return false processing the outbound message, the > SoapMessage's body is always empty. > -- > > Key: CXF-4583 > URL: https://issues.apache.org/jira/browse/CXF-4583 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: handler > Attachments: CXF-4853.patch > > > According to the spec, when return false: > Normal message processing stops, close is called on each previously invoked > handler in the chain, the message is dispatched. > So the message returned by endpoint should be dispatched to client, not > always the empty body element. > In my case, the endpoint has built the soapMessage: > http://schemas.xmlsoap.org/soap/envelope/";> > > > xmlns:ns2="http://jaxws.samples.ibm.com/";> > 116 > > > > but the client receives： > http://schemas.xmlsoap.org/soap/envelope/";> > > > > I find the LogicalHandlerOutInterceptor does not set the SoapMessage correct > when the logicalHandler return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4583) When the logical handler return false processing the outbound message, the SoapMessage's body is always empty.
Yi Xiao created CXF-4583: Summary: When the logical handler return false processing the outbound message, the SoapMessage's body is always empty. Key: CXF-4583 URL: https://issues.apache.org/jira/browse/CXF-4583 Project: CXF Issue Type: Bug Components: JAX-WS Runtime Affects Versions: 2.6.2 Reporter: Yi Xiao According to the spec, when return false: Normal message processing stops, close is called on each previously invoked handler in the chain, the message is dispatched. So the message returned by endpoint should be dispatched to client, not always the empty body element. In my case, the endpoint has built the soapMessage: http://schemas.xmlsoap.org/soap/envelope/";> http://jaxws.samples.ibm.com/";> 116 but the client receives： http://schemas.xmlsoap.org/soap/envelope/";> I find the LogicalHandlerOutInterceptor does not set the SoapMessage correct when the logicalHandler return false. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4565) The message flow is not correct when handler throw ProtocolException outbound
[ https://issues.apache.org/jira/browse/CXF-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476719#comment-13476719 ] Yi Xiao commented on CXF-4565: -- You are welcome. > The message flow is not correct when handler throw ProtocolException outbound > - > > Key: CXF-4565 > URL: https://issues.apache.org/jira/browse/CXF-4565 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Reporter: Yi Xiao >Assignee: Freeman Fang > Labels: handler > Fix For: 2.4.11, 2.5.7, 2.6.4, 2.7.1 > > Attachments: cxf-4565.patch > > > The scenario is using two SoapHandler and one LogicalHandler to intercept the > message from client, and when LogicalHandler at server side handle the > outbound message, it throws a ProtocolException. > Now, the message flow at server side in CXF is: > Server_SOAPHandler1_handleMessage_Inbound: > Server_SOAPHandler2_handleMessage_Inbound: > Server_LogicalHandler_handleMessage_Inbound: > Server_countString: > Server_LogicalHandler_handleMessage_Outbound: > Server_LogicalHandler_handleFault_Outbound: // All of the three > Server_SOAPHandler2_handleFault_Outbound: // handlerFault methods > Server_SOAPHandler1_handleFault_Outbound: // are invoked > Server_LogicalHandler_close: > Server_SOAPHandler2_close: > Server_SOAPHandler1_close: > But according to jsr224 9.3.2.1 > Throw ProtocolException or a subclass This indicates that normal message > processing should cease. > Subsequent actions depend on whether the MEP in use requires a response to > the message currently being processed or not: > No response Normal message processing stops, close is called on each > previously invoked handler in the chain, the exception is dispatched (see > section 9.1.2.3). > I also test the same case in WebSphere8.5 and Glassfish3.1.2.2, the message > flow is: > Server_SOAPHandler1_handleMessage_Inbound: > Server_SOAPHandler2_handleMessage_Inbound: > Server_LogicalHandler_handleMessage_Inbound: > Server_countString: > Server_LogicalHandler_handleMessage_Outbound: > Server_LogicalHandler_close: > Server_SOAPHandler2_close: > Server_SOAPHandler1_close: > The handleFault methods are not called, and the close methods are called > directly, I think it matches the spec better. > I also provide a patch for the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4565) The message flow is not correct when handler throw ProtocolException outbound
[ https://issues.apache.org/jira/browse/CXF-4565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated CXF-4565: - Attachment: cxf-4565.patch Could some one review the patch? thank you very much :) > The message flow is not correct when handler throw ProtocolException outbound > - > > Key: CXF-4565 > URL: https://issues.apache.org/jira/browse/CXF-4565 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Reporter: Yi Xiao > Labels: handler > Attachments: cxf-4565.patch > > > The scenario is using two SoapHandler and one LogicalHandler to intercept the > message from client, and when LogicalHandler at server side handle the > outbound message, it throws a ProtocolException. > Now, the message flow at server side in CXF is: > Server_SOAPHandler1_handleMessage_Inbound: > Server_SOAPHandler2_handleMessage_Inbound: > Server_LogicalHandler_handleMessage_Inbound: > Server_countString: > Server_LogicalHandler_handleMessage_Outbound: > Server_LogicalHandler_handleFault_Outbound: // All of the three > Server_SOAPHandler2_handleFault_Outbound: // handlerFault methods > Server_SOAPHandler1_handleFault_Outbound: // are invoked > Server_LogicalHandler_close: > Server_SOAPHandler2_close: > Server_SOAPHandler1_close: > But according to jsr224 9.3.2.1 > Throw ProtocolException or a subclass This indicates that normal message > processing should cease. > Subsequent actions depend on whether the MEP in use requires a response to > the message currently being processed or not: > No response Normal message processing stops, close is called on each > previously invoked handler in the chain, the exception is dispatched (see > section 9.1.2.3). > I also test the same case in WebSphere8.5 and Glassfish3.1.2.2, the message > flow is: > Server_SOAPHandler1_handleMessage_Inbound: > Server_SOAPHandler2_handleMessage_Inbound: > Server_LogicalHandler_handleMessage_Inbound: > Server_countString: > Server_LogicalHandler_handleMessage_Outbound: > Server_LogicalHandler_close: > Server_SOAPHandler2_close: > Server_SOAPHandler1_close: > The handleFault methods are not called, and the close methods are called > directly, I think it matches the spec better. > I also provide a patch for the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4565) The message flow is not correct when handler throw ProtocolException outbound
Yi Xiao created CXF-4565: Summary: The message flow is not correct when handler throw ProtocolException outbound Key: CXF-4565 URL: https://issues.apache.org/jira/browse/CXF-4565 Project: CXF Issue Type: Bug Components: JAX-WS Runtime Reporter: Yi Xiao The scenario is using two SoapHandler and one LogicalHandler to intercept the message from client, and when LogicalHandler at server side handle the outbound message, it throws a ProtocolException. Now, the message flow at server side in CXF is: Server_SOAPHandler1_handleMessage_Inbound: Server_SOAPHandler2_handleMessage_Inbound: Server_LogicalHandler_handleMessage_Inbound: Server_countString: Server_LogicalHandler_handleMessage_Outbound: Server_LogicalHandler_handleFault_Outbound: // All of the three Server_SOAPHandler2_handleFault_Outbound: // handlerFault methods Server_SOAPHandler1_handleFault_Outbound: // are invoked Server_LogicalHandler_close: Server_SOAPHandler2_close: Server_SOAPHandler1_close: But according to jsr224 9.3.2.1 Throw ProtocolException or a subclass This indicates that normal message processing should cease. Subsequent actions depend on whether the MEP in use requires a response to the message currently being processed or not: No response Normal message processing stops, close is called on each previously invoked handler in the chain, the exception is dispatched (see section 9.1.2.3). I also test the same case in WebSphere8.5 and Glassfish3.1.2.2, the message flow is: Server_SOAPHandler1_handleMessage_Inbound: Server_SOAPHandler2_handleMessage_Inbound: Server_LogicalHandler_handleMessage_Inbound: Server_countString: Server_LogicalHandler_handleMessage_Outbound: Server_LogicalHandler_close: Server_SOAPHandler2_close: Server_SOAPHandler1_close: The handleFault methods are not called, and the close methods are called directly, I think it matches the spec better. I also provide a patch for the issue. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (CXF-4522) The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage
[ https://issues.apache.org/jira/browse/CXF-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao resolved CXF-4522. -- Resolution: Fixed > The logicalHandler could not modify the soap:body content if provider uses > the SOAPMessage > -- > > Key: CXF-4522 > URL: https://issues.apache.org/jira/browse/CXF-4522 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: logicalHandler > Attachments: jaxws-handlerdeploy.war, > logicalHandlerDoesnotWork_final.patch > > > The logical handler does not add the approperiate content in the soap11 > message's soap:body if the provider consumes the SOAPMessage. > I attache a sample to reproduce the issue, also supply a patch(include some > format :)). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4522) The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage
[ https://issues.apache.org/jira/browse/CXF-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13471236#comment-13471236 ] Yi Xiao commented on CXF-4522: -- Daniel, Thanks very much for your commitment, it works fine! > The logicalHandler could not modify the soap:body content if provider uses > the SOAPMessage > -- > > Key: CXF-4522 > URL: https://issues.apache.org/jira/browse/CXF-4522 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: logicalHandler > Attachments: jaxws-handlerdeploy.war, > logicalHandlerDoesnotWork_final.patch > > > The logical handler does not add the approperiate content in the soap11 > message's soap:body if the provider consumes the SOAPMessage. > I attache a sample to reproduce the issue, also supply a patch(include some > format :)). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4522) The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage
[ https://issues.apache.org/jira/browse/CXF-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated CXF-4522: - Attachment: logicalHandlerDoesnotWork_final.patch Hi Daniel, I've test the new patch, all the systests/jaxws tests are passed. Please review it when free. Thank you very much :) I also plan to add some tests to guarantee no regression in future. > The logicalHandler could not modify the soap:body content if provider uses > the SOAPMessage > -- > > Key: CXF-4522 > URL: https://issues.apache.org/jira/browse/CXF-4522 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: logicalHandler > Attachments: jaxws-handlerdeploy.war, > logicalHandlerDoesnotWork_final.patch > > > The logical handler does not add the approperiate content in the soap11 > message's soap:body if the provider consumes the SOAPMessage. > I attache a sample to reproduce the issue, also supply a patch(include some > format :)). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4522) The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage
[ https://issues.apache.org/jira/browse/CXF-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated CXF-4522: - Attachment: (was: logicalHandlerDoesnotWork_noFormat.patch) > The logicalHandler could not modify the soap:body content if provider uses > the SOAPMessage > -- > > Key: CXF-4522 > URL: https://issues.apache.org/jira/browse/CXF-4522 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: logicalHandler > Attachments: jaxws-handlerdeploy.war > > > The logical handler does not add the approperiate content in the soap11 > message's soap:body if the provider consumes the SOAPMessage. > I attache a sample to reproduce the issue, also supply a patch(include some > format :)). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4522) The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage
[ https://issues.apache.org/jira/browse/CXF-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated CXF-4522: - Attachment: (was: logicalHandlerDoesnotWork.patch) > The logicalHandler could not modify the soap:body content if provider uses > the SOAPMessage > -- > > Key: CXF-4522 > URL: https://issues.apache.org/jira/browse/CXF-4522 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: logicalHandler > Attachments: jaxws-handlerdeploy.war, > logicalHandlerDoesnotWork_noFormat.patch > > > The logical handler does not add the approperiate content in the soap11 > message's soap:body if the provider consumes the SOAPMessage. > I attache a sample to reproduce the issue, also supply a patch(include some > format :)). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4522) The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage
[ https://issues.apache.org/jira/browse/CXF-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated CXF-4522: - Attachment: logicalHandlerDoesnotWork_noFormat.patch Hi Daniel, I upload the patch without format. It's more clear about my intention :) Could you please take a look at it? thank you very much. I will also run the test cases to see why there are so many failures. > The logicalHandler could not modify the soap:body content if provider uses > the SOAPMessage > -- > > Key: CXF-4522 > URL: https://issues.apache.org/jira/browse/CXF-4522 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: logicalHandler > Attachments: jaxws-handlerdeploy.war, > logicalHandlerDoesnotWork_noFormat.patch, logicalHandlerDoesnotWork.patch > > > The logical handler does not add the approperiate content in the soap11 > message's soap:body if the provider consumes the SOAPMessage. > I attache a sample to reproduce the issue, also supply a patch(include some > format :)). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CXF-4522) The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage
[ https://issues.apache.org/jira/browse/CXF-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463530#comment-13463530 ] Yi Xiao commented on CXF-4522: -- Any idea about the issue? thanks very much > The logicalHandler could not modify the soap:body content if provider uses > the SOAPMessage > -- > > Key: CXF-4522 > URL: https://issues.apache.org/jira/browse/CXF-4522 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: logicalHandler > Attachments: jaxws-handlerdeploy.war, logicalHandlerDoesnotWork.patch > > > The logical handler does not add the approperiate content in the soap11 > message's soap:body if the provider consumes the SOAPMessage. > I attache a sample to reproduce the issue, also supply a patch(include some > format :)). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4522) The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage
[ https://issues.apache.org/jira/browse/CXF-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated CXF-4522: - Attachment: jaxws-handlerdeploy.war > The logicalHandler could not modify the soap:body content if provider uses > the SOAPMessage > -- > > Key: CXF-4522 > URL: https://issues.apache.org/jira/browse/CXF-4522 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: logicalHandler > Attachments: jaxws-handlerdeploy.war, logicalHandlerDoesnotWork.patch > > > The logical handler does not add the approperiate content in the soap11 > message's soap:body if the provider consumes the SOAPMessage. > I attache a sample to reproduce the issue, also supply a patch(include some > format :)). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CXF-4522) The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage
[ https://issues.apache.org/jira/browse/CXF-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yi Xiao updated CXF-4522: - Attachment: logicalHandlerDoesnotWork.patch The patch include some format. > The logicalHandler could not modify the soap:body content if provider uses > the SOAPMessage > -- > > Key: CXF-4522 > URL: https://issues.apache.org/jira/browse/CXF-4522 > Project: CXF > Issue Type: Bug > Components: JAX-WS Runtime >Affects Versions: 2.6.2 >Reporter: Yi Xiao > Labels: logicalHandler > Attachments: jaxws-handlerdeploy.war, logicalHandlerDoesnotWork.patch > > > The logical handler does not add the approperiate content in the soap11 > message's soap:body if the provider consumes the SOAPMessage. > I attache a sample to reproduce the issue, also supply a patch(include some > format :)). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CXF-4522) The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage
Yi Xiao created CXF-4522: Summary: The logicalHandler could not modify the soap:body content if provider uses the SOAPMessage Key: CXF-4522 URL: https://issues.apache.org/jira/browse/CXF-4522 Project: CXF Issue Type: Bug Components: JAX-WS Runtime Affects Versions: 2.6.2 Reporter: Yi Xiao The logical handler does not add the approperiate content in the soap11 message's soap:body if the provider consumes the SOAPMessage. I attache a sample to reproduce the issue, also supply a patch(include some format :)). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
