On Friday 22 November 2002 05:52 pm, Rob van Maris wrote: > <Pierre van Rooden:> > > > I see no reason to make it a staic method. > > A reason I can see to NOT make it static is that you cannot override the > > methods if you make them static. > > They are not instance methods because they are not tied to a builder > instance. > In addition, I sees no reason to override them, on the contrary: I think > this should be prevented.
hmm . an object builder belongs to a cloud MMOBjectBuilder has a datamember mmb (by inheriance from MMTable) mmb shoud be used to get a database connection. So for me in theory I think the method should not be static at all. "if it's static it's not builder specific"? but I think the "problem" is that is does not belong at all in a builder (it's not builder specific). I think i should be in MMBase.java there might still be fuctions in MMObjectBuilder but that should be a "marco/shortcut" and i should use the object builder instance.
