A few things I noticed while working with the new GBeans framework...
1. Some parts use Class parameters (e.g. GConstructorInfo), others String for class name.
2. some GAttributeInfo constructors have one boolean and two Boolean parameters.
3. (an actual question, not a niggle) We tended to use data objects in constructors when the number of parameters got really large (ejb containers, web application, etc). What's the recommended style when using persistent attributes? should these be spread out again into zillions of little parameters or should we write a PropertyEditor that can edit the data object encapsulating them? I'd guess the zillions of little parameters would be simpler.
4. I'd think a constructor for GConstructorInfo taking String[], Class[] would be useful as it indicates the types.
thanks david jencks
