Attachment error on client

[Wörner Till <Ti...@t-systems.com>]

Hi,

first I want to thank all the guys that helped me with my attachment problem. With the examples from the wstk and a bit of try and error I can get a message with an attached JPEG file from the server to client. When I write out the message to System.out on the server, it looks as it should. But on the client invoke-call throws an exception with following text:

"org.xml.sax.SAXParseException: Content is not allowed in prolog."

Anyone know why?

Greetings,
Till

-- 
T-Systems GEI GmbH

Hausanschrift: Eichhornstraße 3, D-10785 Berlin
Postanschrift: D-10875 Berlin
Telefon: +49 (30) 2554 3254
E-Mail: Till.Woerner@t-systems.com 

mapping javax.xml.soap.SOAPFault to AxisFault

[Chris Haddad <ch...@cobia.net>]

Axis - 

If a service method desires to conform to the JAX-RPC standard, should
it throw javax.xml.rpc.soap.SOAPFault instead of
org.apache.axis.AxisFault?

If the code should be ideally throwing SOAPFault, should Axis be passing
back to the client more than just the faultstring from the SOAPFault
exception object?

The default behavior for unknown exception types such as SOAPFault does
not allow the transmission of custom faultcodes, faultactors, and
faultdetails to the client.

The intent of the proposed modification is to allow custom faultcodes,
faultactors, and faultdetails to be added to the fault while throwing a
JAX-RPC compliant fault in the service method.

To achieve this goal, the AxisFault.makeFault method needs to be
enhanced to convert the SOAPFault properties into the corresponding
AxisFault properties.

For example, a simple addition to AxisFault.makeFault()  - 

if (e instanceof SOAPFault) {
        SOAPFault exSOAP = (SOAPFault)e;

        return new AxisFault(new
QFault(exSOAP.getFaultCode()),exSOAP.getFaultString(),exSOAP.getFaultAct
or(),convertDetails(exSOAP.getDetail()));
}

The convertDetail method would convert the javax.xml.soap.Detail object
to Element[].


Is this a valid proposal?



/Chris