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 "Manohar (JIRA)" <ax...@ws.apache.org> on 2005/08/08 12:47:34 UTC
[jira] Created: (AXISCPP-788) AXIS C++ allows to set positive values to XSD_negativeInteger type
AXIS C++ allows to set positive values to XSD_negativeInteger type
-------------------------------------------------------------------
Key: AXISCPP-788
URL: http://issues.apache.org/jira/browse/AXISCPP-788
Project: Axis-C++
Type: Bug
Reporter: Manohar
Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
serialze/deserialized)
I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
Regards
Manohar.
--
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] Reopened: (AXISCPP-788) AXIS C++ allows to set positive values to XSD_negativeInteger type
Posted by "Manohar (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-788?page=all ]
Manohar reopened AXISCPP-788:
-----------------------------
> AXIS C++ allows to set positive values to XSD_negativeInteger type
> -------------------------------------------------------------------
>
> Key: AXISCPP-788
> URL: http://issues.apache.org/jira/browse/AXISCPP-788
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Samisa Abeysinghe
> Fix For: 1.6 Alpha
>
> Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
> 1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
> 2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
> serialze/deserialized)
> I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
> Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
> Regards
> Manohar.
--
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] Resolved: (AXISCPP-788) AXIS C++ allows to set positive values to XSD_negativeInteger type
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-788?page=all ]
Adrian Dick resolved AXISCPP-788:
---------------------------------
Resolution: Fixed
I have modified xsd:nonPositiveInteger and xsd:negativeInteger to use long long, rather than unsigned long long, which should prevent the confusion caused by using an unsigned type.
> AXIS C++ allows to set positive values to XSD_negativeInteger type
> -------------------------------------------------------------------
>
> Key: AXISCPP-788
> URL: http://issues.apache.org/jira/browse/AXISCPP-788
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Adrian Dick
> Fix For: 1.6 Alpha
>
> Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
> 1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
> 2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
> serialze/deserialized)
> I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
> Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
> Regards
> Manohar.
--
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-788) AXIS C++ allows to set positive values to XSD_negativeInteger type
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-788?page=all ]
Samisa Abeysinghe closed AXISCPP-788:
-------------------------------------
Fix Version: 1.6 Alpha
Resolution: Fixed
It would throw an exception in case of invalid values
> AXIS C++ allows to set positive values to XSD_negativeInteger type
> -------------------------------------------------------------------
>
> Key: AXISCPP-788
> URL: http://issues.apache.org/jira/browse/AXISCPP-788
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Samisa Abeysinghe
> Fix For: 1.6 Alpha
>
> Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
> 1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
> 2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
> serialze/deserialized)
> I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
> Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
> Regards
> Manohar.
--
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] Assigned: (AXISCPP-788) AXIS C++ allows to set positive values to XSD_negativeInteger type
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-788?page=all ]
Adrian Dick reassigned AXISCPP-788:
-----------------------------------
Assign To: Adrian Dick (was: Samisa Abeysinghe)
> AXIS C++ allows to set positive values to XSD_negativeInteger type
> -------------------------------------------------------------------
>
> Key: AXISCPP-788
> URL: http://issues.apache.org/jira/browse/AXISCPP-788
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Adrian Dick
> Fix For: 1.6 Alpha
>
> Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
> 1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
> 2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
> serialze/deserialized)
> I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
> Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
> Regards
> Manohar.
--
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-788) AXIS C++ allows to set positive values
to XSD_negativeInteger type
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-788?page=all ]
Fred Preston closed AXISCPP-788:
--------------------------------
> AXIS C++ allows to set positive values to XSD_negativeInteger type
> -------------------------------------------------------------------
>
> Key: AXISCPP-788
> URL: http://issues.apache.org/jira/browse/AXISCPP-788
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Adrian Dick
> Fix For: 1.6 Alpha
>
> Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
> 1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
> 2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
> serialze/deserialized)
> I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
> Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
> Regards
> Manohar.
--
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-788) AXIS C++ allows to set positive values to XSD_negativeInteger type
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-788?page=comments#action_12318578 ]
Samisa Abeysinghe commented on AXISCPP-788:
-------------------------------------------
I fixed the code to check for the value range.
> AXIS C++ allows to set positive values to XSD_negativeInteger type
> -------------------------------------------------------------------
>
> Key: AXISCPP-788
> URL: http://issues.apache.org/jira/browse/AXISCPP-788
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Samisa Abeysinghe
>
> Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
> 1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
> 2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
> serialze/deserialized)
> I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
> Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
> Regards
> Manohar.
--
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] Assigned: (AXISCPP-788) AXIS C++ allows to set positive values to XSD_negativeInteger type
Posted by "Samisa Abeysinghe (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-788?page=all ]
Samisa Abeysinghe reassigned AXISCPP-788:
-----------------------------------------
Assign To: Samisa Abeysinghe
> AXIS C++ allows to set positive values to XSD_negativeInteger type
> -------------------------------------------------------------------
>
> Key: AXISCPP-788
> URL: http://issues.apache.org/jira/browse/AXISCPP-788
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Samisa Abeysinghe
>
> Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
> 1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
> 2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
> serialze/deserialized)
> I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
> Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
> Regards
> Manohar.
--
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-788) AXIS C++ allows to set positive values to XSD_negativeInteger type
Posted by "Adrian Dick (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-788?page=comments#action_12319381 ]
Adrian Dick commented on AXISCPP-788:
-------------------------------------
There seems to be some misunderstanding on what goes on with negativeInteger and nonPositiveInteger.
Within AxisUserAPI.hpp these two types are declared as unsigned LONGLONG (64bit integer), so it isn't possible to provide a signed negative value as you will get an unexpectedly large unsigned value( as seen in case 2. of the original description). Also, as a result of this, the recently introduced code in the constructors, below, will fail for all values except 0 (if compiler treats as signed) or all values over 18446744073709551615 (is compiler treats as unsigned) :
if(valueToCheck > -1)
throw AxisSoapException(CLIENT_SOAP_SOAP_CONTENT_ERROR, "PositiveInteger value must be minus one or less");
As I see it, there are two possible fixes:
1) Improve the API documentation within AxisUserAPI.hpp to make it clear that xsd__negativeInteger is an unsigned value that is implicitly negative.
2) Modify xsd__negativeInteger to be a signed LONGLONG, and make some minor modifications to the checks for Max/Min Inclusive/Exclusive (which currently assume negative unsigned integer).
In either case, the recently introduced checks within the constructor are not required because this is already carried out within the serialize method (which is invoked as part of the object constructor)
For the second case, we will loose 1/2 our potential value space -- but others may not see this as a big issue.
Adrian
> AXIS C++ allows to set positive values to XSD_negativeInteger type
> -------------------------------------------------------------------
>
> Key: AXISCPP-788
> URL: http://issues.apache.org/jira/browse/AXISCPP-788
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Samisa Abeysinghe
> Fix For: 1.6 Alpha
>
> Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
> 1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
> 2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
> serialze/deserialized)
> I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
> Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
> Regards
> Manohar.
--
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-788) AXIS C++ allows to set positive values to XSD_negativeInteger type
Posted by "Manohar (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-788?page=comments#action_12319157 ]
Manohar commented on AXISCPP-788:
---------------------------------
Hi Samisa,
XSD_negativeInteger and XSD_nonPositiveInteger still have problems. The following AxisSoapException is thrown when both positive as well as negative inputs are given for these types.
Exception : AxisSoapException:Received content is faulty NonPositiveInteger value must be non positive
The existing testscases XSD_negativeIntegerClient and XSD_nonPositiveIntegerClient can be used to see this problem.
Regards
Manohar
> AXIS C++ allows to set positive values to XSD_negativeInteger type
> -------------------------------------------------------------------
>
> Key: AXISCPP-788
> URL: http://issues.apache.org/jira/browse/AXISCPP-788
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Samisa Abeysinghe
> Fix For: 1.6 Alpha
>
> Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
> 1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
> 2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
> serialze/deserialized)
> I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
> Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
> Regards
> Manohar.
--
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-788) AXIS C++ allows to set positive values to XSD_negativeInteger type
Posted by "Fred Preston (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXISCPP-788?page=comments#action_12331993 ]
Fred Preston commented on AXISCPP-788:
--------------------------------------
Could the fixer of this JIRA either create a new or incorporate into an existing test a test that would create a for this function so that we do not regress?
> AXIS C++ allows to set positive values to XSD_negativeInteger type
> -------------------------------------------------------------------
>
> Key: AXISCPP-788
> URL: http://issues.apache.org/jira/browse/AXISCPP-788
> Project: Axis-C++
> Type: Bug
> Reporter: Manohar
> Assignee: Adrian Dick
> Fix For: 1.6 Alpha
>
> Axis C++ allows to set positive values for XSD_negativeInteger dataype. As per the XML schema specification, the ·value space· of negativeInteger is the infinite set {...,-2,-1} and it's maxInclusive is -1. This means, only negagtive integer values should be allowed and no positive values. But, I see that positive values can also be set for this datatype. As per my observation,
> 1. negativeInteger and nonPositiveInteger types accept positive values ( e.g. +1 is accepted and same value is displayed after serialze/deserialized)
> 2. positiveInteger and nonNegativeInteger types accept negative values ( e.g. -1 is accepted and 18446744073709551615 value is displayed after
> serialze/deserialized)
> I think this is not the correct behaviour. Though these XML datatypes are mapped to different datatypes of client programming languages (C/C++ in our case), this should not be allowed while serializing/deserializing in the client product and some exception should be reported indicating the error. I see the whole purpose of a datatype is lost when a +ve value is set for a negativeInteger type and vice versa.
> Testcases written for these types ( XSD_negativeIntegerClient.cpp, XSD_nonPositiveIntegerClient.cpp, XSD_positiveIntegerClient.cpp and XSD_nonNegativeIntegerClient.cpp) show this problem.
> Regards
> Manohar.
--
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