> From: Wesley Wannemacher [mailto:[EMAIL PROTECTED] > [...] I think this actually stifles my Java development from time to time > because I tend to think in terms of 'normalized db' rather than 'good OO'
I'm not entirely sure I see a huge differentiation between the two. > I figured the business logic bean representing a character would have a > method 'Characteristics[] getExtendedCharacteristics().' I could just > make two beans, but this made sense to me. That makes perfect sense; I wouldn't do it any other way. There's nothing non-OOP about that, and from the DB perspective, as you've said, it just makes sense. Beans can contain lists/sets/etc. of other beans: you *are* making two beans (Character, Characteristic). That said, you might want to use a map or set, not an array. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
