Thanks for all your time.
We've took a closer look to it, and it seems to be not a problem of
Axis2. Because from different client pc's, it does work.
So we are examining that first now.
Thanks
2008/7/9 Paul Fremantle <[EMAIL PROTECTED]>:
> PS WSAS should run on WebLogic too.
>
> On Wed, Jul 9
PS WSAS should run on WebLogic too.
On Wed, Jul 9, 2008 at 10:18 AM, Deepal jayasinghe <[EMAIL PROTECTED]> wrote:
> I am sorry I did not have time to test on weblogic , but in tomcat this does
> not happen. It gives me the correct WSDL. If you do not bind with Weblogic ,
> have a look at WSO2 WSAS
Yes , once the servlet receives the message it does not whether the
message came on http or https.
-Deepal
Paul Fremantle wrote:
Surely if there is a front-end server handling HTTPS then the messages
coming into Axis2 should be in HTTP?
Paul
On Wed, Jul 9, 2008 at 9:57 AM, Jan Verstuyft
<[EM
I am sorry I did not have time to test on weblogic , but in tomcat this
does not happen. It gives me the correct WSDL. If you do not bind with
Weblogic , have a look at WSO2 WSAS , which is an open source Web
service server built on Axis2. And provide better support for transport
management.
I
Surely if there is a front-end server handling HTTPS then the messages
coming into Axis2 should be in HTTP?
Paul
On Wed, Jul 9, 2008 at 9:57 AM, Jan Verstuyft
<[EMAIL PROTECTED]> wrote:
> It is indeed on a WebLogic server.
>
> But if I do remember, it is the following infrastructure:
>
> 2 weblog
It is indeed on a WebLogic server.
But if I do remember, it is the following infrastructure:
2 weblogic servers with this WEB APP on it.
In front of it an Apache Webserver for loadbalancing
in front of it a BlueCoat that handles the HTTPS.
The actual problem is that (if the HTTP is disabled and
Are you using just standalone version of Axis2 or Axis2 on tomcat or
somewhere ?
if it is on Tomcat then you do not need to add this https in axis2.xml
Ok, i've found the problem for the class path. I'm running on JDK
1.4 and the nio packages use the javax.net.ssl.SSLEngine that is
introduced
Ok, i've found the problem for the class path. I'm running on JDK
1.4 and the nio packages use the javax.net.ssl.SSLEngine that is
introduced in JDK 1.5
is there a workaround for this? Or do we need to migrate to JDK 1.5?
2008/7/9 Jan Verstuyft <[EMAIL PROTECTED]>:
> Hi Deepal,
>
> thanks for
Hi Deepal,
thanks for the response. I've tried this, but he still is complaining
about the nio files.
Like I told, i've uncommented the section of transport receiver for
https (at the first moment, I don't mind the settings, first I want to
get this working :) ).,
I've put the following servic
Hmmm,
I guess I'm already one step closer :).
Do I also need to define the transportreceiver for HTTPS?
Yes , you need to do that.
I've read
something about configure the services.xml with the following stuff:
https
yes you also need to add the expose transports in services.xml
ht
Hmmm,
I guess I'm already one step closer :).
Do I also need to define the transportreceiver for HTTPS? I've read
something about configure the services.xml with the following stuff:
https
So that you only have the https transport. But if I do this, he
complains that HTTPS is not defined
Hi,
we had a default configuration for our axis2 webservices and now we
want to put this on a HTTPS configuration. The intention is also to
block the http request.
Because we've found some settings in the axis2.xml:
HTTP/1.1
HTTP/1.1
We've thought that we do
12 matches
Mail list logo
