>  In other words, I'd like to avoid building get/set methods in my Jython
>  class instances which are being used by a Java program as a "bean".
>  For this to work, there would have to be something that automatically
>  built get/set methods for classes (as Groovy does), or there would have
>  to be a run-time mechanism that sees a getFoo/setFoo call and converts
>  it to a simpler property usage.

As I said - currently that's not implemented. And it can't be without a 
declarative step. similar to the existing 

@sig 

extension to specify which overloaded method exactly to implement. It could 
look like this:

class Foo:
    ''' @properties = [bar, baz]'''

and then would automatically generate get/set methods for these. But it has to 
be implemented.

Diez


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Jython-users mailing list
Jython-users@[...].net
https://lists.sourceforge.net/lists/listinfo/jython-users