Re: Code Generation Problem ( Order of constructor parameters)

2008-07-31 Thread Samisa Abeysinghe 

This could be a bug. Could you please provide the WSDL you are using.

Thanks,
Samisa...

Shripad Gokhale wrote:


 

In a certain situation, the code generated by AXIS 1.4 is giving 
compilation errors. After investigation, I found that in some classes, 
the super class’s constructors were called with wrong order of input 
parameters. For example, a class CustomerListEntity which extends 
ListMessageEntity calls super(long, MessageEntity[]) from its 
constructor. But, the actual definition of the constructor of 
ListMessageEntity is ListMessageEntity(MessageEntity[], long). 
Similarly, there are a couple of other classes also doing the same 
thing. Due to this, compilation is failing.


 

 


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp




--
Samisa Abeysinghe

http://people.apache.org/~samisa/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Code Generation Problem ( Order of constructor parameters)

2008-07-30 Thread Shripad Gokhale 
 

In a certain situation, the code generated by AXIS 1.4 is giving
compilation errors. After investigation, I found that in some classes,
the super class's constructors were called with wrong order of input
parameters. For example, a class CustomerListEntity which extends
ListMessageEntity calls super(long, MessageEntity[]) from its
constructor. But, the actual definition of the constructor of
ListMessageEntity is ListMessageEntity(MessageEntity[], long).
Similarly, there are a couple of other classes also doing the same
thing. Due to this, compilation is failing.

 

 


This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at http://www.amdocs.com/email_disclaimer.asp