DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=35687>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=35687 ------- Additional Comments From [EMAIL PROTECTED] 2005-07-13 15:51 ------- (In reply to comment #5) > I consider it a step back, because there's a lot of duplication in your design. > Rather than have on class hold the triplet of name+type+class, you end up > duplicating information across two classes. It makes it harder to follow, and > increases the chances of mistakes/inconsistencies/confusion. > Personally, I find one long list in one place much simpler than two half > duplicated lists in two places... > It might not be purest OO, but I find it a more pragmatic design! There is no duplication. There are two objects and which of them is responsible for the specific functionality. RecordTypes is needed only to map ID and Name. That'all. Consider it as final class. It is not meant to be modified. RecordFactory is responsible for the instantiation. When you create a new class which extents Record you will have to register it there, not in RecordTypes! Also I think we should follow object oriented design. It's going to be a big project and we must do it right. What seems pragmatic to you now can be a pain very soon!. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] Mailing List: http://jakarta.apache.org/site/mail2.html#poi The Apache Jakarta POI Project: http://jakarta.apache.org/poi/
