MethodBindings called on unrendered components

[Galen Dunkleberger <ga...@gmail.com>]

I turned logging on for my application and noticed that method
bindings were being called for components that were in a panel stack
and had not yet been rendered. Is this typical behavior? Should
methods which I'm binding to in my managed beans first check to make
sure that their component is actually rendered before performing their
actions? For instance I have a panel stack and one of the panelGroups
contains a data table which is bound to a managedbean method that hits
the database and retrieves the data. When I first enter the
application that particular panelGroup is not rendered (specifically
because I don't have all the data yet needed to make the database
call). However, the method is called on the managed bean and an
exception is thrown but apparently swallowed by the
PropertyResolverImpl and only displayed as an error in the logging
system. Should I expect this behavior or am I doing something wrong?
           Thanks,
              Galen