No, certainly the "?wsdl" suffix should not be part of the SOAP address,
you just use it when viewing from the browser.
CXF 2.2.x is unsupported, I'm not sure how to configure it or how you
can base security on top of it anyway (security on an obsolete version
of software is a bit of a contradiction). The configuration
instructions that you see in the online docs may very well not be
applicable for a version that old.
I can't think of an immediate solution, more detective work may be
needed. Possible ideas/options:
1.) I would check the WAS logs for any error messages pointing to the
problem, although from what I'm seeing below I don't think the app
server is even getting any message.
2.) As in my SSL tutorial I referenced earlier, does the truststore of
the JRE that the client is using (or the truststore that you've
specifically configured for you client) contain the public cert of the
WAS server? (That will be needed for SSL connections, but I think you
would have gotten another error message if that was the problem.)
3.) If you can do so without risking the transmission of sensitive data,
downgrade your web service provider temporarily to just HTTP and see if
you can get that working at least before moving to HTTPS. (will help
isolate whether the problem is HTTPS-related.)
4.) Create a Metro client using my SOAP client tutorial and see if it
works or doesn't (it will help show whether the problem is with CXF
client, your network, or WAS, or possibly give different errors better
pointing to the problem.)
5.) See if you can deploy your web service on Tomcat instead and see if
it works (can help show whether the problem is with the CXF web service
provider or WAS's internal configuration.)
6.) Deploy a Metro web service provider on WAS
(http://www.jroller.com/gmazza/entry/web_service_tutorial) and see if
that fixes the problem (another way of pinpointing whether the problem
is with CXF or WAS, and if you're not allowed to deploy anything more
recent than CXF 2.2.3, it may be a good time to use a different web
service stack instead.)
HTH,
Glen
On 07/20/2012 08:07 AM, nhrraj wrote:
Yes, the wsdl is accessible.
If I use, the url+"?wsdl" for creating the port, then I am getting the below
error.
javax.xml.ws.soap.SOAPFaultException: java.net.ConnectException: HTTP ( 404
) Not Found address : https://xx.yy.com/service/myservice?wsdl
If I use only the url (without ?wsdl) for creating the port, then I am
receiving the below error.
java.net.ConnectException: HTTP ( 404 ) Not Found address :
https://xx.yy.com/service/myservice
Also, please note the client for this service runs in was 8.0 and uses cxf
2.3.11
The server(that hosts myservice) runs on was 8.0 and uses cxf 2.2.3.
Can this cause the problem?
Please note that the service is up and wsdl is accessible. I am able to hit
the service from .net client and soapui as well without any issues.
thanks.
--
View this message in context:
http://cxf.547215.n5.nabble.com/getport-returning-http-url-instead-of-https-tp5711336p5711355.html
Sent from the cxf-user mailing list archive at Nabble.com.
--
Glen Mazza
Talend Community Coders
coders.talend.com
blog: www.jroller.com/gmazza
