Re: Axis2 403 forbidden error over SSL in WebSphere

2011-08-31 Thread Bala Rajamani
I've added the transport receivers entries in axis2.xml under /conf folder and seem to be working fine. Thanks for the help.

Re: Axis2 403 forbidden error over SSL in WebSphere

2011-08-31 Thread Bala Rajamani
The web service requests on HTTP are working fine but unable to configure on HTTPS and also not seeing calls pointing to the HTTPS transport but still eencountering the error "https is forbidden" but http is fine. Also I understand axis2.xml entries are working on the Tomcat environment on HTTP an

Re: Axis2 403 forbidden error over SSL in WebSphere

2011-08-30 Thread Andreas Veithen
The code that throws this exception looks as follows in 1.6.0: TransportInDescription transportInDescription = req.isSecure()? this.axisConfiguration.getTransportIn(Constants.TRANSPORT_HTTPS) : this.axisConfiguration.getTransportIn(Constants.TRANSPORT_HTTP); if (transportInDescription

Re: Axis2 403 forbidden error over SSL in WebSphere

2011-08-30 Thread Bala Rajamani
I tried creating "axis2.xml" with the following entries (for both http and https and placed under ../WEB-INF) but no luck. 80 443 Also based on this thread, I tried the same steps on both axis 1.6.0 and 1.5.5 no luck either: http://mail-archives.apache.org/mod_mbox/axis-java-user/20

Re: Axis2 403 forbidden error over SSL in WebSphere

2011-08-30 Thread Andreas Veithen
Please refer to the relevant documentation: http://axis.apache.org/axis2/java/core/docs/servlet-transport.html Andreas On Tue, Aug 30, 2011 at 23:15, Bala Rajamani wrote: > I'm trying to configure Axis2 (1.6.0) Web Services frame work in WebSphere > 6.1 but encountering a 403 forbidden error es

Axis2 403 forbidden error over SSL in WebSphere

2011-08-30 Thread Bala Rajamani
I'm trying to configure Axis2 (1.6.0) Web Services frame work in WebSphere 6.1 but encountering a 403 forbidden error especially when I try configure the Web Service over SSL. I saw there is a known issue in 1.6.0 and has been fixed in 1.5.5 but encountering the error in 1.5.5 as well. Wondering i