Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • Home
  • SEARCH
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 6604469
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 25, 20262026-05-25T19:09:37+00:00 2026-05-25T19:09:37+00:00

I really need your help. I read that the wsdl for a jax-ws webservice

  • 0

I really need your help. I read that the wsdl for a jax-ws webservice will be generated on the fly for every request. By this, the addresses like the soap endpoint will be adjusted to the request url.

In my case it, no matter wheather internal or external request, the addresses are always refered to localhost:8080.

Does sb have a clue how can I handle this issue?

Thanks in advance


Maybe I haven’t described my problem very well.

  1. I have a ws created with jax-ws
  2. Its deployed on a tomcat server 5.5.17
  3. Access with local ip works fine http://192.168.1.20:8070/mywebservice?wsdl
  4. Access with external ip doesn’t work resp. the ws “engine” rewrites the url by using the local ip and not the external one
    external.domain.de:8070/mywebservice?wsdl

For external.domain all urls in the wsdl are rewritten to the local ip
To the xsdschemaLocation and the soap:address location

Could the proxy server the problem? Request through the proxy makes the webservice think that it is an local access and not a external.

How can I prevent this behaviour on server side?Changes in web.xml or sun.jax (Changes on client side are regrettably not possible)

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-25T19:09:38+00:00Added an answer on May 25, 2026 at 7:09 pm

    This is a classic problem when accessing web-services thru external proxies.

    For this to work properly, you have to do the following

    1) Add another HTTP connector in your Tomcat’s server.xml. Say on port 8071, just copy the 8080 Connector Dfn. and set the port to 8071.

    2) And in that Connector’s defn. you have to add the external IP and Port as proxyHost and proxyPort.

    i.e. your server.xml should contain one more Connector entry some thing like this

    <Connector port="8071" protocol="HTTP/1.1"
       connectionTimeout="20000"
       redirectPort="8443"
       proxyHost="external.domain.de" proxyPort="8070" />
    

    And make sure that Connections to external.domain.de on port 8070, get forwarded to 192.168.1.20 and port 8071, instead of 8070.

    I told you to setup a new connector, assuming you would want to access the WS internally as well as externally. That way the internal port connector on 8070, does not use proxyhost and change the hostname for internal requests, but any requests coming from external sources via external.domain.de on port 8071 , will get the external.domain.de as hostname and 8070 as port.

    If your WS is going to be accessed only from external clients, then you don’t really need 2 connectors, just add the proxyHost and proxyPort directives to the 8070 connector and you’re done.
    But be warned, that even internal requests, will now see the hostname as external.domain.de.

    More info @ https://tomcat.apache.org/tomcat-5.5-doc/config/http.html#Proxy_Support

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I really need your help for this. I am relatively new to programming and
Sorry if this is already posted, but I really need your help. What I
Afternoon all, I really need your help as this is a Nightmare! I was
i really need your help. I'm trying to get request token from twitter with
I really need your help in my issue very quickly and it's too close
I've some questions .. and I really need your help. I have an application.
I really need help with interfaces in general... Any resources that you guys would
I really need help on this one. I am having a simple login form
I realy need your help as this is driving me nuts. On my website
i really need your help with a CSS-Layout. I tried a few time, however

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.