Issue 10: Allow serialization of read-only properties
Status:  Verified
Owner: ----
Closed:  Apr 2009
Reported by pca...@gmail.com, Apr 7, 2009
It seems that if a property has a getter but not a setter, it will be
ignored by the type inspection machinery.  It would be nice to be able to
serialize out those read-only fields.

As it is, one has to add dummy setters to model objects in order to
serialize those values out.

Apr 7, 2009
#1 pca...@gmail.com
This is really more of a feature request, but I don't see how to change the issue type.
Apr 8, 2009
Project Member #2 alex.id....@gmail.com
It's a good point. I'll add support for serializing readOnly fields.

Apr 8, 2009
Project Member #3 alex.id....@gmail.com
(No comment was entered for this change.)
Status: Accepted
Labels: -Type-Defect Type-Enhancement
Apr 8, 2009
#4 pca...@gmail.com
I've patched this myself at line 163 of Descriptor store by just commenting out the
readwrite predicate:

            for each (field in descriptor..accessor /*.(@access == "readwrite")*/ ) {

Not sure if that is the best solution but it is working for me.
Apr 8, 2009
Project Member #5 alex.id....@gmail.com
I added suport for both serializing readOnly fields and deserializing writeOnly 
fields. Didn't get a chance to do a full test sequence yet but seems to be working 
ok. 
Apr 11, 2009
Project Member #6 alex.id....@gmail.com
(No comment was entered for this change.)
Status: Fixed
Dec 28, 2009
Project Member #7 alex.id....@gmail.com
(No comment was entered for this change.)
Status: Verified