On Wed, Mar 31, 2010 at 1:33 AM, MDee wrote:
>
> Could this be the solution? I added this line after creating the stub.
>
> ws._getServiceClient().getOptions().setProperty( HTTPConstants.CHUNKED,
> "false" );
>
> It seems to work! Don't know why though.
>
May be a problem with IIS handling chu
Hello all,
I have created a simple HelloWorld axis2 webservice and it works perfectly
when rampart is not engaged. I made the web service a secure one implementing
transport level security as indicated by Nandana in the following tutorial:
http://wso2.org/library/3190
When I invoke the se
Could this be the solution? I added this line after creating the stub.
ws._getServiceClient().getOptions().setProperty( HTTPConstants.CHUNKED,
"false" );
It seems to work! Don't know why though.
http://blog.roweware.com/2007/09/18/axis2-iis-woes/
So far it seems to work.
Mike
--
View this
Hi all:
I am invoking the simple webservice that Nandana created
at http://wso2.org/library/3190 from the client code and I get Exception in
thread "main" org.apache.axis2.AxisFault: Read timed out error. The client
code is as below:
public class HelloWorldClient {
public static vo
I figured this never mind. Thanks. I used https protocol when I disabled
security on the webservice.
--- On Tue, 3/30/10, SM wrote:
From: SM
Subject: Invoking a webservie call from the client gives --> "main"
org.apache.axis2.AxisFault: Remote host closed connection during handshake
To: jav
Hi all:
I am invoking a simple webservice call from a client and I get the following
error. Any tips for resolving this will be much appreciated. My client code
is also pasted below:
public class HelloWorldClient {
public static void main(String[] args) throws Exception {
HelloWor
Hi All,
I had webservice and am able to generate proper response based on client
request but when they are making invalid request i.e. removing some tag or
making syntax related mistake, in response i'm getting exception related to
soap:Client.
I check my logs and it seems that the request is
Hello Axis Users,
I am currently implementing a client for a Siebel CRM web service with
Axis 1.4. When there is no error everything is fine, but in case of an
error Siebel might return a HTTP 500 error code where the detailed reason
is in a HTTP Header. To react differently on the error reason
Need to get Axis2 based web service up and running. Having problem and can
pay for help. Issue involves IIS + isapi_redirector + tomcat and Axis2.
Can read about full problem at:
http://old.nabble.com/Axis2-with-SSL-gives-AxisFault-td28053938.html
Feel free to contact me directly.
Mike
--
V
>is this working when directly invoke the tomcat 8443 port with https?
>
>Since this request hit the AxisServlet within the tomcat server you can
>debug it. For this you can
>download the source code and start debuging AxisServlet class post method.
IIS handles all HTTP/HTTPS operations via the I
10 matches
Mail list logo