Thomas Dudziak wrote:
Well actually it might enforce it - it depends on what you use theyes. and this is a problem - I want my interfaces contain only business methods - so
interfaces for, i.e. whether you want an implementation-agnostic
persistence mechanism or not. If you use interfaces, then yes, you
have to expose the (bean) properties, but you can hide the
implementation much more strongly (factories).
I'll preferer have assignToGroup(Group) method instead setGroupId(Integer) .
I found that it's very useful and clear when interfaces are really free from implementation details.
And if you refer to interfaces from references/collections, then you really should declare at least the primarykey fields (references) / foreignkey fields (collections) in the interface to communicate your intent.
Tom
by the way I want to thank you for xdoclet - its realy usefull and bugless tool ;)
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
