This week's book giveaway is in the Performance forum. We're giving away four copies of The Java Performance Companion and have Charlie Hunt, Monica Beckwith, Poonam Parhar, & Bengt Rutisson on-line! See this thread for details.
I am trying to make a small issue tracker to for learning JSP/ Servelets. I am trying to follow MVC architecture for the same and I am stuck in a design issue with model classes.
Here is the scene....
There is a entity "IssueAtribute", which represents elements in a Issue. (Basically entity "Issue" contains a Ordered List of "IssueAttributes").
Now "IssueAttribute" can be of various types eg. TextIssueAttribute, LongTextIssueAttribute, DateIssueAttribute, etc. The "View" in the MVC will probably use this information to render the issue attribute. eg. A JSP might create a Calendar widget for DateIssueType and TextArea for LongTextIssueType etc.
So the design decision that i am struck with is how design class hierarchy for "IssueAttribute" and its types. I considered using inheritance for all its types as that way I can keep all "IssueAttributes" in "Issue" as a single ArrayList but that will loose its type information unless is do a check at runtime (using instanceOf) which i think is in elegant.