Hi Dennis, Normally I would just make the changes to the Axis code, submit it back in, and go on with life <grin>. However, my first-blush look at the code tells me that it's pretty complex, and without delving much deeper into the architecture (which I'd love to do but simply don't have the bandwidth right now), I'm concerned that any changes I made would be rather short-sighted (to meet my immediate needs) and is likely to break existing functionality.
I've been continuing to dig into this issue, and I think I may have a workaround. It appears that Axis _is_ reflecting the host part of the request back as the service location in the autogenerated WSDL. I'm not sure about the port since I'm changing the port as the request passes through the NAT firewall, but Axis wants to leave it at 80 (which is the port that Apache httpd is listening on). So it looks like as long as I keep the port numbers consistent across the stack, I can get it to behave mostly the way I want, though I still have to confirm this. The ability to specify a server-specific endpoint is still desirable for many reasons, and I'll still pursue this. Thanks, -Mike -----Original Message----- From: Dennis Sosnoski [mailto:[EMAIL PROTECTED] Sent: Monday, April 12, 2004 7:29 PM To: [EMAIL PROTECTED] Cc: Mike Panzitta Subject: Re: How can I specify the service host/port in autogenerated WSDL? Wouldn't it be simpler to just go into the Axis code and make the change to use the incoming path information, Mike? That way you can submit the change back to the main codebase. It doesn't sound like the change would break existing code, though you could always make it optional to be on the safe side. - Dennis Davanum Srinivas wrote: >If you are going to do it Please try a HTTP Filter instead of a Servlet >(http://www.javaworld.com/javaworld/jw-06-2001/jw-0622-filters.html) that way you have better >control. > >-- dims > >--- Mike Panzitta <[EMAIL PROTECTED]> wrote: > > >>Hi Nelson, >> >>Well, I'm "glad" to know that I'm not the only one suffering this >>problem. The servlet approach looks like the best bet at this point, >>although I'm thinking filter might work, too. I'm considering having it >>grab anything directed at <context>/services/* with the "?wsdl" query, >>then simply replacing the host/port portion of the <wsdlsoap:address >>location="xxx" /> element on the way out. >> >>If I wind up having to do this, I'll happily post the source for all to >>use and abuse. >> >>Thanks, >> >>-Mike >> >> >>
