[
https://issues.apache.org/jira/browse/TUSCANY-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Raymond Feng resolved TUSCANY-1899.
-----------------------------------
Resolution: Fixed
Fixed by keeping the name as-is.
> Java2WSDL (trivial) - do we have to assume method names start w/ a lowercase
> char?
> ----------------------------------------------------------------------------------
>
> Key: TUSCANY-1899
> URL: https://issues.apache.org/jira/browse/TUSCANY-1899
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA Tools
> Affects Versions: Java-SCA-1.0, Java-SCA-1.0.1
> Reporter: Scott Kurz
> Assignee: Raymond Feng
> Priority: Trivial
> Fix For: Java-SCA-Next
>
>
> The fact that: TuscanyWSDLTypesGenerator .createSchemaTypeForMethodPart
> on line 267 calls:
> globalElement.setName(formGlobalElementName(localPartName));
> which lowercases the first char in the parm passed to formGlobalElementName
> ends up implying that method names must start in a lowercase char.
> Because otherwise..the elem name
> so constructed won't match the operation name... which will cause us to not
> end up with doc-lit-wrapped WSDL.
> Since everyone uses lowercase method names this in Java, I ranked this as
> 'trivial'.
> Still, I opened this anyway because I didn't see why we bother to lowercase
> this string at all, and thought that if someone cancelled this JIRA, at least
> I'd learn
> there was a good reason for doing so.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
