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 "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org> on 2007/08/08 04:01:59 UTC
[jira] Resolved: (RAMPART-11) Enumerated types fail to map into
return messages when rampart-1.1 has been engaged.
[ https://issues.apache.org/jira/browse/RAMPART-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ruchith Udayanga Fernando resolved RAMPART-11.
----------------------------------------------
Resolution: Cannot Reproduce
> Enumerated types fail to map into return messages when rampart-1.1 has been engaged.
> ------------------------------------------------------------------------------------
>
> Key: RAMPART-11
> URL: https://issues.apache.org/jira/browse/RAMPART-11
> Project: Rampart
> Issue Type: Bug
> Environment: Axis 2-1.1.1 nov 29 and Axis2-1.1 release , Rampart 1.1-RC1, fails in the standalone Axis server as well as in
> axis deployed in Tomcat. The client and server code were generated by Axis 2-1.1.1 wsdl2java.
> Reporter: Mary Thompson
> Attachments: OSCARSSample.tar
>
>
> I have a service that returns an enumerated type. In the absence of the rampart module, it works correctly, but once the rampart 1.1 module is engaged by axis2 it fails in the following way. It doesn't matter if my service is actually using rampart to do anything with the message, it fails in both cases.
> Axis log reports
> Dec 2, 2006 10:23:31 PM org.apache.axiom.om.impl.llom.OMSourcedElementImpl forceExpand
> SEVERE: forceExpand: expected element name cancelReservationResponse, found resStatus
> The returned exception is:
> Caused by: java.lang.Exception: java.lang.Exception: java.lang.ExceptionInInitializerError
> at org.apache.axis2.engine.AxisEngine.extractFaultInformationFromMessageContext(AxisEngine.java:443)
> at org.apache.axis2.engine.AxisEngine.createFaultMessageContext(AxisEngine.java:249)
> at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService(DefaultHttpServiceProcessor.java:194)
> at org.apache.http.protocol.HttpService.handleRequest(HttpService.java:123)
> at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.run(DefaultHttpServiceProcessor.java:251)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:665)
> at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:690)
> at java.lang.Thread.run(Thread.java:613)
> Caused by: java.lang.ExceptionInInitializerError
> at org.apache.rampart.RampartMessageData.<init>(RampartMessageData.java:291)
> at org.apache.rampart.MessageBuilder.build(MessageBuilder.java:56)
> at org.apache.rampart.handler.RampartSender.invoke(RampartSender.java:59)
> at org.apache.axis2.engine.Phase.invoke(Phase.java:382)
> at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:522)
> at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:655)
> at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceive
> r.java:48)
> at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:497)
> at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:326)
> at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:230)
> at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService(DefaultHttpServiceProcessor.java:179)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.