Re: WSDL element restrictions

2008-03-09 Thread Amila Suriarachchi
Please try with a nighly build. I build with the current code base.
And the generated EndUserIdenfier class has the following method

 public void setEndUserIdentifier(java.lang.String param) {

if ((1 <= java.lang.String.valueOf(param).length()) && (
java.lang.String.valueOf(param).length() <= 255)) {
this.localEndUserIdentifier = param;
} else {
throw new java.lang.RuntimeException();
}


}

so this is checked at the setter method.
thanks,
Amila.

On Thu, Mar 6, 2008 at 6:21 AM, David Bunzli <[EMAIL PROTECTED]>
wrote:

>  Hi all,
>
> I haven't been able to get restrictions to consistently work -
> enumerations work, but not length restrictions. I've tried both Axis2
> v1.1.1 (my production version) and Axis2 v1.3 (just in case v1.3 fixed
> this) with no success. Does anyone have any ideas why?
>
> To help, here are the relevant types...
>
>
>
> 
>  
>  
>  
> 
>
>
>
>
> 
>  
>  
> 
>
>
> Here is the complete WSDL...
> 
>   xmlns:eSig="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au"
>  xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/";
>  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
>  xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>  xmlns:xmime="http://www.w3.org/2005/05/xmlmime";
>  name="SigningServices_v1_0_0"
>
>  
> targetNamespace="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au">
>  
>   
>
> targetNamespace="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au"
>
>xmlns:eSig="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au">
>http://www.w3.org/2005/05/xmlmime";
> schemaLocation="xmlmime.xsd" />
>
>
>
> 
>  
>  
>  
> 
>
>
>
>
> 
>  
>  
> 
>
>
>
> 
>   />
>   maxOccurs="1" xmime:expectedContentTypes="application/binary" />
>   maxOccurs="1" />
> 
>
>
>
> 
>   maxOccurs="1" />
>   maxOccurs="1" />
>   maxOccurs="1" />
>   maxOccurs="1" />
>   maxOccurs="1" />
> 
>
>
>
> 
>  
>maxOccurs="1" />
>minOccurs="1" maxOccurs="1" />
>maxOccurs="2" />
>minOccurs="0" maxOccurs="1" />
>minOccurs="0" maxOccurs="1" />
>  
> 
>
>
>
> 
>  
>maxOccurs="1" />
>maxOccurs="1" />
>maxOccurs="1" />
>maxOccurs="1" minOccurs="0" />
>  
> 
>
>
>
>
> 
>   type="xsd:string" />
>   type="xsd:string" />
>   type="xsd:dateTime" />
> 
>
>
>
>
>   
>  
>
>  
>   
>  
>  
>   
>  
>  
>   
>  
>  
>   
>  
>
>  
>   
>
>
>
>
>   
>  
>
>   type="eSig:SigningServices_v1_0_0">
>   http://schemas.xmlsoap.org/soap/http"; />
>   
> soapAction="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au/Verify"
> />
>
> 
>
>
> 
>
>
> 
>
>
> 
>
>   
>  
>
>  
>   
>This web service facilitates the digital signing and
>verification of content while avoiding the need to implement
>the technical, as well as physical and procedural,
>complexities within user applications.
>   
>name="SigningServices_v1_0_0SOAP">
>http://localhost:8080/SecureServices/Services/Signing_v1_0_0"; />
>   
>  
> 
>
>
> >>> "David Bunzli" [EMAIL PROTECTED]> 25/02/2008 3:51 pm >><[EMAIL 
> >>> PROTECTED]/02/2008+3:51+pm+%3E%3E>
> Hi,
>
> Where does Axis2 enforce WSDL element restrictions? For example, if you
> wish a string element to have a minLength of 1 and maxLength of 3, are
> requests rejected by Schema validation if they don't conform? Or are these
> restrictions in the generated classes from Wsdl2Java?
>
> Regards,
> David
>
> *
>
> This email, including any attachmen

WSDL element restrictions

2008-03-05 Thread David Bunzli
Hi all,
 
I haven't been able to get restrictions to consistently work - enumerations 
work, but not length restrictions. I've tried both Axis2 v1.1.1 (my production 
version) and Axis2 v1.3 (just in case v1.3 fixed this) with no success. Does 
anyone have any ideas why?
 
To help, here are the relevant types...
 
   
   

 
 
 

   
 
   
   

 
 

   
 
Here is the complete WSDL...

http://schemas.xmlsoap.org/wsdl/soap/";
 xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/";
 xmlns:xsd="http://www.w3.org/2001/XMLSchema";
 xmlns:xmime="http://www.w3.org/2005/05/xmlmime";
 name="SigningServices_v1_0_0"
 targetNamespace="urn:SigningServices_v1_0_0.secureServices.health.qld.gov.au">
 
  
   http://www.w3.org/2005/05/xmlmime"; 
schemaLocation="xmlmime.xsd" />
 
   
   

 
 
 

   
 
   
   

 
 

   
 
   

 
 
 

   
 
   

 
 
 
 
 

   
 
   

 
  
  
  
  
  
 

   
 
   

 
  
  
  
  
 

   
 

   

 
 
 

   
 
   
   
  
 
 
 
  
 
 
  
 
 
  
 
 
  
 
 
 
  
   
   
   
   
  
 
 
 
  http://schemas.xmlsoap.org/soap/http"; />
  
   
   

   
   

   
   

   
   

   
  
 
 
 
  
   This web service facilitates the digital signing and
   verification of content while avoiding the need to implement
   the technical, as well as physical and procedural,
   complexities within user applications.
  
  
   http://localhost:8080/SecureServices/Services/Signing_v1_0_0"; />
  
 



>>> "David Bunzli" [EMAIL PROTECTED]> 25/02/2008 3:51 pm >> ( mailto:[EMAIL 
>>> PROTECTED]> )
Hi,
 
Where does Axis2 enforce WSDL element restrictions? For example, if you wish a 
string element to have a minLength of 1 and maxLength of 3, are requests 
rejected by Schema validation if they don't conform? Or are these restrictions 
in the generated classes from Wsdl2Java?
 
Regards,
David

*
This email, including any attachments sent with it, is
confidential and for the sole use of the intended recipient(s).
This confidentiality is not waived or lost, if you receive it and
you are not the intended recipient(s), or if it is transmitted/
received in error.

Any unauthorised use, alteration, disclosure, distribution or
review of this email is strictly prohibited.  The information
contained in this email, including any attachment sent with
it, may be subject to a statutory duty of confidentiality if it
relates to health service matters.

If you are not the intended recipient(s), or if you have
received this email in error, you are asked to immediately
notify the sender by telephone collect on Australia
+61 1800 198 175 or by return email.  You should also
delete this email, and any copies, from your computer
system network and destroy any hard copies produced.

If not an intended recipient of this email, you must not copy,
distribute or take any action(s) that relies on it; any form of
disclosure, modification, distribution and/or publication of this
email is also prohibited.

Although Queensland Health takes all reasonable steps to
ensure this email does not contain malicious software,
Queensland Health does not accept responsibility for the
consequences if any person's computer inadvertently suffers
any disruption to services, loss of information, harm or is
infected with a virus, other malicious computer programme or
code that may occur as a consequence of receiving this
email.

Unless stated otherwise, this email represents only the views
of the sender and not the views of the Queensland Government.




Re: WSDL element restrictions

2008-02-28 Thread Amila Suriarachchi
if you generated classes with ADB these restrictions are forced within the
classes.
you can see these codes from the generated classes.

thanks,
Amila.

On Mon, Feb 25, 2008 at 11:21 AM, David Bunzli <
[EMAIL PROTECTED]> wrote:

>  Hi,
>
> Where does Axis2 enforce WSDL element restrictions? For example, if you
> wish a string element to have a minLength of 1 and maxLength of 3, are
> requests rejected by Schema validation if they don't conform? Or are these
> restrictions in the generated classes from Wsdl2Java?
>
> Regards,
> David
>
> *
>
> This email, including any attachments sent with it, is
>
> confidential and for the sole use of the intended recipient(s).
>
> This confidentiality is not waived or lost, if you receive it and
>
> you are not the intended recipient(s), or if it is transmitted/
>
> received in error.
>
>
>
> Any unauthorised use, alteration, disclosure, distribution or
>
> review of this email is strictly prohibited. The information
>
> contained in this email, including any attachment sent with
>
> it, may be subject to a statutory duty of confidentiality if it
>
> relates to health service matters.
>
>
>
> If you are not the intended recipient(s), or if you have
>
> received this email in error, you are asked to immediately
>
> notify the sender by telephone collect on Australia
>
> +61 1800 198 175 or by return email. You should also
>
> delete this email, and any copies, from your computer
>
> system network and destroy any hard copies produced.
>
>
>
> If not an intended recipient of this email, you must not copy,
>
> distribute or take any action(s) that relies on it; any form of
>
> disclosure, modification, distribution and/or publication of this
>
> email is also prohibited.
>
>
>
> Although Queensland Health takes all reasonable steps to
>
> ensure this email does not contain malicious software,
>
> Queensland Health does not accept responsibility for the
>
> consequences if any person's computer inadvertently suffers
>
> any disruption to services, loss of information, harm or is
>
> infected with a virus, other malicious computer programme or
>
> code that may occur as a consequence of receiving this
>
> email.
>
>
>
> Unless stated otherwise, this email represents only the views
>
> of the sender and not the views of the Queensland Government.
>
> 
>
>
>



-- 
Amila Suriarachchi,
WSO2 Inc.


WSDL element restrictions

2008-02-24 Thread David Bunzli
Hi,
 
Where does Axis2 enforce WSDL element restrictions? For example, if you wish a 
string element to have a minLength of 1 and maxLength of 3, are requests 
rejected by Schema validation if they don't conform? Or are these restrictions 
in the generated classes from Wsdl2Java?
 
Regards,
David

*
This email, including any attachments sent with it, is
confidential and for the sole use of the intended recipient(s).
This confidentiality is not waived or lost, if you receive it and
you are not the intended recipient(s), or if it is transmitted/
received in error.

Any unauthorised use, alteration, disclosure, distribution or
review of this email is strictly prohibited.  The information
contained in this email, including any attachment sent with
it, may be subject to a statutory duty of confidentiality if it
relates to health service matters.

If you are not the intended recipient(s), or if you have
received this email in error, you are asked to immediately
notify the sender by telephone collect on Australia
+61 1800 198 175 or by return email.  You should also
delete this email, and any copies, from your computer
system network and destroy any hard copies produced.

If not an intended recipient of this email, you must not copy,
distribute or take any action(s) that relies on it; any form of
disclosure, modification, distribution and/or publication of this
email is also prohibited.

Although Queensland Health takes all reasonable steps to
ensure this email does not contain malicious software,
Queensland Health does not accept responsibility for the
consequences if any person's computer inadvertently suffers
any disruption to services, loss of information, harm or is
infected with a virus, other malicious computer programme or
code that may occur as a consequence of receiving this
email.

Unless stated otherwise, this email represents only the views
of the sender and not the views of the Queensland Government.