|
Arnaud, what do you think...something that the binding file could support?
The binding file is definitely the place to go. We could have a feature to
select the visibility of a class member (private, public,protected) One could, for example, add a new attribute 'visibilty' to the complexType 'fieldType' in binding.xsd, similar to
<xsd:attribute name="visibility"> to allow a user to specify the visibility of a field. Index: C:/workspace/castor1675/src/main/resources/org/exolab/castor/builder/binding/binding.xsd
=================================================================== — C:/workspace/castor1675/src/main/resources/org/exolab/castor/builder/binding/binding.xsd (revision 6380) +++ C:/workspace/castor1675/src/main/resources/org/exolab/castor/builder/binding/binding.xsd (working copy) @@ -188,6 +188,15 @@ </xsd:restriction> </xsd:simpleType> </xsd:attribute> + <xsd:attribute name="visibility"> + <xsd:simpleType> + <xsd:restriction base="xsd:string"> + <xsd:enumeration value="public"/> + <xsd:enumeration value="protected"/> + <xsd:enumeration value="private"/> + </xsd:restriction> + </xsd:simpleType> + </xsd:attribute> <xsd:attribute name="validator" type="xsd:string"/> </xsd:complexType> Initial (untested) patch
Patch committed (incl. new CTF test case). If you still would want to see the changes to the property change listener being implemented, please feel free to open a new (follow-up) issue.
|
|||||||||||||||||||||||||||||||||||||||||||||||||
ahead and do it, I'd like to know if the castor developers think the features
are desirable and the likelihood of it getting accepted. Assuming of course the
patch is good and doesn't have any bugs.