The last released version of Axis for Java is 1.4. Note that there is also Axis2 1.4.1.
Andreas On Tue, Mar 31, 2009 at 15:08, Ghazzaoui, Ramez (NIH/NLM/LHC) [C] <ghazzao...@mail.nih.gov> wrote: > I am using Axis 1.6 for Java, with Tomcat, on Linux. But it's definitely for > Java. All of our web services are written in Java. > -Ramez > > ________________________________________ > From: Andreas Veithen [andreas.veit...@gmail.com] > Sent: Tuesday, March 31, 2009 6:52 AM > To: axis-user@ws.apache.org > Subject: Re: How do we configure Axis to write the proper host name in the > WSDL that it generates? > > Ramez, > > I guess you are talking about Axis/C. If this is the case, you posted > your message on the wrong mailing list, as this is the list for Axis > for Java. > > Andreas > > On Mon, Mar 30, 2009 at 17:48, Ghazzaoui, Ramez (NIH/NLM/LHC) [C] > <ghazzao...@mail.nih.gov> wrote: >> Hi all, >> >> >> >> If anyone knows for sure that this cannot be done in Axis 1.6 please let me >> know so that I stop hoping/waiting for a solution. >> >> >> >> Cheers, >> >> -Ramez >> >> >> >> ________________________________ >> >> From: Ghazzaoui, Ramez (NIH/NLM/LHC) [C] >> Sent: Friday, March 27, 2009 5:13 PM >> To: axis-user@ws.apache.org >> Subject: How do we configure Axis to write the proper host name in the WSDL >> that it generates? >> >> >> >> Hi, >> >> >> >> Can anyone please tell me what to change in my existing installation of Axis >> 1.6 in order for it to write the proper host name instead of the generic >> localhost:8080 in the WSDL that it generates? >> >> >> >> I am developing a public web service, and I want people to be able to get >> the latest WSDL dynamically by accessing the URL of my service’s WSDL as >> http://host_name/path/service_name?wsdl where host_name is the real server >> name (and port) of my server rather than localhost:8080 >> >> >> >> Currently the solution that I am using is to get the WSDL, edit it to >> replace “localhost:8080” with my host name, save it in a public folder, and >> advertise that file as being the location for my web app’s WSDL. The >> downside of this solution is that the advertised WSDL can often fall out of >> sync with the latest edition of the web app deployed. >> >> >> >> I was unable to find an answer to this question anywhere on the Internet. >> >> >> >> Note that I am using Axis 1.6 >> >> >> >> Thanks. >> >> >> >>
