Is there any compelling reason for me to un-static this method?
<p>I have this SaveCheckedStateToDB() function:</p>

<pre><code>public class oDaA_DBUtils {

    // TOOD: Perhaps this should not be static, and I should force callers to instantiate the class first?
    public static void SaveCheckedStateToDB(int AOptionSelected, String id, boolean AToggledOn)
    {
      //
    }
}
</code></pre>

<p>...that I changed to "static" after getting static about calling it from here prior to adding the "static" keyword:</p>

<pre><code>            cbOnDemand.setOnCheckedChangeListener(new OnCheckedChangeListener()
            {
            @Override 
                public void onCheckedChanged(CompoundButton buttonView, boolean isChecked)
                {
                // Contact id is a string?
                oDaA_DBUtils.SaveCheckedStateToDB(oDaA_Consts.ALERT_ON_DEMAND, id, isChecked);
                }
            });
</code></pre>

<p>Now it compiles, but is that a "wrong" way of working? Should I remove the "static" appendage/decoration and force callers to instantiate the class prior to calling SaveCheckedStateToDB()?</p>
