Re: HTTP error in Axis client
Kumar, Amit {PBSG} wrote:
> Hi,
>
> I am new to Axis. I am running into an issue while invoking a webservice from
> an Axis client. The webservice is deployed and running. I have verified the
> endpoint URL. The webservice is not getting hit from the client. Both
> webservice and the client are running on the same machine.
>
> Below is the error message.
>
> Thanks in advance.
>
> best regards
> amit
>
>
> faultCode: {http://xml.apache.org/axis/}HTTP
> faultSubcode:
> faultString: (404)404
> faultActor:
> faultNode:
> faultDetail:
> {}:return code: 404
> {http://xml.apache.org/axis/}HttpErrorCode:404
>
> (404)404
> at
> org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:744)
> at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:144)
> at
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
> at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
> at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
> at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
> at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
> at org.apache.axis.client.Call.invoke(Call.java:2767)
> at org.apache.axis.client.Call.invoke(Call.java:1910)
> at webserviceCall.main(webserviceCall.java:82)
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Hi Amit,
http error code 404 means - not found
may be you missed up something in the verification of the endpoint ?! :)
George
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 byte[] transfer/serialization bug ?!
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 :
>>
>> 9102101164511510512210158324948>
>> >11211659131091021011645119101105103104116583211014109971085913101251310469910>
>> s:byteData>>
>> 2000
>>
>> >116101110
>>
>>
>> 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]
Re: Axis2 byte[] transfer/serialization bug ?!
Georgi Yonchev 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 :
>
> 9102101164511510512210158324948
>> 11211659131091021011645119101105103104116583211014109971085913101251310469910>
> s:byteData>
> 2000
>
>
>> 116101110
>>
>
> 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]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 byte[] transfer/serialization bug ?!
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 :
910210116451151051221015832494811211659131091021011645119101105103104116583211014109971085913101251310469910116101110
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]
Re: Axis2 byte[] transfer/serialization bug ?!
Deepal jayasinghe wrote: > Hi Georgi , > > We had that issue in Axis2 1.2 and we have now fixed the issues in Axis2 > 1.3 RC2 [http://ws.apache.org/axis2/download.cgi] please download that > and see. In the meantime I deploy ur service and invoke it and got the > following responses. > > http://www.w3.org/2003/05/soap-envelope";> > > http://ws.apache.org/axis2";> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true" /> > > 0 > > > > > > > http://www.w3.org/2003/05/soap-envelope";> > > http://ws.apache.org/axis2";> > >0 > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:nil="true" /> > > > > > > http://www.w3.org/2003/05/soap-envelope";> > > http://ws.apache.org/axis2"; > xmlns:ax21="http://ws.apache.org/axis2/xsd";> > AA== > > > > > > I think all of them are correct. > > Thanks > Deepal > >> Hi, >> i developing a web service, based on Axis2, >> and the client side on gSOAP >> and i have a serious problem, >> Each call, return a complex type Result, >> how contains a String, int & comples type ResultData (i try with Object >> (anyType) but always get a null, only if i set the object like a String) >> so the ResultData contains again String, int & byte[] >> everything goes well, but when i set something bigger in byte[], the >> serialization crashes. >> i don't want to use MTOM ... >> only works when the return type of a call is byte[], isn't complex type >> >> here is a part of my wsdl: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> can you give me some help .. >> >> Best Regards >> George >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> > > > Thank you guys, i now testing the new RC but i'm getting the same results !? maybe i do wrong ? Paul how to use this DataHandler ? 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 .. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 byte[] transfer/serialization bug ?!
Paul Fremantle wrote:
> Can you post the interface (or the POJO itself) and the services.xml.
> Its not handling the byte[] correctly as a base64binary.
>
> Paul
>
> On 7/24/07, Georgi Yonchev <[EMAIL PROTECTED]> wrote:
>> Paul Fremantle wrote:
>> > George
>> >
>> > Is there any stack trace? How big is the byte[] before it crashes? Can
>> > you attach any code you've generated? What kind of databinding are you
>> > using? Which version of Axis2?
>> >
>> > Paul
>> >
>> > On 7/24/07, Georgi Yonchev <[EMAIL PROTECTED]> wrote:
>> >> Hi,
>> >> i developing a web service, based on Axis2,
>> >> and the client side on gSOAP
>> >> and i have a serious problem,
>> >> Each call, return a complex type Result,
>> >> how contains a String, int & comples type ResultData (i try with
>> Object
>> >> (anyType) but always get a null, only if i set the object like a
>> String)
>> >> so the ResultData contains again String, int & byte[]
>> >> everything goes well, but when i set something bigger in byte[], the
>> >> serialization crashes.
>> >> i don't want to use MTOM ...
>> >> only works when the return type of a call is byte[], isn't complex
>> type
>> >>
>> >> here is a part of my wsdl:
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> can you give me some help ..
>> >>
>> >> Best Regards
>> >> George
>> >>
>> >>
>> >> -
>> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> >> For additional commands, e-mail: [EMAIL PROTECTED]
>> >>
>> >>
>> >
>> >
>>
>> Hi Paul,
>> there is no stack trace, no errors, the call i succeed, but on client
>> side ... (heap exception)
>> I'm using Axis2 1.2, how bigger is the byte[] ?
>> works with 4 bytes :) later i try something real and again small (14 kB)
>> but the serialization goes nasty ..
>>
>> i can paste you the payload, which i sniffed with ethereal
>>
>> > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";>>
>> xmlns:ns="http:///xsd";>77686912177122814978<
>>
>>
>> etc..
>>
>> the service is written in POJO
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
Attaching a simple snapshot of my service ..
call test1 works with larger size
the problem is on test2 & test3, which is complex types
here is and the conf file, may there is the problem !?
public class Service {
public byte[] test1(){
return new byte[1]; //some bytes
}
public Result test2(){
Result result = new Result();
result.setBytes(new byte[1]); //some bytes
return result;
}
public Result test3(){
Result result = new Result();
ResultData data = new ResultData();
data.setBytes(new byte[1]); //some bytes
result.setData(data);
return result;
}
}
public class Result {
private byte[] bytes;
private ResultData data;
public byte[] getBytes() {
return bytes;
}
public void setBytes(byte[] bytes) {
this.bytes = bytes;
}
public ResultData getData() {
return data;
}
public void setData(ResultData data) {
this.data = data;
}
}
public class ResultData {
private byte[] bytes;
public byte[] getBytes() {
return bytes;
}
public void setBytes(byte[] bytes) {
this.bytes = bytes;
}
}
Please Type your service description here
http://www.w3.org/2004/08/wsdl/in-only"; class="org.apache.axis2.rpc.receivers.RPCInOnlyMessageReceiver" />
http://www.w3.org/2004/08/wsdl/in-out"; class="org.apache.axis2.rpc.receivers.RPCMessageReceiver"/>
Service
true
true
true
true
3
false
false
admin
axis2
true
false
http://www.w3.org/2004/08/wsdl/in-only";
class=&q
Re: Axis2 byte[] transfer/serialization bug ?!
Paul Fremantle wrote: > George > > Is there any stack trace? How big is the byte[] before it crashes? Can > you attach any code you've generated? What kind of databinding are you > using? Which version of Axis2? > > Paul > > On 7/24/07, Georgi Yonchev <[EMAIL PROTECTED]> wrote: >> Hi, >> i developing a web service, based on Axis2, >> and the client side on gSOAP >> and i have a serious problem, >> Each call, return a complex type Result, >> how contains a String, int & comples type ResultData (i try with Object >> (anyType) but always get a null, only if i set the object like a String) >> so the ResultData contains again String, int & byte[] >> everything goes well, but when i set something bigger in byte[], the >> serialization crashes. >> i don't want to use MTOM ... >> only works when the return type of a call is byte[], isn't complex type >> >> here is a part of my wsdl: >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> can you give me some help .. >> >> Best Regards >> George >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > Hi Paul, there is no stack trace, no errors, the call i succeed, but on client side ... (heap exception) I'm using Axis2 1.2, how bigger is the byte[] ? works with 4 bytes :) later i try something real and again small (14 kB) but the serialization goes nasty .. i can paste you the payload, which i sniffed with ethereal http://schemas.xmlsoap.org/soap/envelope/";>http:///xsd";>77686912177122814978< etc.. the service is written in POJO - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis2 byte[] transfer/serialization bug ?!
Hi, i developing a web service, based on Axis2, and the client side on gSOAP and i have a serious problem, Each call, return a complex type Result, how contains a String, int & comples type ResultData (i try with Object (anyType) but always get a null, only if i set the object like a String) so the ResultData contains again String, int & byte[] everything goes well, but when i set something bigger in byte[], the serialization crashes. i don't want to use MTOM ... only works when the return type of a call is byte[], isn't complex type here is a part of my wsdl: can you give me some help .. Best Regards George - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
