We're using Axis as a JAX-WS implementation (under WebSphere 6.1, if
that matters), so we're not writing any Axis-specific code ourselves.
On Axis2 1.4, we observed many sockets being opened and staying open
long after use and we had some kind of problem that led us to this
ticket https://issues.a
There are known issues with generating endpoint references for HTTPS
in Axis2. This has been fixed by AXIS2-4465.
Andreas
On Thu, May 27, 2010 at 16:58, Alexander Rosemann
wrote:
> Hi,
>
> I configured a service to use a hand written WSDL contract. Axis shows the
> contract as expected but displ
Hi,
I configured a service to use a hand written WSDL contract. Axis shows
the contract as expected but displays the wrong port for the address
location. I'm running Axis2 1.4.1 included in a web-app in Tomcat 6.0.20
using HTTPS, port 8443.
That's what I get:
location="http://192.168.1.102:8
Thank you.
http:// was there...
Spent many days on it... but at the end when I narrowed it down then I found
that there was A space before the http://
:(
thx
AL
From: Andy Dysart
To: "[email protected]"
Sent: Wed, 26 May, 2010 18:19:11
Subje
Hi Steven,
Are you sure that RPC/literal binding is correct for your service?
I think the document/literal wrapped binding is the most WS-I compliant
variant. Seems you received the wsdl from someone else? Maybe ask if the
specified binding is correct? For a document style binding you can keep
Hi,
interesting that you mention this.
In fact the original WSDL provided to me had this:
However this resulted in the following error:
org.apache.axis2.AxisFault: The binding operation LeaseBaseClientOp is
RPC/literal. The message parts for this operation m
