[CXF-1414] cxf-codegen-plugin generates incomplete method signatures for operations with multiple faults defined

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Invalid
• Affects Version/s: 2.0.4
• Fix Version/s: Invalid
• Component/s: Tooling

Environment

MacOS 10.5, Eclipse, Maven 2.0.8

• Assignee: Unassigned
• Reporter: Ryan Norris
• Created: 04/Feb/08 04:35
• Updated: 06/Feb/08 18:10
• Resolved: 06/Feb/08 18:10

Description

When a WSDL defines multiple faults for a given operation, tooling fails to generate a method signature with all defined faults as exceptions. Only the last defined exception is defined as part of the method signature for the operation. Example:

<wsdl:operation name="addPlayerToTeam">
<wsdl:input message="baseball:addPlayerToTeamRequest"></wsdl:input>
<wsdl:fault name="fault"
message="baseball:teamNotFoundException">
</wsdl:fault>
<wsdl:output message="baseball:addPlayerToTeamResponse"></wsdl:output>
<wsdl:fault name="fault"
message="baseball:playerNotFoundException">
</wsdl:fault>
</wsdl:operation>

Generates an incorrect method signature of:

@ResponseWrapper(localName = "addPlayerToTeamResponse", targetNamespace = "http://baseball/", className = "baseball.AddPlayerToTeamResponse")
@RequestWrapper(localName = "addPlayerToTeam", targetNamespace = "http://baseball/", className = "baseball.AddPlayerToTeam")
@WebResult(name = "contractId", targetNamespace = "")
@WebMethod
public int addPlayerToTeam(
@WebParam(name = "playerId", targetNamespace = "")
int playerId,
@WebParam(name = "teamId", targetNamespace = "")
int teamId
) throws PlayerNotFoundException;