[
https://issues.apache.org/jira/browse/RAMPART-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13463955#comment-13463955
]
Brian Reinhold commented on RAMPART-392:
----------------------------------------
Yes. One just has to be aware the method .toStringWithConsume() on OMElements
has side affects it didn't have in earlier versions. Perhaps it was meant to
always have those affects but it did not.
> Rampart unable to insert security token into security header
> ------------------------------------------------------------
>
> Key: RAMPART-392
> URL: https://issues.apache.org/jira/browse/RAMPART-392
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Affects Versions: 1.6.2
> Environment: Windows 7, jre, jdk 6 or 7, Eclipse client, Tomcat
> Axis2/Rampart for both STS service and 'myCommunicate' service. Axis2 1.6.2,
> Axiom 1.2.13 OR 1.2.14 Snapshot sept 21, 2012.
> NOTE this is 1.6.2 it DOES exist but the bug infrastructure says it doesn't.
> Reporter: Brian Reinhold
> Priority: Critical
> Labels: patch
> Fix For: 1.6.2
>
>
> When attempting to add the security token obtained from the default STS
> service, and 'unexpected end of document' exception is thrown. Stack trace
> follows:
> Unexpected END_DOCUMENT eventorg.apache.axiom.om.OMException: Unexpected
> END_DOCUMENT event
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.parserNext(StAXOMBuilder.java:660)
> at
> org.apache.axiom.om.impl.builder.StAXOMBuilder.next(StAXOMBuilder.java:189)
> at
> org.apache.axiom.om.impl.common.OMContainerHelper.buildNext(OMContainerHelper.java:162)
> at
> org.apache.axiom.om.impl.common.OMContainerHelper.getFirstOMChild(OMContainerHelper.java:174)
> at
> org.apache.axiom.om.impl.dom.ParentNode.getFirstOMChild(ParentNode.java:126)
> at
> org.apache.axiom.om.impl.dom.ParentNode.getFirstChild(ParentNode.java:185)
> at
> org.apache.axiom.om.impl.dom.DocumentImpl.importNode(DocumentImpl.java:352)
> at
> org.apache.axiom.om.impl.dom.DocumentImpl.importNode(DocumentImpl.java:354)
> at
> org.apache.rampart.util.RampartUtil.appendChildToSecHeader(RampartUtil.java:826)
> at
> org.apache.rampart.util.RampartUtil.insertSiblingAfter(RampartUtil.java:834)
> at
> org.apache.rampart.builder.BindingBuilder.handleSupportingTokens(BindingBuilder.java:381)
> at
> org.apache.rampart.builder.TransportBindingBuilder.build(TransportBindingBuilder.java:148)
> at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:140)
> at
> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:65)
> at org.apache.axis2.engine.Phase.invokeHandler(Phase.java:340)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:313)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:262)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:427)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:406)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:229)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:165)
> There was no problem when using Axis2 1.5.1 and Rampart 1.5.1 and Axiom
> 1.2.9. The problem shows up on the client side when moving to versions 1.6.2
> and axiom 1.2.14 to solve server side bugs with respect to SAML. See JIRA
> AXIOM-439
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
