OK, I think thats actually a different bug - i.e. the byte[0] is only
peripherally related. Could you please open a JIRA issue for this? It would
really help debugging if you were able to attach your WSDL as well. Thanks!

- Dan

On 12/29/06, Frank Hemer <[EMAIL PROTECTED]> wrote:

On Friday 29 December 2006 20:29, Dan Diephouse wrote:
> Hmmm sounds like a bug. Could you provide the NPE? Thanks,
>

Hi Dan,

I'm not sure with exactly what settings I got the NPE, however the code I
sent
before produces an XFireFault:

org.codehaus.xfire.fault.XFireFault: Index: 1, Size: 1
        at
org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(
Soap11FaultSerializer.java:31)
        at
org.codehaus.xfire.fault.SoapFaultSerializer.readMessage(
SoapFaultSerializer.java:28)
        at
org.codehaus.xfire.soap.handler.ReadHeadersHandler.checkForFault(
ReadHeadersHandler.java:111)
        at
org.codehaus.xfire.soap.handler.ReadHeadersHandler.invoke(
ReadHeadersHandler.java:67)
        at
org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java
:131)
        at org.codehaus.xfire.client.Client.onReceive(Client.java:382)
        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 $Proxy0.containerTest(Unknown Source)
        at Test.main(Test.java:29)


Frank

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

    http://xircles.codehaus.org/manage_email




--
Dan Diephouse
Envoi Solutions
http://envoisolutions.com | http://netzooid.com/blog

Reply via email to