Arun Gupta wrote:
> With TExtensionHandler checked into workspace, WSDLParserExtension is
> moot. Is that correct ?
>
I dont see any WSDLParserExtension in the api package. For the rest of
stuff - yes there some cleanup left. I will do that.
> Also, can we rename TExtensionHandler to TWSDLParserExtensionHandler
> to be more meaningful ?
>
Well, the wsdl package is there for a reason - wsdl.TExtensible. I
thought we agreed upon to prefix with the tools api with 'T' because
There are lots of wsdl related classes/interfaces in our codebase and to
differentiate it from the runtime ones. If you feel strongly about it we
can have TWSDL.
> Can we also rename JavaExtensionHandler to TJavaExtensionHandler to be
> consistent ?
>
Again T was appended to the wsdl extension classes to differentiate them
from other model classes. This stands alone and I dont see any other
class having similar name. What do others think, I am fine either way.
-vivek.
> -Arun
--
Vivek Pandey
Web Services Standards and Technologies
Sun Microsystems Inc.