You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Mary Thompson (JIRA)" <ji...@apache.org> on 2006/12/03 07:54:20 UTC

[jira] Created: (AXIS2-1811) Enumerated types fail to map into return messages when rampart-1.1 has been engaged.

Enumerated types fail to map into return messages when rampart-1.1 has been engaged.
------------------------------------------------------------------------------------

                 Key: AXIS2-1811
                 URL: http://issues.apache.org/jira/browse/AXIS2-1811
             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


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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] Commented: (AXIS2-1811) Enumerated types fail to map into return messages when rampart-1.1 has been engaged.

Posted by "Ruchith Udayanga Fernando (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/AXIS2-1811?page=comments#action_12455169 ] 
            
Ruchith Udayanga Fernando commented on AXIS2-1811:
--------------------------------------------------

I tried your service and client (made sure Rampart is engaged) with the latest Rampart and Axis2-1.1.1-SNAPSHOT and the request and response passes through Rampart handlers without any problem, as shown below.

Did you copy all jars in the "rampart-1.1-RC1/lib" dir into the "lib" directory of axis2 and the classpath of the client?


==============
Listen Port: 9080
Target Host: localhost
Target Port: 8080
==== Request ====
POST /axis2/services/OSCARSSam HTTP/1.1
SOAPAction: "http://oscars.es.net/OSCARS/cancelReservation"
User-Agent: Axis2
Host: localhost:9080
Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8

1d9
<?xml version='1.0' encoding='UTF-8'?>
   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
      <soapenv:Header>
         <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" soapenv:mustUnderstand="1" />
      </soapenv:Header>
      <soapenv:Body>
         <ns1:cancelReservation xmlns:ns1="http://oscars.es.net/OSCARS">
            <tag xmlns="http://oscars.es.net/OSCARS">tag1</tag>
         </ns1:cancelReservation>
      </soapenv:Body>
   </soapenv:Envelope>0
==== Response ====
HTTP/1.1 200 OK
Date: Sun, 03 Dec 2006 13:27:13 GMT
Server: Simple-Server/1.1
Transfer-Encoding: chunked
Content-Type: text/xml; charset=UTF-8

123
<?xml version='1.0' encoding='UTF-8'?>
   <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
      <soapenv:Header />
      <soapenv:Body>
         <ns3:cancelReservationResponse xmlns:ns3="http://oscars.es.net/OSCARS">FINISHED</ns3:cancelReservationResponse>
      </soapenv:Body>
   </soapenv:Envelope>0

==============

> Enumerated types fail to map into return messages when rampart-1.1 has been engaged.
> ------------------------------------------------------------------------------------
>
>                 Key: AXIS2-1811
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1811
>             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 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] Commented: (AXIS2-1811) Enumerated types fail to map into return messages when rampart-1.1 has been engaged.

Posted by "Mary Thompson (JIRA)" <ji...@apache.org>.
    [ http://issues.apache.org/jira/browse/AXIS2-1811?page=comments#action_12455380 ] 
            
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.

server:
Dec 4, 2006 10:00:19 AM 
org.apache.axiom.om.impl.llom.OMSourcedElementImpl forceExpand
SEVERE: forceExpand: expected element name cancelReservationResponse, 
found resStatus

client:
OSCARSStub threw exception
org.apache.axiom.om.impl.llom.OMElementImpl
java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMElementImpl
         at 
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101)
         at 
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:312)
         at 
net.es.oscars.service.OSCARSSamStub.cancelReservation(Unknown Source)
         at net.es.oscars.client.Client.cancelReservation(Unknown 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.


Mary



> Enumerated types fail to map into return messages when rampart-1.1 has been engaged.
> ------------------------------------------------------------------------------------
>
>                 Key: AXIS2-1811
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1811
>             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 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] Updated: (AXIS2-1811) Enumerated types fail to map into return messages when rampart-1.1 has been engaged.

Posted by "Mary Thompson (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-1811?page=all ]

Mary Thompson updated AXIS2-1811:
---------------------------------

    Attachment: OSCARSSample.tar

wsdl, client and server code.

> Enumerated types fail to map into return messages when rampart-1.1 has been engaged.
> ------------------------------------------------------------------------------------
>
>                 Key: AXIS2-1811
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1811
>             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 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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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


[jira] Assigned: (AXIS2-1811) Enumerated types fail to map into return messages when rampart-1.1 has been engaged.

Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2-1811?page=all ]

Deepal Jayasinghe reassigned AXIS2-1811:
----------------------------------------

    Assignee: Ruchith Udayanga Fernando

> Enumerated types fail to map into return messages when rampart-1.1 has been engaged.
> ------------------------------------------------------------------------------------
>
>                 Key: AXIS2-1811
>                 URL: http://issues.apache.org/jira/browse/AXIS2-1811
>             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
>         Assigned To: Ruchith Udayanga Fernando
>         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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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