Vivek Pandey wrote:
>
> 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.
I can see it here ...
https://jax-ws-sources.dev.java.net/source/browse/jax-ws-sources/jaxws-ri/rt/src/com/sun/xml/ws/api/wsdl/parser/Attic/WSDLParserExtension.java?rev=1.1.2.4&only_with_tag=rearch-2005&view=markup
>
>> 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.
Since there is a JavaExtensionHandler in the codebase as well, I dont
want people to confuse that TExtensionHandler might be in someway
related to that class. I feel we should follow a consistent naming
scheme for all the extension handlers. Either they should be
TWSDLParserExtensionHandler and TJavaExtensionHandler or
WSDLParserExtensionHandler and JavaExtensionHandler.
>
>> 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.
same as above.
-Arun
>
> -vivek.
>
>> -Arun
>
>
--
got Web Services ?
Download Java Web Services Developer Pack from
http://java.sun.com/webservices