RE: No headers in response

Okay, I didn't mean to imply that the behavior was wrong, I just needed to know what I needed to do. Since the namespace is in the standard I should be able to hardcode one. Brian -Original Message- From: Andreas Veithen [mailto:[email protected]] Sent: Tuesday, October 02, 2012

Build failed in Jenkins: axis2-transports-trunk #1069

See -- Started by upstream project "Axis2" build number 1835 Started by upstream project "Axis2" build number 1836 Building remotely on ubuntu3 in workspace

[jira] [Updated] (AXIS-2093) XPathAPI cannot find namespace nodes in Axis dom

[ https://issues.apache.org/jira/browse/AXIS-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS-2093: -- Labels: dom-compatibility (was: ) > XPathAPI cannot find namespace nodes in Axis dom >

[jira] [Updated] (AXIS-2125) DOMException (NAMESPACE_ERR) if we run a XPath Query using Sun JDK1.5 on a SOAPPart DOM

[ https://issues.apache.org/jira/browse/AXIS-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS-2125: -- Labels: dom-compatibility (was: ) > DOMException (NAMESPACE_ERR) if we run a XPath Query us

[jira] [Updated] (AXIS-2163) Horrendous implementation of DOM APIs, especially those dealing with Attribute Nodes, in org.apache.axis.message

[ https://issues.apache.org/jira/browse/AXIS-2163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS-2163: -- Labels: dom-compatibility (was: ) > Horrendous implementation of DOM APIs, especially those

[jira] [Updated] (AXIS-2857) IlegalArgumentException on SimpleDeserializer onEndElement

[ https://issues.apache.org/jira/browse/AXIS-2857?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS-2857: -- Labels: (was: 1.4 Axis IlegalArgumentException) > IlegalArgumentException on SimpleDeseria

[jira] [Resolved] (AXIS-1581) NullPointerException - null reqMsg in Call.java

[ https://issues.apache.org/jira/browse/AXIS-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen resolved AXIS-1581. --- Resolution: Fixed > NullPointerException - null reqMsg in Call.java >

[jira] [Commented] (AXIS-1581) NullPointerException - null reqMsg in Call.java

[ https://issues.apache.org/jira/browse/AXIS-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13468035#comment-13468035 ] Hudson commented on AXIS-1581: -- Integrated in axis-trunk #166 (See [https://builds.apache.org

[jira] [Assigned] (AXIS-1581) NullPointerException - null reqMsg in Call.java

[ https://issues.apache.org/jira/browse/AXIS-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen reassigned AXIS-1581: - Assignee: Andreas Veithen > NullPointerException - null reqMsg in Call.java >

[jira] [Updated] (AXIS-1581) NullPointerException - null reqMsg in Call.java

[ https://issues.apache.org/jira/browse/AXIS-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Veithen updated AXIS-1581: -- Fix Version/s: 1.4.1 > NullPointerException - null reqMsg in Call.java > ---

[jira] [Created] (AXIS2-5432) add command-line option to wsdl2java.sh to connect to arbitrary https sites (dummy trust stores)

Ralf Hauser created AXIS2-5432: -- Summary: add command-line option to wsdl2java.sh to connect to arbitrary https sites (dummy trust stores) Key: AXIS2-5432 URL: https://issues.apache.org/jira/browse/AXIS2-5432

[jira] [Commented] (AXIS2-5431) No Header in response

[ https://issues.apache.org/jira/browse/AXIS2-5431?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467675#comment-13467675 ] Martin Gainty commented on AXIS2-5431: -- if the SOAPHeaders were never populated in S

[jira] [Created] (AXIS2-5431) No Header in response

Martin Gainty created AXIS2-5431: Summary: No Header in response Key: AXIS2-5431 URL: https://issues.apache.org/jira/browse/AXIS2-5431 Project: Axis2 Issue Type: Bug Components: ker

Re: No headers in response

On Tue, Oct 2, 2012 at 2:01 PM, Brian Reinhold wrote: > Martin, > > > > How do I get an attribute from an OMElement? This OMElement is one of the > addressing elements. When I try: > > > > QName qname = new QName("mustUnderstand"); > > String mustUnderstand = > soap

[jira] [Commented] (AXIS-2814) could not find deserializer for type

[ https://issues.apache.org/jira/browse/AXIS-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13467634#comment-13467634 ] Nicolas commented on AXIS-2814: --- We have exactly the same problem, is there a fix or workarou