Using oc4j to generate interfaces from wsdl produced improper method names

Question

The method names that were produced from the opperations in my WSDL, generated an interface file with incorrect method names. The name went from "DoTest" in the wsdl to "doTest" in the Interface file.
I double checked and all the cases are correct in the wsdl.
<?xml version="1.0" encoding="UTF-8"?>
<!-- edited with XMLSpy v2005 rel. 3 U (http://www.altova.com) by John Reynolds (MedPlus) -->
<definitions xmlns="http://schemas.xmlsoap.org/wsdl/" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:http="http://schemas.xmlsoap.org/wsdl/http/" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/" xmlns:y="http://localhost/TestService" targetNamespace="http://localhost/TestService">
     <types>
          <xs:schema targetNamespace="http://localhost/TestService" xmlns="http://www.w3.org/2001/XMLSchema">
               <xs:element name="Tresult" type="xs:string"/>
               <xs:element name="Tname" type="xs:string"/>
               <xs:element name="Tfault" type="xs:string"/>
          </xs:schema>
     </types>
     <message name="DoTestResponse">
          <part name="Result" element="y:Tresult"/>
     </message>
     <message name="DoTestRequest">
          <part name="Name" element="y:Tname"/>
     </message>
     <message name="DoTestFault">
          <part name="ExceptionDetail" element="y:Tfault"/>
     </message>
     <portType name="TestService">
          <operation name="DoTest">
               <input message="y:DoTestRequest"/>
               <output message="y:DoTestResponse"/>
               <fault name="DoTestException" message="y:DoTestFault"/>
          </operation>
     </portType>
     <binding name="TestService" type="y:TestService">
          <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
          <operation name="DoTest">
               <soap:operation soapAction="urn:#DoTest" style="document"/>
               <input>
                    <soap:body use="literal"/>
               </input>
               <output>
                    <soap:body use="literal"/>
               </output>
               <fault name="DoTestException">
                    <soap:fault name="DoTestException" use="literal"/>
               </fault>
          </operation>
     </binding>
     <service name="TestServiceSoap">
          <port name="TestService" binding="y:TestService">
               <soap:address location="http://localhost/TestService"/>
          </port>
     </service>
</definitions>

Answer 1

Obviously one could rename the operation to that standard, but that doesn't exactly strike me as being anything other that a work around for a bug.
WSDL provides a contract in which multiple languages have to conform to a set of interfaces, and it's not exactly good to have a tool, just a assume the contract for an interface is wrong.
I could argue that I'm only doing Java on the front end and .Net on the client side and that they don't neccessarily follow the Java convention, nor should be constrained by it.
I do agree with you that they probably just followed the convention when writing to code generator and just happened to pick up the convention. They just need to fix it now.