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 > > -----Original Message----- > From: Nelson Minar [mailto:[EMAIL PROTECTED] > Sent: Monday, April 12, 2004 3:08 PM > To: [EMAIL PROTECTED] > Cc: Parley, Thunder Jon > Subject: RE: How can I specify the service host/port in autogenerated > WSDL? > > > >We need to be able to deploy the identical WAR on our dev, QA, and > >production server stacks > > Me too! > > >We give it the URL of the WSDL file, and it uses that to determine > >the URL of the service. We can serve up different versions of a > >static (not autogenerated) WSDL file, but this is the same issue; we > >would have to maintain different versions of the deployables > >depending upon where it is deployed. > > Having a different static WSDL will work, but as you say it's a > hassle to have different versions. The next step would be to write a > servlet that takes a static WSDL template for most of the data but > modifies the binding to match the deployment environment. > > Some discussion of this approach (but no code) is here: > http://marc.theaimsgroup.com/?l=axis-user&m=107972343110185&w=2 > http://marc.theaimsgroup.com/?t=107903201400006&r=1&w=2 > > There are other WSDL customizations I'd like; see my note about headers > http://marc.theaimsgroup.com/?l=axis-user&m=108173808023833&w=2 > > I think Axis should support a mode where the WSDL type data is written > by hand but the other parts of the service are assembled dynamically > with the ability to override it in various places. If this were > designed well I think a lot of Axis users would benefit. > ===== Davanum Srinivas - http://webservices.apache.org/~dims/
