GetClientId messages in log

Question

JDEV 12.1.3
WEBLOGIC 12.1.3
When run my page, I see this warning in weblogic webserver console window. I DO not have getClientId call in my code.
These are two declarative component we developed. There is no getClientId in declarative component code too.
Not sure what caused this warnings and if these warnings are harmful or not.
<Apr 21, 2015 11:21:56 AM PDT> <Warning> <org.apache.myfaces.trinidad.component.UIXComponentBase> <BEA-000000> <getClientId should not be called while the view is being constructed. Component ID: pl1>
<Apr 21, 2015 11:21:56 AM PDT> <Warning> <org.apache.myfaces.trinidad.component.UIXComponentBase> <BEA-000000> <getClientId should not be called while the view is being constructed. Component ID: dl5>

Answer 1

Commenting out this code does not get rid of the messages.
Got a response from ADF Dev. Share with the community here.
DMS error can be ignored - this is an artifact of the logging level being used and is caused when we are writing supplemental information for the ADF Request Tracing feature. So we should see these go away when some of the diagnostics are switched off.
The GetClientId error is more puzzling.  We did have some issues in 12.1.2 with this error occurring in the base framework code, but these should all be fixed in 12.1.3.  A couple of the issues where specifically linked to certain components (geomap and dialog) but those have been resolved.
So there are two possibilities here. 
1) There is a similar issue to the above which is somehow linked to the use of declarative component which triggers this warning in the framework (so nothing to do with your code)
2) There is a call to getClientId in your code, but not necessarily explicitly in the stuff you have written - it could for example be in a PhaseListener or Filter which is being run as your page is being processed. 
Note that in the cases where you see an unknown component id such as j_id15 this is just where the page defines a component that you have not set an explicit ID property for, and so JSF has generated an internal ID for itself . It might be a good idea to check your pages to add explicit IDs to any components that don’t have them, just to make future issue diagnosis simpler, but it’s not required that you do this, it’s just a recommendation.