I just committed a change to filter the ".jws" out of the service name we derive from the URL is the service name isn't set.
FYI Greg - a change I made yesterday to the EJBProvider class now correctly uses the right interface to generate WSDL for EJBs. -- Tom Jordahl Macromedia -----Original Message----- From: Greg Truty [mailto:[EMAIL PROTECTED]] Sent: Thursday, January 10, 2002 6:03 PM To: [EMAIL PROTECTED] Subject: Re: .jws files and generated WSDL Yes, I think it would be good. We have already seen cases in the EJB case where it's useful to filter out some things in the javaToWsdl emitter. Regards...Greg Tom Jordahl <tomj@macromedia. To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]> com> cc: Subject: .jws files and generated WSDL 01/10/2002 04:34 PM Please respond to axis-dev If you look at the WSDL generated by a .jws file, the names of the binding and service have .jws in them. This gets handled OK by WSDL2Java, but it looks a little funny: + <wsdl:portType name="Calculator"> + <wsdl:binding name="Calculator.jwsSoapBinding" type="intf:Calculator"> + <wsdl:service name="Calculator.jwsService"> These get translated to the class names 'CalculatorJwsSoapBinding' and 'CalculatorJwsService'. Does anyone think its a good idea to filter out the ".jws" in the WSDL emitter? -- Tom Jordahl Macromedia Server Development
