[
https://issues.apache.org/jira/browse/CXF-8337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17197317#comment-17197317
]
Andriy Redko commented on CXF-8337:
-----------------------------------
Hi [~xardasos] ,
Could you please share a bit more details why the name of the private field
matter in this case? Yes, I would agree with you that `faultInfo` looks more
logical but it is hidden behind the appropriate getter
({color:#172b4d}getFaultInfo(){color}). Do you access the field directly, and
if yes, why? If not, how the re{color:#172b4d}naming of the field to
`faultInfo` would be helpful (besides convenience since we are talking about
*generated* code)? Thank you.{color}
{color:#172b4d}Best Regards,
{color}{color:#172b4d} Andriy Redko{color}
> wsdl2java generates exceptions which do not follow naming convention
> --------------------------------------------------------------------
>
> Key: CXF-8337
> URL: https://issues.apache.org/jira/browse/CXF-8337
> Project: CXF
> Issue Type: Bug
> Components: JAXB Databinding
> Affects Versions: 3.3.3
> Reporter: Tomasz Zorawik
> Priority: Major
>
> wsdl2java generates wrapper exception class for _fault bean._ The generated
> exception has method getFaultInfo(). This method name is correct according to
> JAX-WS specification. However this method returns _fault bean_ stored in a
> field called _"name of fault bean"._ The name of the field and getter do not
> follow the naming convention. Why this field is not called "faultInfo"?
> I believe a template responsible for generating exceptions is here:
> excxf-tools-wsdlto-frontend-jaxws-3.3.3.jar!\org\apache\cxf\tools\wsdlto\frontend\jaxws\template\fault.vm
> {color:#172b4d}public $field.ClassName getFaultInfo() {{color}
> {color:#172b4d} return this.$paraName;{color}
> }
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
