Re: Service Interface get

[scheu]

I looked at Appendix 20, and I believe that Axis is doing the mapping the correct way.

The java mapping for the xml name "xMLJavaMappingTestService" is "XMLJavaMappingTestService".

So this is another case where the TCK is testing an invalid assumption of the RI.

Rich 'Shirley' Scheuerle
IBM WebSphere & Axis Web Services Development
512-838-5115 (IBM TL 678-5115)
R J Scheuerle Jr/Austin/[EMAIL PROTECTED]

R J Scheuerle Jr/Austin/[EMAIL PROTECTED] 06/24/2002 02:43 PM Please respond to axis-tck

To: [EMAIL PROTECTED] cc: Subject: Service Interface get<name-of-wsdl-port>

Problem:
The xmlnamemappingtest requires the generated XMLNameMappingTestService interface to have a getxMLNameMappingTestService method. Axis currently generates a getXMLNameMappingTestService. (The name of the wsdl prot is xMLNameMappingTestService.)

Though strictly correct (the spec says to generate get<wsdl-port-name>), I question whether tooling should emit get methods that don't conform to the general java conventional syntax for get methods.

NOTE: Note that the xmlnamemappingtest is currently blocked by the "full constructor" issue. The get<wsdl-port-name> is a second issue with the test.

Rich 'Shirley' Scheuerle
IBM WebSphere & Axis Web Services Development
512-838-5115 (IBM TL 678-5115)

<<inline: graycol.gif>>

<<inline: ecblank.gif>>