Paul

I guess I can't monitor a http*s* connection with tcpmon?
I mean I could but I would't see anything readable...
Unfortunately my service is only available over TLS, so I will not be able
to figure out whats going over the line that easy.

Is there no other way of debbuging?

What I've also tried is to access the URL over the browser, after
authentication I get an SOAP error message saying something about incomplete
request -> So the URL must be correct, right?

What I did was trying out XFire, again with no success, but this time it
seemed to be a binding issue with namespaces and JAXB which is the only
option when autogenerating a client with XFire, as I figured out. The error
message said something about an unknown method even though the Class was
there. I didnot understand what the real problem was, because the error
message was not very helpful to me.
 (org.codehaus.xfire.fault.XFireFault: Method 'Payment' not implemented:
method name or namespace not recognized
        at
org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(Soap11FaultSerializer.java:31)
....  )

Anyway, asking questions about xfire doesnot belong here.
What confuses about my axis2 variant, is that it talks about redirecting,
and xfire does not.

One of my intents why i chose to use a soap based communication with an
already working server implementation (there are users successfully using
it, even though maybe not based on Java but C#) was that it should be easy.
Generate a client and use it.

But it seems to me, that the S in SOAP doesnot really mean simple, at least
for me :(

Markus



pzfreo wrote:
> 
> Markus
> 
> I think you need to use tcpmon to trace the HTTP flow. It seems like
> the server doesn't like    the URI that you are sending the request
> to. Its sending back an HTTP 302 Found code which is basically a
> redirect. I guess Axis2 should probably follow that redirect, but at
> the same time the server shouldn't be publishing a URI in the WSDL
> that ends up with a redirect.
> 
> If you trace it you can set the stub to go to the real URI and all
> should be fine.
> 
> Paul
> 
> On 4/25/07, Markus F. <[EMAIL PROTECTED]> wrote:
>>
>> Hello list,
>> this is my first contact with axis2. I've to implemtent a client using a
>> 3rd
>> party service over https and username/passwd authentication.
>> I've been spending many hours on this and couldnot find any similar
>> errors
>> on the list or even on the web
>> I autogenerated the client with following command.
>>
>> wsdl2java.bat -o src\generated -s -p com.someservice.test -uri
>> src\wsdl\some.wsdl -d xmlbeans
>>
>> The wsdl makes use of complex type extension, so I'm using xmlbeans for
>> binding.
>> I get the following error: org.apache.axis2.AxisFault: HTTP Transport
>> error
>> : '302' - 'Found'
>> It must be something basic, what I'm missing here, because I get the same
>> error when not providing the credentials.
>>
>> Any hints?
>> Thanks a lot.
>> Markus
>>
>>
>> Here's the stack trace:
>>
>> 25.04.2007 11:17:54 org.apache.commons.httpclient.HttpMethodDirector
>> isRedirectNeeded
>> INFO: Redirect requested but followRedirects is disabled
>> org.apache.axis2.AxisFault: HTTP Transport error : '302' - 'Found';
>> nested
>> exception is:
>>         org.apache.axis2.AxisFault: HTTP Transport error : '302' -
>> 'Found'; nested
>> exception is:
>>         org.apache.axis2.AxisFault: HTTP Transport error : '302' -
>> 'Found'; nested
>> exception is:
>>         org.apache.axis2.AxisFault: HTTP Transport error : '302' -
>> 'Found'
>>         at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:227)
>>         at org.apache.axis2.engine.AxisEngine.send(AxisEngine.java:674)
>>         at
>> org.apache.axis2.description.OutInAxisOperationClient.send(OutInAxisOperation.java:237)
>>         at
>> org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:202)
>>         ...
>> Caused by: org.apache.axis2.AxisFault: HTTP Transport error : '302' -
>> 'Found'; nested exception is:
>>         org.apache.axis2.AxisFault: HTTP Transport error : '302' -
>> 'Found'
>>         at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:344)
>>         at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.invoke(CommonsHTTPTransportSender.java:204)
>>         ... 5 more
>> Caused by: org.apache.axis2.AxisFault: HTTP Transport error : '302' -
>> 'Found'
>>         at
>> org.apache.axis2.transport.http.SOAPOverHTTPSender.send(SOAPOverHTTPSender.java:144)
>>         at
>> org.apache.axis2.transport.http.CommonsHTTPTransportSender.writeMessageWithCommons(CommonsHTTPTransportSender.java:335)
>>         ... 6 more
>> --
>> View this message in context:
>> http://www.nabble.com/Axis2-xmlbeans-http-transport-error-302-found-tf3644416.html#a10177848
>> Sent from the Axis - User mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
> 
> 
> -- 
> Paul Fremantle
> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair
> 
> http://bloglines.com/blog/paulfremantle
> [EMAIL PROTECTED]
> 
> "Oxygenating the Web Service Platform", www.wso2.com
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Axis2-xmlbeans-http-transport-error-302-found-tf3644416.html#a10199717
Sent from the Axis - User mailing list archive at Nabble.com.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to