Is this correct for working with a web service?

Hi, I use SOAPUI and VS2013.
I recently have to work with, calling, a Java SOAP web api, provided by a 3rd party vendor.  It seems that it would generate endpoint url as "https://localhost:8443/xxxx/xxxxservice "  in both SOAPUI and in my web config file in VS2013 and that of course doesn't work.  Their response was "Typically when calling a web service the web service client will override the endpoint URL with a URL that is accessible to it in the network. "

My question is why isn't it possible for the wdsl to be customized for each of their customer so that it will generate the correct endpoint? Also, when I add asp.net service api that I wrote, I didn't have to deal with this wsdl and endpoints needing customzation that I ever have to do.  So can this be done in creating the wsdl that would generate wsdl for each FQDN?  Is that a lot of work to do that in Java web SOAP web service?
Thank you.
lapuccaAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jorge_torizResearch & Development ManagerCommented:
Mmm... I don't agree with "Typically when calling a web service the web service client will override the endpoint URL with a URL that is accessible to it in the network", the endpoint URL is determined by the Web Service address, not by the best wishes and dreams of the client.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
lapuccaAuthor Commented:
Perfect!  That's what I thought!  In the real world, if a vendor is to install their web services on our server, they would need to make sure it generate the correct wsdl!  They did so without any warning and it wasted several days of my time to find out the problem in VS2013 and then SOAPUI.  I just want some expert feedback to make sure I'm not the web services idiot here.  
I like how you word it as drams and best wishes, lol..
jorge_torizResearch & Development ManagerCommented:
Jejejeje... wel, one more thing, I would recommend to deploy the vendor's web service to a URL (IP Address) that is accessible by all the devices that will use the web service, otherwise you will face connection issues.
lapuccaAuthor Commented:
Yes, already had DNS and trust certification issues.  Sloppy work but now it's resolved after I pointed them out, sigh.
Thank you.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
WCF

From novice to tech pro — start learning today.