> org.apache.turbine.om.map
> DatabaseMap.java
> DatabaseMapBuilder.java
> ColumnMap.java
> TableMap.java
I still don't think these are business objects. They don't have any
business meaning in terms of an "object model." They are db utility classes
used to *help* create objects so I'd like to see them stay in
org.apache.turbine.util.db.
Now that I think about it org.apache.turbine.util.db.map would make more
sense.
> org.apache.turbine.om.user
> TurbineUser.java
> User.java
> UserFactory.java
> org.apache.turbine.om.user.peer
> TurbineUserPeer.java
> VisitorRolePeer.java
I still think UserFactory fits better in user.peer since it itself is not an
object that one would consider part of the object model. As I said above,
it helps create business objects but it is not a business object itself.
+1 on everything else
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
