• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

AXIS and Apache : Domain Names

 
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a webservice that I've developed in java with AXIS. Everything works fine when I use tomcat as the webserver (port 8080). However, I'm trying to migrate it to the development server which uses Apache and proxy passes requests to tomcat. When I generate the wsdl (using the ant tasks) the service location looks like this:

<wsdlsoap:address location="https://mydevserver/axis/services/mySvc"/>

I then use this wsdl to generate the necessary classes and wsdd files (using the ant tasks). The address in the servicelocator says:
"https://myServer/axis/services/mySvc"

Which is correct.

When I register the webservice the wsdl that appears in the Admin page ("View the list of deployed Web services") has a service location that looks like this:

<wsdlsoap:address location="http://myserver:8080/axis/services/mySvc"/>

There is no "https" and it added the :8080. Why is it doing this? I am running the AdminClient registration tool via localhost:8080, is that the problem?
 
Ranch Hand
Posts: 548
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
yes, when you deploy your web service using Axis's AdminClient tool you have to specify admin service url using -l option
 
B Rook
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
But you can run the adminclient program from the command line without specifying a url. That url is only needed to tell the adminclient program where the adminclient service lives. It doesn't tell the wsdl what to put in the service location attribute. I'm trying to find out why my service location attribute (in the wsdl) is saying something different that what is in my servicelocation class.

brian
reply
    Bookmark Topic Watch Topic
  • New Topic