Thanks! I will try these. BTW, I got Axis to use .asmx instead of .jws by modifying JWSHandler.java and changing DEFAULT_JWS_FILE_EXTENSION from '.jws' to '.asmx'. There was a small gotcha that some of the substring code assumes a 3 character file extension. There are two places where you need to change '-3' to '-4' and one place where you need to change '-4' to '-5'. Everything seemed to work fine, although I didn't do much testing.
> -----Original Message----- > From: Steve Loughran [mailto:[EMAIL PROTECTED]] > Sent: Monday, January 27, 2003 12:03 PM > To: [EMAIL PROTECTED] > Subject: Re: Simple mapping .asmx to .jws? > > > > ----- Original Message ----- > From: "Randy Belknap" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Saturday, January 25, 2003 11:19 > Subject: RE: Simple mapping .asmx to .jws? > > > > Does anyone know whether OPTION_JWS_FILE_EXTENSION is > implemented? The > > org.apache.axis.handlers.JWSHandler has this: > > > > String extension = > (String)getOption(OPTION_JWS_FILE_EXTENSION); > > if (extension == null) extension = > DEFAULT_JWS_FILE_EXTENSION; > > > > Where the default extension is '.jws', but the option extension is a > > parameter that is looked up. I haven't been able to trace > back to where > how > > that parameter can get set. > > > > If you have any ideas, that would be cool. > > This would be an interesting experiment. At the very least, > you need to edit > web.xml to bind .asmx to the axis servlet; you can try setting the > OPTION_EXTENSION the way you set any other parameter: as a > global option in > server-config.wsdd. But you'd be exploring new areas of Axis. > The other > trick would be servlet2.3 filter to forward .asmx to .jws urls >
