This discussion is archived
6 Replies Latest reply: May 30, 2013 1:02 AM by Steven Davelaar RSS

No query Bind parameters passed into applyBindParams

Stephen J. Journeyer
Currently Being Moderated
Is there a way to suppress this message?
<JhsApplicationModuleImpl> <applyBindParams> No query Bind parameters passed into applyBindParams for Lookup1, do nothing

It doesn't seem to be affecting anything, but they're filling up our log files.
We're in JDev 11.1.1.4, JHS 11.1.1.3, but the app was upgraded from JHS 10 and it uses JHS lists (not ADF model lists).

Thanks,
Stephen J.
  • 1. Re: No query Bind parameters passed into applyBindParams
    Steven Davelaar Employee ACE
    Currently Being Moderated
    Stephen,

    Those are ADF Logger messages at the "info" level.
    If you don't want them, then just raise the log level for oracle.jheadstart package to warning

    Steven Davelaar,
    JHeadstart Team.
  • 2. Re: No query Bind parameters passed into applyBindParams
    Stephen J. Journeyer
    Currently Being Moderated
    When viewing the log messages in WebLogic EM console they show up as errors.


    May 17, 2013 7:49:03 AM EDT (Error)
                   
    Message Level     1
    Relationship ID     0
    Component     MS1
    Module     oracle.jheadstart.model.adfbc.v2.JhsApplicationModuleImpl
    Host     dtgwebl103
         
    Host IP Address     127.0.0.1
    User     <anonymous>
    Thread ID     [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'
    ECID     11d1def534ea1be0:7cad7c04:13ea635282d:-7ffd-0000000000006ddb
         
    Message     No query Bind parameters passed into applyBindParams for Lookup1, do nothing
  • 3. Re: No query Bind parameters passed into applyBindParams
    Steven Davelaar Employee ACE
    Currently Being Moderated
    Stephen,

    I looked again, I was wrong, the log level for this specific message is "severe".
    That might be a bit high, but the question is how come you don't pass in any params?

    The param values might be null, but of there are no params at all, the method shouldn't be called.
    Can you check the task flow for a managed bean that uses the QueryBindParams class and see how the params are configured?

    Steven Davelaar,
    JHeadstart team.
  • 4. Re: No query Bind parameters passed into applyBindParams
    Stephen J. Journeyer
    Currently Being Moderated
    Hi Steven,
    all of these are domains in JHS (upgraded to 11.1.13 from 10), used for dropDownList items, so I'm pulling them from the AppService-Domains-beans.xml file. There are several that are throwing the same error, all of them are nested lists (they depend on the value in another dropdown list). All of them have roughly the same managed-bean definition. We do have plans to change these over to adf-model choicelists instead, so this may become a moot issue, but that could be a couple of months out.

    <managed-bean id="__1284">
    <managed-bean-name id="__1285">MyLookupQueryBindParamsRowSpecific</managed-bean-name>
    <managed-bean-class id="__1286">oracle.jheadstart.controller.jsf.bean.DynamicListItemsBean</managed-bean-class>
    <managed-bean-scope id="__1287">request</managed-bean-scope>
    <managed-property id="__1288">
    <property-name id="__1289">applicationModule</property-name>
    <value id="__1290">#{data.AppServiceDataControl.dataProvider}</value>
    </managed-property>
    <managed-property id="__1291">
    <property-name id="__1292">dataCollection</property-name>
    <value id="__1293">MyLookup1</value>
    </managed-property>
    <managed-property id="__1294">
    <property-name id="__1295">valueAttribute</property-name>
    <value id="__1296">InternalValue</value>
    </managed-property>
    <managed-property id="__1297">
    <property-name id="__1298">meaningAttribute</property-name>
    <value id="__1299">DisplayValue</value>
    </managed-property>
    <managed-property id="__1300">
    <property-name id="__1301">namedParamDefs</property-name>
    <map-entries id="__1302">
    <map-entry id="__1303">
    <key id="__1304">code_set</key>
    <value id="__1305">#{'#{row.RecordType}'}</value>
    </map-entry>
    </map-entries>
    </managed-property>
    </managed-bean>
  • 5. Re: No query Bind parameters passed into applyBindParams
    Stephen J. Journeyer
    Currently Being Moderated
    Actually, come to think of it, this could be a data issue. We have records in the database that were imported from legacy systems and they do not have values that match anything in the code set for the parent dropdown, causing the parent dropdown to display as blank. Would that cause the child dropdown to not get it's appropriate bind parameter. If so, this will be fixed in the next few weeks as we are planning a data audit and update on the legacy records.
  • 6. Re: No query Bind parameters passed into applyBindParams
    Steven Davelaar Employee ACE
    Currently Being Moderated
    Stephen,

    The log message can't be a data issue.

    In the managed bean the namedParamDefs proeprty is defined as follows:

    <property-name id="__1301">namedParamDefs</property-name>
    <map-entries id="__1302">
    <map-entry id="__1303">
    <key id="__1304">code_set</key>
    <value id="__1305">#{'#{row.RecordType}'}</value>
    </map-entry>
    </map-entries>
    </managed-property>

    Then, in the page def the applyBindParams method references this namedParamDefs property, so even if #{'#{row.RecordType}'} evaluates to null, the hashmap itself is not hull.

    Anyway, the easiest way to prevent the log error is to override the method in your app module, and only call super when the arguments hash map is not null.

    Steven Davelaar,
    Jheadstart Team.

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points