-
Bug
-
Resolution: Done
-
Major
-
jbossws-native-2.0.3
-
None
When a WSDL is processed with the following definitions: -
<portType name='phoneBookPort'>
<operation name='lookup'>
<input message='tns:PhoneBook_lookup'/>
<output message='tns:PhoneBook_lookupResponse'/>
</operation>
</portType>
<binding name='phoneBookBinding' type='tns:phoneBookPort'>
<soap:binding style='document' transport='http://schemas.xmlsoap.org/soap/http'/>
<operation name='lookup'>
<soap:operation soapAction=''/>
<input>
<soap:body use='literal' parts='parameters'/>
</input>
<output>
<soap:body use='literal'/>
</output>
</operation>
</binding>
<service name='phoneBookService'>
<port binding='tns:phoneBookBinding' name='PhoneBook'>
<soap:address location='REPLACE_WITH_ACTUAL_URL'/>
</port>
</service>
The generated service-interface and generated service-endpoint-interface are correctly generated with the first letter upper, however the generated JAX-RPC mapping references the types with the first letter lower case.
- is incorporated by
-
JBPAPP-874 JBossWS - WSDL To Java - Case of service-interface and service-endpoint-interface in JAX-RPC mapping does not match generated interface when WSDL type begins with lower case.
- Resolved