Interesting question for you folks. Okay, I have an EJB that has hierarchy
within it and I want to use JAWS to deploy it. During my experiments this
weekend I came up with 2 ways to represent this hierarchy:
1) Build one table that represents the entire object hierarchy chain such
that any object can have a single record in the table.
2) Build a table for each one of the objects in the hierarchy and add a
bunch of methods to perform lookups within the hierarchy for parent and
child classes.
If I am building a system with JAWS, and assuming that the system may change
- which approach seems to make the most sense? At the moment I am leaning
towards building a single table rather that doing a leaf node
implementation.
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
