You are viewing a plain text version of this content. The canonical link for it is here.
Posted to rampart-dev@ws.apache.org by "Jorge Fernández (JIRA)" <ji...@apache.org> on 2007/08/09 11:53:42 UTC
[jira] Issue Comment Edited: (RAMPART-70) RAMPART SNAPSHOT Problems
on building messages
[ https://issues.apache.org/jira/browse/RAMPART-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518675 ]
informaticu007-pfc edited comment on RAMPART-70 at 8/9/07 2:52 AM:
----------------------------------------------------------------
Yes, I have addressing at client and server side. The header is present at client side because I'm using basic rampart configuration and I'm encrypting that header (sorry I must have specified this) and rampart doesn't complain of a missing element.
When I don't engage rampart everything works OK.
Sorry but I can't attach this code on the JIRA because it contains some pieces of code that can't be published.
If you can't reproduce the JIRA, I'll try to make a sample if that's OK.
was (Author: informaticu007-pfc):
Yes, I have addressing at client and server side. The header is present at client side because I'm using basic rampart configuration and I'm encrypting that header (sorry I must have specified this) and rampart doesn't complain of a missing element.
When I don't engage rampart everything works OK.
Sorry but I can't attach this code on the JIRA because it contains some pieces of code that can't be published.
> RAMPART SNAPSHOT Problems on building messages
> ----------------------------------------------
>
> Key: RAMPART-70
> URL: https://issues.apache.org/jira/browse/RAMPART-70
> Project: Rampart
> Issue Type: Bug
> Components: rampart-core
> Affects Versions: 1.3
> Environment: Windows XP SP2, Java 1.6.0, Tomcat 6.0
> Reporter: Jorge Fernández
> Priority: Blocker
>
> I'm having some problems with last rampart snapshot (08/08/2007 19:17 and the one before). Please, read 3 cases:
> First, I'm using basic configuration on client as with 1.2 and policy on server side.
> Rampart is engaged in both. In server is engaged in service scope and in
> client at global scope.
> I receive an exception from service that makes me thing about a problem
> in phases order:
> org.apache.axis2.AxisFault: The org.apache.axis2.AxisFault: A required
> header representing a Message Addressing Property is not present
> at
> org.apache.axis2.addressing.AddressingFaultsHelper.triggerAddressingFault(AddressingFaultsHelper.java:355)
> at
> org.apache.axis2.addressing.AddressingFaultsHelper.triggerMessageAddressingRequiredFault(AddressingFaultsHelper.java:281)
> at
> org.apache.axis2.handlers.addressing.AddressingValidationHandler.checkMessageIDHeader(AddressingValidationHandler.java:168)
> at
> org.apache.axis2.handlers.addressing.AddressingValidationHandler.invoke(AddressingValidationHandler.java:56)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132)
> at
> org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
> at
> org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:710)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
> at
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)
> at
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
> at
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:230)
> at
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175)
> at
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128)
> at
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:104)
> at
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109)
> at
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:261)
> at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844)
> at
> org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:581)
> at
> org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447)
> at java.lang.Thread.run(Unknown Source)
> header is required when WS-Addressing is in use but was not sent.
> at
> org.apache.axis2.handlers.addressing.AddressingInFaultHandler.invoke(AddressingInFaultHandler.java:114)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:132)
> at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:336)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> at client.Medici_LinkStub.validate(Medici_LinkStub.java:744)
> at client.ClientUtilities.validateTest(ClientUtilities.java:61)
> at client.Client.main(Client.java:34)
> Second, I removed configuration from client but keeping rampart engaged
> and I receive this exception from the service:
> org.apache.axis2.AxisFault: java.lang.NullPointerException
> at
> org.apache.axis2.util.Utils.getInboundFaultFromMessageContext(Utils.java:486)
> at
> org.apache.axis2.description.OutInAxisOperationClient.handleResponse(OutInAxisOperation.java:343)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:389)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> at client.Medici_LinkStub.validate(Medici_LinkStub.java:744)
> at client.ClientUtilities.validateTest(ClientUtilities.java:61)
> at client.Client.main(Client.java:34)
> Third, I remove <module ref="rampart"/> from services.xml and the first
> operation works ok but for the nexts I see an exception ocurred in the
> client:
> org.apache.axis2.AxisFault: Error in extracting message properties
> at
> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:68)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:292)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:212)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:377)
> at
> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:374)
> at
> org.apache.axis2.description.OutInAxisOperationClient.executeImpl(OutInAxisOperation.java:211)
> at
> org.apache.axis2.client.OperationClient.execute(OperationClient.java:163)
> at
> client.Medici_LinkStub.getDetailedMonitoringStages(Medici_LinkStub.java:4413)
> at
> client.ClientUtilities.getDetailedMonitoringStagesTest(ClientUtilities.java:356)
> at client.Client.main(Client.java:60)
> Caused by: org.apache.rampart.RampartException: Error in extracting
> message properties
> at
> org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:293)
> at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:58)
> at
> org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:62)
> ... 9 more
> Caused by: org.apache.ws.security.WSSecurityException: Error in
> converting SOAP Envelope to Document; nested exception is:
> java.lang.ClassCastException:
> org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to org.apache.axiom.soap.SOAPHeaderBlock
> at
> org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:157)
> at
> org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:150)
> ... 11 more
> Caused by: java.lang.ClassCastException:
> org.apache.axiom.om.impl.llom.OMElementImpl cannot be cast to org.apache.axiom.soap.SOAPHeaderBlock
> at
> org.apache.rampart.util.Axis2Util.getDocumentFromSOAPEnvelope(Axis2Util.java:107)
> ... 12 more
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.