Please open a JIRA bug report...

thanks,
dims


----- Original Message -----
From: Malinda Kaushalye <[EMAIL PROTECTED]>
Date: Mon, 14 Jun 2004 11:37:09 +0600
Subject: Security Token Service - wsdl2java generated code
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED]












Hi 
All,


 


I could 
generate the Security Token Service using wsdl2java tool with ws-trust.wsdl and 
other related .xsd files. 


But 
there are some bugs (I guess so) in the generated 
code.


 


//////////////////////////////////////////////////////////////


 


In the RequestTypeEnum 
class there is an unhandled exception(MalformedURIException).  


Please 
check the following section.


    


public 
static final org.apache.axis.types.URI _value1 = new
org.apache.axis.types.URI("http://schemas.xmlsoap.org/ws/2004/04/security/trust/Issue";);


public 
static final org.apache.axis.types.URI _value2 = new
org.apache.axis.types.URI("http://schemas.xmlsoap.org/ws/2004/04/security/trust/Renew";);


public 
static final org.apache.axis.types.URI _value3 = new
org.apache.axis.types.URI("http://schemas.xmlsoap.org/ws/2004/04/security/trust/Validate";);


 


//////////////////////////////////////////////////////////////


 


Some 
return statements do not keep the space ' '  between the return
keyword and the return
type.


e.g. 
please refer the return statement shown below...


 


public 
org.xmlsoap.schemas.ws._2004._04.trust.BinarySecretTypeEnum 
getBinarySecretTypeEnumValue() {        
returnorg.xmlsoap.schemas.ws._2004._04.trust.BinarySecretTypeEnum.fromString(value);


    }  



//////////////////////////////////////////////////////////////


 


It seems the method 
setValue(params) cause some problems. 


e.g.


The method setValue(URI) is 
undefined for the type RequestTypeOpenEnum   File:      
STSServerSideCompile/org/xmlsoap/schemas/ws/_2004/_04/trust 
.RequestTypeOpenEnum.java


 


There are some other files 
having the same problem.         



 


//////////////////////////////////////////////////////////////


 


Do I need to handle these errors or is it a bug (required to 
be fixed) in the WSDL file (or wsdl2java tool)?


 


Thanks and regards,


Kaushalye



-- 
Davanum Srinivas - http://webservices.apache.org/~dims/

Reply via email to