|
From: Claudio R. <cla...@li...> - 2008-07-15 09:26:22
|
Jim Moore <moore.jim <at> gmail.com> writes: > > For whatever reason, if you give <at> Command a <at> Target of > ElementType.METHOD in addition to ElementType.TYPE then the > auto-scan breaks. > So I guess it's staying with <at> Invoker, which is fine.I added the > auto-namespacing support, and updated the test cases and sample. I also > renamed the method to getExternalCommandNames() to better identify its new > role.If people think this looks good, I can start migrating this into the > trunk. (And I'm copying spring-desktop <at> googlegroups.com for good > measure >to get this kind of discussion moved into the correct list. > -Jim Moore > Hi Jim, your implementation looks quite good! What about something like this: @Invoke(enableProperty="enabled") ? This annotation parameter would bind the enabled state of the @Invoke to the current value of a property? (Like JSR 296 btw) If the this would make sense for you then it would be another annotation parameter: "selectedProperty" . This additional parameter would toggle the selected state of the action. just my ... Claudio ps: What is the correct list for this disscussion, google group or the spring-rich mailinglist? |