You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Adrian Dick (JIRA)" <ax...@ws.apache.org> on 2005/06/30 17:56:57 UTC
[jira] Created: (AXISCPP-715) Add test cases to validate all XSD built-in simple types
Add test cases to validate all XSD built-in simple types
--------------------------------------------------------
Key: AXISCPP-715
URL: http://issues.apache.org/jira/browse/AXISCPP-715
Project: Axis-C++
Type: Test
Components: Client - Deserialization, Serialization
Versions: current (nightly)
Reporter: Adrian Dick
Assigned to: Adrian Dick
We now claim to support all the XSD built-in simple types, but we need to include tests to ensure these have been correctly implemented, and also detect any future regressions.
These tests should validate boundary conditions for each type - as specified by the constraining facets for each within the XSD Datatypes specification.
We also need to ensure we validate the various paths through the engine to serialize/deserialize XSD types, and also within WSDL2Ws generating valid code for the use of XSD types. The tests I propose for this are:
- Within an element (nillable and non-nillable)
- Within an attribute (required and optional)
- As an array
- Within a complex type
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-715) Add test cases to validate all XSD built-in simple types
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-715?page=comments#action_12314875 ]
Adrian Dick commented on AXISCPP-715:
-------------------------------------
Boolean XSD type now added, and uncovered a minor issue in the external API (see AXISCPP-724 )
> Add test cases to validate all XSD built-in simple types
> --------------------------------------------------------
>
> Key: AXISCPP-715
> URL: http://issues.apache.org/jira/browse/AXISCPP-715
> Project: Axis-C++
> Type: Test
> Components: Serialization, Client - Deserialization
> Versions: current (nightly)
> Reporter: Adrian Dick
> Assignee: Adrian Dick
>
> We now claim to support all the XSD built-in simple types, but we need to include tests to ensure these have been correctly implemented, and also detect any future regressions.
> These tests should validate boundary conditions for each type - as specified by the constraining facets for each within the XSD Datatypes specification.
> We also need to ensure we validate the various paths through the engine to serialize/deserialize XSD types, and also within WSDL2Ws generating valid code for the use of XSD types. The tests I propose for this are:
> - Within an element (nillable and non-nillable)
> - Within an attribute (required and optional)
> - As an array
> - Within a complex type
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-715) Add test cases to validate all XSD built-in simple types
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-715?page=comments#action_12315026 ]
Adrian Dick commented on AXISCPP-715:
-------------------------------------
Unsigned Integer XSD types have now been added to the unit tests. These uncovered one new issue ( AXISCPP-730 ) and have helped confirm the fix to an existing issue ( AXISCPP-653 ).
> Add test cases to validate all XSD built-in simple types
> --------------------------------------------------------
>
> Key: AXISCPP-715
> URL: http://issues.apache.org/jira/browse/AXISCPP-715
> Project: Axis-C++
> Type: Test
> Components: Serialization, Client - Deserialization
> Versions: current (nightly)
> Reporter: Adrian Dick
> Assignee: Adrian Dick
>
> We now claim to support all the XSD built-in simple types, but we need to include tests to ensure these have been correctly implemented, and also detect any future regressions.
> These tests should validate boundary conditions for each type - as specified by the constraining facets for each within the XSD Datatypes specification.
> We also need to ensure we validate the various paths through the engine to serialize/deserialize XSD types, and also within WSDL2Ws generating valid code for the use of XSD types. The tests I propose for this are:
> - Within an element (nillable and non-nillable)
> - Within an attribute (required and optional)
> - As an array
> - Within a complex type
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (AXISCPP-715) Add test cases to validate all XSD built-in simple types
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-715?page=all ]
Adrian Dick closed AXISCPP-715:
-------------------------------
Fix Version: current (nightly)
Resolution: Fixed
A set of unit tests has been added for each of the XSD built-in simple types.
> Add test cases to validate all XSD built-in simple types
> --------------------------------------------------------
>
> Key: AXISCPP-715
> URL: http://issues.apache.org/jira/browse/AXISCPP-715
> Project: Axis-C++
> Type: Test
> Components: Client - Deserialization, Serialization
> Versions: current (nightly)
> Reporter: Adrian Dick
> Assignee: Adrian Dick
> Fix For: current (nightly)
>
> We now claim to support all the XSD built-in simple types, but we need to include tests to ensure these have been correctly implemented, and also detect any future regressions.
> These tests should validate boundary conditions for each type - as specified by the constraining facets for each within the XSD Datatypes specification.
> We also need to ensure we validate the various paths through the engine to serialize/deserialize XSD types, and also within WSDL2Ws generating valid code for the use of XSD types. The tests I propose for this are:
> - Within an element (nillable and non-nillable)
> - Within an attribute (required and optional)
> - As an array
> - Within a complex type
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-715) Add test cases to validate all XSD built-in simple types
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-715?page=comments#action_12315158 ]
Adrian Dick commented on AXISCPP-715:
-------------------------------------
All the xsd:string derived types have now been added to the unit tests. This uncovered one new issue ( AXISCPP-733 ), and showed one issue ( AXISCPP-710 ) to be invalid.
> Add test cases to validate all XSD built-in simple types
> --------------------------------------------------------
>
> Key: AXISCPP-715
> URL: http://issues.apache.org/jira/browse/AXISCPP-715
> Project: Axis-C++
> Type: Test
> Components: Serialization, Client - Deserialization
> Versions: current (nightly)
> Reporter: Adrian Dick
> Assignee: Adrian Dick
>
> We now claim to support all the XSD built-in simple types, but we need to include tests to ensure these have been correctly implemented, and also detect any future regressions.
> These tests should validate boundary conditions for each type - as specified by the constraining facets for each within the XSD Datatypes specification.
> We also need to ensure we validate the various paths through the engine to serialize/deserialize XSD types, and also within WSDL2Ws generating valid code for the use of XSD types. The tests I propose for this are:
> - Within an element (nillable and non-nillable)
> - Within an attribute (required and optional)
> - As an array
> - Within a complex type
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-715) Add test cases to validate all XSD built-in simple types
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-715?page=comments#action_12315162 ]
Adrian Dick commented on AXISCPP-715:
-------------------------------------
Remaining XSD simple types have now been added to the unit tests, uncovering a further two issues ( AXISCPP-734 ) and ( AXISCPP-735 ).
> Add test cases to validate all XSD built-in simple types
> --------------------------------------------------------
>
> Key: AXISCPP-715
> URL: http://issues.apache.org/jira/browse/AXISCPP-715
> Project: Axis-C++
> Type: Test
> Components: Client - Deserialization, Serialization
> Versions: current (nightly)
> Reporter: Adrian Dick
> Assignee: Adrian Dick
> Fix For: current (nightly)
>
> We now claim to support all the XSD built-in simple types, but we need to include tests to ensure these have been correctly implemented, and also detect any future regressions.
> These tests should validate boundary conditions for each type - as specified by the constraining facets for each within the XSD Datatypes specification.
> We also need to ensure we validate the various paths through the engine to serialize/deserialize XSD types, and also within WSDL2Ws generating valid code for the use of XSD types. The tests I propose for this are:
> - Within an element (nillable and non-nillable)
> - Within an attribute (required and optional)
> - As an array
> - Within a complex type
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (AXISCPP-715) Add test cases to validate all XSD built-in simple types
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-715?page=comments#action_12314784 ]
Adrian Dick commented on AXISCPP-715:
-------------------------------------
Date/Time base XSD types have now been added to the unit tests, and have uncovered some issues (see http://issues.apache.org/jira/browse/AXISCPP-717 and http://issues.apache.org/jira/browse/AXISCPP-718 ).
> Add test cases to validate all XSD built-in simple types
> --------------------------------------------------------
>
> Key: AXISCPP-715
> URL: http://issues.apache.org/jira/browse/AXISCPP-715
> Project: Axis-C++
> Type: Test
> Components: Serialization, Client - Deserialization
> Versions: current (nightly)
> Reporter: Adrian Dick
> Assignee: Adrian Dick
>
> We now claim to support all the XSD built-in simple types, but we need to include tests to ensure these have been correctly implemented, and also detect any future regressions.
> These tests should validate boundary conditions for each type - as specified by the constraining facets for each within the XSD Datatypes specification.
> We also need to ensure we validate the various paths through the engine to serialize/deserialize XSD types, and also within WSDL2Ws generating valid code for the use of XSD types. The tests I propose for this are:
> - Within an element (nillable and non-nillable)
> - Within an attribute (required and optional)
> - As an array
> - Within a complex type
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira