axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mary Thompson (JIRA)" <>
Subject [jira] Commented: (AXIS2-1811) Enumerated types fail to map into return messages when rampart-1.1 has been engaged.
Date Mon, 04 Dec 2006 18:32:21 GMT
    [ ] 
Mary Thompson commented on AXIS2-1811:

I had copied all the rampart jars into the axis server lib, but not the 
client side. But I was not even engaging rampart on the client side 
because when I tried I was getting module not found or invalid module 
errors. When I copied the rampart jar files to the client class path, it 
engaged the module correctly, but now I get similar errors both on the 
server and client side. e.g.

Dec 4, 2006 10:00:19 AM forceExpand
SEVERE: forceExpand: expected element name cancelReservationResponse, 
found resStatus

OSCARSStub threw exception
         at Source)
         at Source)
         at CancelReservationClient.main(Unknown Source)

I am using the Nov 29 snapshot of axis2 which seems to still be the most 
recent, and rampart-1.1-RC1. Is there a later nightly build of rampart, 
and if so where is it?

I am using jdk 1.5.0, MacOSX 10.4 for client and standalone server, 
FreeBSD for axis deployed in Tomcat 5.5.17. Using adb binding.


> Enumerated types fail to map into return messages when rampart-1.1 has been engaged.
> ------------------------------------------------------------------------------------
>                 Key: AXIS2-1811
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: modules
>    Affects Versions: nightly
>         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 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(
>    at org.apache.axis2.engine.AxisEngine.createFaultMessageContext(
>    at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService(
>    at org.apache.http.protocol.HttpService.handleRequest(
>    at
>    at$Worker.runTask(
>    at$
>    at
> Caused by: java.lang.ExceptionInInitializerError
>    at org.apache.rampart.RampartMessageData.<init>(
>    at
>    at org.apache.rampart.handler.RampartSender.invoke(
>    at org.apache.axis2.engine.Phase.invoke(
>    at org.apache.axis2.engine.AxisEngine.invoke(
>    at org.apache.axis2.engine.AxisEngine.send(
>    at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.receive(AbstractInOutSyncMessageReceive
>    at org.apache.axis2.engine.AxisEngine.receive(
>    at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(
>    at org.apache.axis2.transport.http.HTTPWorker.service(
>    at org.apache.axis2.transport.http.server.DefaultHttpServiceProcessor.doService(

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message