[
https://issues.apache.org/jira/browse/TUSCANY-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12471353
]
Frank Budinsky commented on TUSCANY-1093:
-----------------------------------------
I have my doubts about this comment from above:
> ... it seems that some changes were made to modify this behavior. Setting
> boolean attribute when the type is defined in an XSD is now working.
I don't know of, or see, any changes that would fix this problem in the XSD
case. I don't believe the proper "general" solution to this issue (new
semantics of isSet in SDO 2.1) has been implemented yet.
Can someone investigate and/or explain why it seems to be working in the XSD
case?
Thanks,
Frank.
> isSet returning false when boolean set to false, or int set to 0
> ----------------------------------------------------------------
>
> Key: TUSCANY-1093
> URL: https://issues.apache.org/jira/browse/TUSCANY-1093
> Project: Tuscany
> Issue Type: Bug
> Components: Java SDO Implementation
> Reporter: Robbie Minshall
> Priority: Critical
> Attachments: patch
>
>
> when boolean property is set to false a call to isSet returns false ( should
> return true ).
> when an int property is set to 0 a call to isSet returns false ( should
> return true ).
> This causes DataObject serialization ( our scenario involves using the sca ws
> binding ) to be missing values that have been set.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
