Probably you have different use/style settings and client and server side.

On 4/23/07, Andreas Gabel <[EMAIL PROTECTED]> wrote:
Hey Guys,

  i had a WS which runs with AXIS 1.4. As you can see from the parts of
WSDL the method is a void method. The service runs as document/literal
unwrapped.
  If i create a xFire client i get an Exception!!!
  Thats because Axis 1.4 send me not an empty SoapBody. The answer from
Axis looks like:

  <soap:Envelope>
          <soap:Body>
                      <notifyPermissionCreationResponse/> --> methodName
with Response which is HardCoded in  Axis 1.4
           </soap:Body>
  </soap:Envelope>


  And the Client from xfire expects the following Response:


  <soap:Envelope>
          <soap:Body>
           </soap:Body>
  </soap:Envelope>

  How can i solve this Problem? Maybe it is a Bug of AXIS. But we can
not change this WS from AXIS to xFire.


  Greetings

  Andreas



  Exception in thread "main" org.codehaus.xfire.XFireRuntimeException:
Could not invoke service.. Nested exception is
org.codehaus.xfire.fault.XFireFault: Index: 0, Size: 0
org.codehaus.xfire.fault.XFireFault: Index: 0, Size: 0
    at org.codehaus.xfire.fault.XFireFault.createFault(XFireFault.java:89)
    at org.codehaus.xfire.client.Client.onReceive(Client.java:391)
    at
org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:139)
    at
org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
    at
org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
    at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
    at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:75)
    at org.codehaus.xfire.client.Client.invoke(Client.java:335)
    at
org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)
    at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
    at $Proxy12.notifyPermissionCreation(Unknown Source)
    at xfiretest.XfireClientCallAxis.main(XfireClientCallAxis.java:37)
Caused by: java.lang.IndexOutOfBoundsException: Index: 0, Size: 0
    at java.util.LinkedList.entry(Unknown Source)
    at java.util.LinkedList.get(Unknown Source)
    at java.util.Collections$UnmodifiableList.get(Unknown Source)
    at
org.codehaus.xfire.service.binding.AbstractBinding.read(AbstractBinding.java:187)
    at
org.codehaus.xfire.service.binding.DocumentBinding.readMessage(DocumentBinding.java:32)
    at
org.codehaus.xfire.soap.handler.SoapBodyHandler.invoke(SoapBodyHandler.java:42)
    at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
    at org.codehaus.xfire.client.Client.onReceive(Client.java:387)
    ... 10 more





  <message name="NotifyPermissionCreationIn">
    <part name="CreationNotification"
element="mca:PermissionCreationNotification"/>
  </message>
  <message name="NotifyPermissionCreationResponse"/>

  <portType name="blabla">
    <operation name="notifyPermissionCreation">
       <input name="notifyPermissionCreationIn"
message="tns:NotifyPermissionCreationIn"/>
      <output name="NotifyPermissionCreationResponse"
message="tns:NotifyPermissionCreationResponse"/>
      <fault name="ValidationException"
message="tns:ValidationExceptionMessage"/>
    </operation>

  <binding name="blabla" type="tns:bla">
    <soap:binding transport="http://schemas.xmlsoap.org/soap/http"; />
    <operation name="notifyPermissionCreation">
      <soap:operation
soapAction="http://www.skidata.com/mcaccessws:NotifyPermissionCreationIn";
style="document" />
      <input name="notifyPermissionCreationIn"><soap:body use="literal"
/></input>
      <output name="NotifyPermissionCreationResponse"><soap:body
use="literal" /></output>
      <fault name="ValidationException"><soap:fault use="literal"
name="ValidationException"/></fault>
    </operation>

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email




--
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.

---------------------------------------------------------------------
To unsubscribe from this list please visit:

   http://xircles.codehaus.org/manage_email

Reply via email to