As indicated by my previous posts on the Muse forums I'm trying to create a 
system that uses Muse to create resource properties dynamically, starting from 
scratch when the system starts up. Since I don't know my properties in advance 
it's not possible for me to create the corresponding getters and setters in my 
Capability (that extends AbstractWsResourceCapability)

This gives me problems when initializing my capability since the reflection 
part in AbstractWsResourceCapability.createGettersAndSetters doesn't find the 
correct method in my capability.

A solution for me would be to handle my getters and setters in a more generic 
way like overriding getProperty and setProperty and route all get and set calls 
to these methods. The problem is that I can't access the _gettersByQName and 
_settersByQName Maps since they are private in AbstractWsResourceCapability. 

Is it be possible to make these members protected instead (a change request on 
the code)? Many of the AbstractXXX classes might have similar members that it 
might be wise to make protected in order to supply enough flexibility for 
anyone extending these classes to fit their needs. I leave this to the muse 
developers to decide/comment.

/Mattias


Reply via email to