+1
-- Tom Jordahl Macromedia -----Original Message----- From: Glen Daniels [mailto:[EMAIL PROTECTED]] Sent: Friday, February 08, 2002 12:43 AM To: '[EMAIL PROTECTED]' Subject: Caching generated WSDL Let's say we wanted to cache the WSDL generated by the ?WSDL URLs, and also perhaps provide a way for a service to specify its own WSDL. The simple way to do this might be to specify a WSDL output directory property. Then each time a given service's WSDL is requested, we first check for a ServiceName.wsdl file in that directory and simply send that if it exists instead of running the emitter. We don't want the cached WSDL to get out of sync with the class definitions, so we need a way to say "if the file is older than the last class reload, regen it". For non-JWS files, it's probably good enough to mark when the AxisServer starts up, and then generate each service once after that. For JWS classes, we have the time available and so can be a bit more dynamic. If you want to specify a static file which should always be used rather than autogen, perhaps we could simply put that as a parameter of the <service> deployment: <parameter name="wsdlFile" value="/path/to/service.wsdl"/> What do folks think about this direction? Should we add it to the to-do list? --G
