[ https://jira.jboss.org/browse/JBWS-3084?page=com.atlassian.jira.plugin.sy... ] Sergey Beryozkin commented on JBWS-3084: ---------------------------------------- Is it possible to use Dispatch<SOAPMessage> instead of SOAPConnection ? The analysis shows that due to a number of restrictions in SAAJ API (not possible to get an access to the connection headers used by default SOAPConnection instances, even by relying on the custom SOAPConnectionFactories, explicitly added Content-Length header to SOAPMessage.getMimeHeaders() is ignored on the client side), as well as the disconnect between bare SOAPConnections and stack-specific chains, using Dispatch<SOAPMessage> and setting a property on the SOAPMessage which will be recognized by stack-specific HTTP transport modules is probably the only realistic approach. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBWS-3084?page=com.atlassian.jira.plugin.sy... ] Sergey Beryozkin commented on JBWS-3084: ---------------------------------------- OK. The only option I've found so far is to create custom SOAPConnectionFactory and SOAPConnections and directly write SOAPMessage to HttpURLConnection (or may be NettyClient in case of JBossNative) and then manually create SOAPMessage from the response InputStream. I guess this option can be explored further, we just thought directly dealing with it all was not a good idea. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBWS-3084?page=com.atlassian.jira.plugin.sy... ] Sergey Beryozkin commented on JBWS-3084: ---------------------------------------- Revision 13058 contains a disabled SOAPConnection.get test : will have to be enabled before this JIRA can be closed; it depends on the latest CXF 2.3 snapshot to make it into JBoss repos -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBWS-3084?page=com.atlassian.jira.plugin.sy... ] Sergey Beryozkin commented on JBWS-3084: ---------------------------------------- Hi Alessio - I'll enable it asap, just put that comment as I did not want to create a separate test case for get and get it disabled, I'll also retrieve the corresponding revision in CXF, I'm hoping the change is already visible - but it might take time :-) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBWS-3084?page=com.atlassian.jira.plugin.sy... ] Sergey Beryozkin commented on JBWS-3084: ---------------------------------------- Here is a CXF commit which helped with enabling SOAPConnection.get test : http://svn.apache.org/viewvc?rev=1004334&view=rev -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/JBWS-3084?page=com.atlassian.jira.plugin.sy... ] Alessio Soldano updated JBWS-3084: ---------------------------------- Fix Version/s: jbossws-native-3.4.0 jbossws-cxf-3.4.0 (was: jbossws-cxf-3.4.0.CR1) (was: jbossws-native-3.4.0.CR1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBWS-3084?page=com.atlassian.jira.plugin.... ] Richard Opalka commented on JBWS-3084: -------------------------------------- There's also https://issues.apache.org/jira/browse/CXF-3065 related to this issue -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira