Mailing-List: contact dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ws.apache.org
Date: Mon, 3 Oct 2011 09:04:39 +0000 (UTC)
From: "Colm O hEigeartaigh (Closed) (JIRA)" <jira@apache.org>
To: dev@ws.apache.org
Message-ID: 
 <296328891.2516.1317632679079.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2086222510.70866.1307339327369.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Closed] (WSS-293) Getting exception when rampart is engaged
 without addressing at client side
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/WSS-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Colm O hEigeartaigh closed WSS-293.
-----------------------------------

    
> Getting exception when rampart is engaged without addressing at client side
> ---------------------------------------------------------------------------
>
>                 Key: WSS-293
>                 URL: https://issues.apache.org/jira/browse/WSS-293
>             Project: WSS4J
>          Issue Type: Bug
>          Components: WSS4J Core
>    Affects Versions: 1.5.10
>         Environment: windows
>            Reporter: shivendra tripathi
>            Assignee: Colm O hEigeartaigh
>
> Steps to reproduce:
> 1. Engage rampart and use policy based configuarion
> 2. Don't engage any other module like addressing 
> 3. Use OperationClient at client side and create soap envelope as follows
>         SOAPEnvelope envelope = soapFactory.createSOAPEnvelope();// don't use soapFactory.getDefaultEnvelope() to create soap envelope
>     	SOAPBody sb = soapFactory.createSOAPBody(envelope);
> On execution following exception is thrown, since WSS4J is inserting the header which is instance of OMElement and not of SOAPHeader. 
> Caused by: org.apache.rampart.RampartException: Error in extracting message properties
> 	at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:389)
> 	at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:61)
> 	at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:64)
> 	... 59 more
> Caused by: org.apache.axiom.soap.SOAPProcessingException: SOAP Envelope can not have children other than SOAP Header and Body
> 	at org.apache.axiom.soap.impl.dom.SOAPEnvelopeImpl.checkChild(SOAPEnvelopeImpl.java:110)
> 	at org.apache.axiom.soap.impl.dom.SOAPEnvelopeImpl.insertBefore(SOAPEnvelopeImpl.java:164)
> 	at org.apache.ws.security.util.WSSecurityUtil.prependChildElement(WSSecurityUtil.java:646)
> 	at org.apache.ws.security.util.WSSecurityUtil.findWsseSecurityHeaderBlock(WSSecurityUtil.java:722)
> 	at org.apache.ws.security.message.WSSecHeader.insertSecurityHeader(WSSecHeader.java:146)
> 	at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:379)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org