SourceForge : artf2686: (1800) Axis WSDL2Java error when generating fault types

Project: DAIS-WG Trackers > WS-DAI Issues > View Artifact

Artifact artf2686 : (1800) Axis WSDL2Java error when generating fault types

Tracker:	WS-DAI Issues
Title:	(1800) Axis WSDL2Java error when generating fault types
Description:	The Axis 1.2.1 WSDL2Java tool fails because of a clash in the names of WSDL messages and fault type declarations. For example, defining a fault as follows: <xsd:element name="InvalidStartPositionFault"> <xsd:complexType/> </xsd:element> <wsdl:message name="InvalidStartPositionFault"> <wsdl:part name="InvalidStartPositionFault" element="wsdaix:InvalidStartPositionFault"/> </wsdl:message> The above causes WSDL2Java to produce Java code which does not compile. Changing the first letter of the fault type declaration to lower case, as shown below, fixes this. <xsd:element name="invalidStartPositionFault"> <xsd:complexType/> </xsd:element> <wsdl:message name="InvalidStartPositionFault"> <wsdl:part name="InvalidStartPositionFault" element="wsdaix:invalidStartPositionFault"/> </wsdl:message> Perhaps all fault declarations should be changed in this way so that potential WS-DAI developers choosing to use Axis do not encounter this problem. .
Submitted By:	Steven Lynden
Submitted On:	04/28/2006 10:03 AM EDT
Last Modified:	06/21/2006 10:26 AM EDT
Closed:	06/21/2006 10:26 AM EDT

	Status / Comments		Change Log		Associations		Attachments

Status
Group: *
Status:*	Closed
Category: *
Customer: *
Priority: *	2
Assigned To: *	Steven Lynden
Reported in Release: *
Fixed in Release: *
Estimated Hours: *	0
Actual Hours: *	0

Comments

Steven Lynden: 06/21/2006 10:26 AM EDT
	Comment:	WSDL altered to define fault types in a way that works with Axis WSDL2Java.
	Action:	Update Closed set to 06/21/2006 Status changed from Open to Closed

Steven Lynden: 06/07/2006 7:53 AM EDT

Comment:

Proposed resolution:

So the fault type will not clash with the message name and Axis can generate working Java code, declare all faults types as <Fault name>Type, for 
example:

<xsd:element name="InvalidStartPositionFaultType">
    <xsd:complexType/>
</xsd:element>

<wsdl:message name="InvalidStartPositionFault">
<wsdl:part name="InvalidStartPositionFault" element="wsdaix:InvalidStartPositionFaultType"/>
</wsdl:message>

Action:

Update

Norman Paton: 05/27/2006 3:52 AM EDT
	Action:	Update assigned_to changed from 100 to 9474

Norman Paton: 05/26/2006 10:20 AM EDT
	Action:	Update Priority changed from - to 2

Steven Lynden: 04/28/2006 10:03 AM EDT
	Action:	Create

Return

< Previous

Next >