You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Borja Urquizu <bu...@pandasoftware.es> on 2007/05/22 19:41:19 UTC
axis2c and python client
Hi all,
I'm using the axis2c 1.0.0 binary distribution. I follow the deploy
instructions and start the axis server comes with the binary
distribution.
I test it openning a web browser to http://localhost:9090/axis2/ and it
shows the services. all ok.
I execute the example echo and everything ok, the echo returns.
Well, i'm trying to implement a client in python using soappy, this is
the code of the client, very simple :
import SOAPpy
from SOAPpy import anyType
from SOAPpy import StringType
from SOAPpy import UnicodeType
from SOAPpy import voidType
NS = "http://ws.apache.org/axis2/c/samples"
AXIS2_URL= "http://127.0.0.1:9090/axis2/services"
print SOAPpy.SOAPProxy("%s/echo" % AXIS2_URL,
NS).echoString("Increible")
The axis server :
Echo client ERROR: invalid XML in request
The problem is solved if i quit from soappy python library the '/n' when
creating the xml.
Why the xml in axis2c server 1.0.0 must haven't '/n'. Maybe something in
axiom library of axis2c?
I test it with the axis2c-bin-0.96 distribution and the python client
works fine.
The axis2.log :
[Tue May 22 21:06:03 2007] [debug] phase.c(195) Invoke the handler
soap_message_body_based_dispatcher within the phase Dispatch
[Tue May 22 21:06:03 2007] [debug] soap_body_disp.c(217) Checking for
operation using SOAP message body's first child's local name :
echoString
[Tue May 22 21:06:03 2007] [debug] soap_body_disp.c(226) Operation found
using SOAP message body's first child's local name
[Tue May 22 21:06:03 2007] [debug] phase.c(195) Invoke the handler
addressing_based_dispatcher within the phase Dispatch
[Tue May 22 21:06:03 2007] [debug] phase.c(195) Invoke the handler
soap_action_based_dispatcher within the phase Dispatch
[Tue May 22 21:06:03 2007] [debug] engine.c(571) Invoking phase
PostDispatch
[Tue May 22 21:06:03 2007] [debug] phase.c(195) Invoke the handler
dispatch_post_conditions_evaluator within the phase PostDispatch
[Tue May 22 21:06:03 2007] [debug] phase.c(195) Invoke the handler
context_handler within the phase PostDispatch
[Tue May 22 21:06:03 2007] [debug] class_loader.c(135) Object loaded
successfully
[Tue May 22 21:06:03 2007] [debug] engine.c(292) Axis2 engine receive
completed!
[Tue May 22 21:06:03 2007] [debug] engine.c(571) Invoking phase
MessageOut
[Tue May 22 21:06:03 2007] [debug] phase.c(195) Invoke the handler
AddressingOutHandler within the phase MessageOut
[Tue May 22 21:06:03 2007] [info] Request served in 0.125 seconds
[Tue May 22 21:06:04 2007] [info] Received signal SIGINT. Server
shutting down
[Tue May 22 21:06:04 2007] [info] Terminating HTTP server thread
The python client error :
<Fault env:Sender: NULL paramater was passed when a non NULL parameter
was expected: <SOAPpy.Types.structType detail at -1215306228>:
{'EchoServiceError': ''}>
Traceback (most recent call last):
File "/root/tests/echo.py", line 29, in ?
print SOAPpy.SOAPProxy("%s/echo" % AXIS2_URL,
NS).echoString("Increible")
File "/var/lib/python-support/python2.4/SOAPpy/Client.py", line 421,
in __call__
return self.__r_call(*args, **kw)
File "/var/lib/python-support/python2.4/SOAPpy/Client.py", line 443,
in __r_call
self.__hd, self.__ma)
File "/var/lib/python-support/python2.4/SOAPpy/Client.py", line 357,
in __call
raise p
SOAPpy.Types.faultType: <Fault env:Sender: NULL paramater was passed
when a non NULL parameter was expected: <SOAPpy.Types.structType detail
at -1215306228>: {'EchoServiceError': ''}>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: axis2c and python client
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Dinesh Premalal wrote:
> Borja Urquizu <bu...@pandasoftware.es> writes:
>
>
>> The problem is solved if i quit from soappy python library the '/n' when
>> creating the xml.
>> Why the xml in axis2c server 1.0.0 must haven't '/n'. Maybe something in
>> axiom library of axis2c?
>>
>> I test it with the axis2c-bin-0.96 distribution and the python client
>> works fine.
>>
> I think this is a bug in echo service implementation. Please raise a
> jira issue.
>
Yes it is a bug, introduced due to space handling.
I fixed this after the 1.0 release in the svn head.
Samisa...
> thanks,
> Dinesh
>
>
--
Samisa Abeysinghe : http://www.wso2.org/ (WSO2 Oxygen Tank - Web Services Developers' Portal)
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org
Re: axis2c and python client
Posted by Dinesh Premalal <xy...@gmail.com>.
Borja Urquizu <bu...@pandasoftware.es> writes:
>
>
> The problem is solved if i quit from soappy python library the '/n' when
> creating the xml.
> Why the xml in axis2c server 1.0.0 must haven't '/n'. Maybe something in
> axiom library of axis2c?
>
> I test it with the axis2c-bin-0.96 distribution and the python client
> works fine.
I think this is a bug in echo service implementation. Please raise a
jira issue.
thanks,
Dinesh
--
Dinesh Premalal
http://xydinesh.wordpress.com
GPG ID : A255955C
GPG Key Finger Print : C481 E5D4 C27E DC34 9257 0229 4F44 266E A255 955C
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org