Shame about the applet restriction. Any way to save plumbing time and code noise is important for a modern api and using convention rules is a good way of offering this. It sounds like the WTKX annotation is all you have planned for now, so I'll continue building out my application and think about this some more. Being 'efficient' with my time (some might call it lazy :) I will probably build some utility class to do more complex auto-binding and I'll shame my thoughts/code if I get something like a potential patch together.
Sounds good. Keep in mind that you can use @WTKX in a signed applet. Many non-trivial applications delivered as applets will need to be signed anyways (for example, if the application needs to access the local file system). Also, you can access named values directly from script defined within or included by the page, either in a <wtkx:script> block or in an attribute-based event handler. So, you may want to spend a some time playing with these options before pursuing a more complex alternative.
However, if you do end up prototyping some other approaches, we would love to hear about your experiences.
Thanks, Greg
