Content Bean annotated classes should be able to be configured in both external configuration and local classes in a component without warning

When it register local annotated classes which is retrieved by invoking overriden #getLocalAnnotatedClasses(), BaseHstComponent leaves a warning log if there already exists that annotated class as follows:

08.08.2011 13:34:22 WARN [org.hippoecm.hst.component.support.bean.BaseHstComponent.getObjectConverter():449] local added class 'org.onehippo.forge.tcmp.beans.AbstractTagBean' already present. Skipping

However, I found an example where the annotated beans should be configured in both web.xml and local annotated classes in a component.
In the former case, for example, a news content bean can refer a tag child bean. In this case, the news component is basically unaware of the local annotated classes.
So, in this case, the annotated beans should be registered through web.xml as it does for news beans.

Of course, the dedicated tag component provided by tcmp forge project is still able to register its own local annotated beans without configuring web.xml.

Therefore, I think the warning log is not necessary; should be a debug log.