new is not a great command, it implies gc down the road, so allways spend a split second saying... hmm. (lots of people "new" beans, when Struts already did new, for example).
I am not sure (tired) but... most of the time _current is a pointer to an existing "row" in the "list", so no need to new if I just point.
In some situations, there is no "row", so I must new.


If indeed it was needed to new majority of time, it should be in base (rule is "design for the rule, not for the exception").
.V


Rick Reumann wrote:


Are there any drawbacks you can see to adding the _current = new HashMap();
inside of the BaseBean constructor vs having to include that in the
constructors of the BaseBean subclasses? Seems like it would save a line
of code from each subclass by adding it to the BaseBean constructor
but maybe there is a reason to not do this that I'm missing.


Thanks,




-- Vic Cekvenich, Struts Instructor, 1-800-917-JAVA

Advanced <a href ="baseBeans.com">Struts Training</a> and project recovery in North 
East.
Open Source <a href ="baseBeans.com">Content Management</a>  basicPortal sofware
Best practice<a href ="baseBeans.com">Struts Support</a> v.1.1 helper ScafflodingXPress


_______________________________________________ MVC-Programmers mailing list [EMAIL PROTECTED] http://www.basebeans.net:8080/mailman/listinfo/mvc-programmers

Reply via email to