Hi 

Thanks.We don't want to expose our internal ip's along with port numbers to our 
external clients.

Sent from my iPhone

On Jul 29, 2013, at 9:21 PM, "Freeman-2 [via CXF]" 
<[email protected]> wrote:

> Hi, 
> 
> IIRC, using domain name or ip address depend on which you used the first time 
> to access the webservice. 
> 
> That said, if you use 
> http://10.234.45.122:7777/yy/services/testServices2.wsdl in the browser to 
> access the wsdl, then the wsdl endpoint address is what you used here. 
> ------------- 
> Freeman(Yue) Fang 
> 
> Red Hat, Inc. 
> FuseSource is now part of Red Hat 
> Web: http://fusesource.com | http://www.redhat.com/
> Twitter: freemanfang 
> Blog: http://freemanfang.blogspot.com
> http://blog.sina.com.cn/u/1473905042
> weibo: @Freeman小屋 
> 
> 
> 
> On 2013-7-30, at 上午4:02, thennetti_sairam wrote: 
> 
> > Hi Team 
> > 
> > We are seeing some observation when we are trying to access the context 
> > root 
> > of the application (developed using Apache CXF web services). We had 
> > deployed the WAR application successfully in the Web sphere 6.1 clustered 
> > environment and have set up the required web server plugins. 
> > 
> > When we are trying to access the context root via the plugin(domain name) 
> > over the internet (ex: https://xx.com/yy/services),the application is 
> > accessible and displays the list of WSDLs that we have exposed in our 
> > application. 
> > 
> > Here is the weird thing that is happening. For majority of the WSDLs the 
> > End 
> > point address are mapped using the web sphere plugin name 
> > https://xx.com/yy/services/testServices1.wsdl?  and for the rest of the 
> > other web services , the end point of the WSDLs are mapped using the IP 
> > address of the application server instead 
> > http://10.234.45.122:7777/yy/services/testServices2.wsdl? 
> > 
> > We need to have the domain name displayed across for all the WSDL end point 
> > address ,i.e We need even the URL 
> > http://10.234.45.122:7777/yy/services/testServices2.wsdl? to be displayed 
> > as 
> > 
> > https://xx.com/yy/services/testServices2.wsdl? 
> > 
> > Any pointers to make to this work (either in Code/Web sphere DNS/plugins 
> > configuration) will be highly appreciated, since we are nearing our System 
> > testing cycle and need to expose our WSDLs to other stakeholders. 
> > 
> > From the application side we haven't hardcoded any of the links or the URL 
> > in the config files. 
> > 
> > 
> > 
> > 
> > -- 
> > View this message in context: 
> > http://cxf.547215.n5.nabble.com/exposed-WSDL-contains-IP-address-instead-of-domain-name-tp5731630.html
> > Sent from the cxf-user mailing list archive at Nabble.com.
> 
> 
> 
> If you reply to this email, your message will be added to the discussion 
> below:
> http://cxf.547215.n5.nabble.com/exposed-WSDL-contains-IP-address-instead-of-domain-name-tp5731630p5731638.html
> To unsubscribe from exposed WSDL contains IP address instead of domain name, 
> click here.
> NAML




--
View this message in context: 
http://cxf.547215.n5.nabble.com/exposed-WSDL-contains-IP-address-instead-of-domain-name-tp5731630p5731640.html
Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to