I have also been wondering about this exact question.
Please correct me if I am wrong, but I think the issue is the
<ns:return> tag. At the moment, the response looks like this:
<ns:retrieveCustomerIdentifyByCFResponse xmlns:ns="http://my.it/data";>
<ns:return>ciao</ns:return>
</ns:retrieveCustomerIdentifyByCFResponse>
I think the question is, is there a way to make the response look like
this:
<ns:retrieveCustomerIdentifyByCFResponse xmlns:ns="http://my.it/data";>
ciao
</ns:retrieveCustomerIdentifyByCFResponse>
The <ns:return> tag is something being added by AXIS2. Can we shut that
off?
Anthony
-----Original Message-----
From: Paul Fremantle [mailto:[EMAIL PROTECTED]
Sent: Friday, August 03, 2007 7:22 AM
To: [email protected]
Subject: Re: Axis2 byte[] transfer/serialization bug ?!
Georgia
I'm still not clear :) Sorry!
What is the problem with th response?
Paul
On 8/3/07, Georgia Giacobbi <[EMAIL PROTECTED]> wrote:
The my error is in soap message response
see this:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<soapenv:Envelope
xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";>
<soapenv:Body>
<ns:retrieveCustomerIdentifyByCFResponse xmlns:ns="http://my.it/data";>
<ns:return>ciao</ns:return>
</ns:retrieveCustomerIdentifyByCFResponse>
</soapenv:Body>
</soapenv:Envelope>
in the my WSDL, i don't declare return element, and in the web
Services
i declare with JAX-WS annotation the result name
(@WebResult(name="myReturn",partName="myReturn",targetNamespace="http://
my.it/data")
)
Paul Fremantle ha scritto:
Georgia
What exactly is your error?
I'm not clear from the email.
Paul
On 8/3/07, reichan <[EMAIL PROTECTED]> wrote:
Hi Georgi
I have the similar error.
Can i disable the "return" element autogenerated by AXIS2?!
I have tried to indicate the name of the ws using the annotation of
JAX-WS,
WebResult, but seems that AXIS2 don't care about those.
I'm using AXIS2 1.3 RC2.
Georgi Yonchev wrote:
Thilina Gunarathne wrote:
Looks like a bug... Please report a JIRA...
You may also try replacing byte[] with
javax.activation.DataHandler...
DataHandler is the recommended way when using large
attachments...
thanks,
Thilina
On 7/24/07, Georgi Yonchev <[EMAIL PROTECTED]> wrote:
Thilina Gunarathne wrote:
and Deepal, yes works fine, but try it with larger byte[]
size,
with larger, in the payload goes array from bytes ?!
not encoded in base64 ..
Not clear what you meant?... Do they go as native binary in the
form
of an attachment or inside the soap body...
Thanks,
Thilina
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
inside in the soap body, the bytes are not encoded in base64, is
represented like integers
this is a part of the xml :
<ns:byteData>9</ns:byteData><ns:byteData>102</ns:byteData><ns:byteData>1
11</ns:byteData><ns:byteData>110</ns:byteData><ns:byteData>116</ns:byteD
ata><ns:byteData>45</ns:byteData><ns:byteData>115</ns:byteData><ns:byteD
ata>105</ns:byteData><ns:byteData>122</ns:byteData><ns:byteData>101</ns:
byteData><ns:byteData>58</ns:byteData><ns:byteData>32</ns:byteData><ns:b
yteData>49</ns:byteData><ns:byteData>48</ns:byteData
<ns:byteData>112</ns:byteData><ns:byteData>116</ns:byteData><ns:byteData
59</ns:byteData><ns:byteData>13</ns:byteData><ns:byteData>10</ns:byteDa
ta><ns:byteData>9</ns:byteData><ns:byteData>102</ns:byteData><ns:byteDat
a>111</ns:byteData><ns:byteData>110</ns:byteData><ns:byteData>116</ns:by
teData><ns:byteData>45</ns:byteData><ns:byteData>119</ns:byteData><ns:by
teData>101</ns:byteData><ns:byteData>105</ns:byteData><ns:byteData>103</
ns:byteData><ns:byteData>104</ns:byteData><ns:byteData>116</ns:byteData>
<ns:byteData>58</ns:byteData><ns:byteData>32</ns:byteData><ns:byteData>1
10</ns:byteData><ns:byteData>111</ns:byteData><ns:byteData>114</ns:byteD
ata><ns:byteData>109</ns:byteData><ns:byteData>97</ns:byteData><ns:byteD
ata>108</ns:byteData><ns:byteData>59</ns:byteData><ns:byteData>13</ns:by
teData><ns:byteData>10</ns:byteData><ns:byteData>125</ns:byteData><ns:by
teData>13</ns:byteData><ns:byteData>10</ns:byteData><ns:byteData>46</ns:
byteData><ns:byteData>99</ns:byteData><ns:byteData>111</ns:byteData><ns:
byteData>110</n
s:byteData><ns:byteData
2000
116</ns:byteData><ns:byteData>101</ns:byteData><ns:byteData>110</ns:byte
Data>
this happens only when i set the byte[] in Complex return object
class Result{
private byte[] bytes;
set..
get..
}
and the call likes:
public Res test(){
..set byte[] in res
return res;
}
if the call is :
public byte[] test(){
..
}
everything goes well...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hi Thilina,
i report it on JIRA, and is fixed on both tags/branches in the
svn...
can you give some hints about this DataHandler ...
some example how to implement it,
10x a lot in advance :)
George
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Axis2-byte---transfer-serialization-bug--%21-tf413
4147.html#a11979538
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
