[ https://issues.jboss.org/browse/AS7-4201?page=com.atlassian.jira.plugin.s... ] Will Tatam commented on AS7-4201: --------------------------------- Our soap client send an extra header that contains the REMOTE_ADDR of the user who is browsing the website back to the application server. This is used so the web service can pass the website visitor's ip address to the bank for anti-fraud checks. The code below worked fine in AS5. When I made this bug report we had axis1 bundled in with our ear. I have not yet re-tested since we replaced axis with jaxws for consuming third party web services @Stateless @WebService public class MyClass implements MyInterface { public String testMethod() { return "Call came from " + getVisitorIp(); } private String getVisitorIp() { try { SOAPMessageContext jaxwsContext = (SOAPMessageContext) wsContext.getMessageContext(); if(jaxwsContext == null) { logger.warn("getVisitorIp() SOAPMessageContext is NULL"); return null; } SOAPHeader soapHeader = jaxwsContext.getMessage().getSOAPHeader(); if(soapHeader == null) { logger.warn("getVisitorIp() SOAPHeader is NULL"); return null; } // Extract All header elements. Iterator headerElements = soapHeader.examineAllHeaderElements(); while (headerElements.hasNext()) { SOAPHeaderElement element = (SOAPHeaderElement) headerElements.next(); logger.debug("soapHeader." + element.getElementName().getLocalName() + " = " + element.getValue()); if(element.getElementName().getLocalName().equalsIgnoreCase("REMOTE_ADDR")) { ip = element.getValue(); } } } catch (SOAPException se) { logger.error("Failed to parse SOAP Header", se); } return ip; } } -- 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

[ https://issues.jboss.org/browse/AS7-4201?page=com.atlassian.jira.plugin.s... ] Alessio Soldano commented on AS7-4201: -------------------------------------- OK, this explain the "issue". You're assuming the message context is a SOAPMessageContext in the ws endpoints, which is not granted. That's granted in SOAPHandler instances instead, as per my former message. This said, I believe you have better approaches here; http://cxf.apache.org/faq.html#FAQ-HowcanIaddsoapheaderstotherequest%2Fre... summarizes your options very well. Basically either your do what you're currently doing, but in a SOAPHandler, or you go the standard approach and use @WebParam(header=true) and add the header to the contract. -- 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

[ https://issues.jboss.org/browse/AS7-4201?page=com.atlassian.jira.plugin.s... ] Will Tatam commented on AS7-4201: --------------------------------- Thanks, but that link is about adding headers. We are trying to read headers and the example does not show what context is or how it was obtained -- 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

[ https://issues.jboss.org/browse/AS7-4201?page=com.atlassian.jira.plugin.s... ] Will Tatam commented on AS7-4201: --------------------------------- Would this example work even though it's metro rather than cxf ? http://metro.java.net/2.0.1/guide/SOAP_headers.html -- 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

[ https://issues.jboss.org/browse/AS7-4201?page=com.atlassian.jira.plugin.s... ] Alessio Soldano commented on AS7-4201: -------------------------------------- The code in the link is about the cxf proprietary way of adding headers; I was referring more to 1 (the "jaxws standard way") and 2/3. If 2/3 is not good for you because you don't want to update the method signatures and/or endpoint wsdl contract, you should go the jaxws standard way, i.e. keep on using SAAJ as you've doing, but within a SOAPHandler. -- 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