[Solved] Named Bind Variables at Runtime - SQL WHERE clause issue

Question

Hey 'all,
I've been having this issue today with a Search page using Named Bind Variables at Runtime for the search parameters for the WHERE clause in the view objects SQL.
I've got everything working except for a clearing method which I've created so that the user can clear the current WHERE clause from the SQL statment and set it as 1=2 (so that it doesn't do a blind query on load).
The method can clear and set the WHERE clause to 1=2 only when there is already one there.
Below are the methods: (located in my view object class)
public void findInvoiceById(Number invoiceId){
    setWhereClause("invoice_id = :P_INVOICE_ID");
    defineNamedWhereClauseParam("P_INVOICE_ID",null,null);
    setNamedWhereClauseParam("P_INVOICE_ID",invoiceId);
    executeQuery();
public void clearCriteria(){
    setWhereClause("1=2");
    removeNamedWhereClauseParam("P_INVOICE_ID");
    executeQuery();
}The error which I get is the following - this happens when the button is pressed twice in a row, or when no query has been passed previously.
1. JBO-29000: Unexpected exception caught: oracle.jbo.NoDefException, msg=JBO-25058: Definition P_INVOICE_ID of type Variable not found in SupplierInvoicesView1
2. JBO-25058: Definition P_INVOICE_ID of type Variable not found in SupplierInvoicesView1
Any help with this would be greatly appreciated!
Cheers,

Answer 1

Hi Bonnie,
we have it working ok, but still feel that there is room for improvement in the design.
For us the key factors are:
Pages based on the same view object that can be queried multiple ways.
We don't want to put design time bind variables in because it limits the use of the VO
We don't wan't multiple VO's with different where clauses.
The page is displaying the same table columns and fields, but the where clause must be dynamic.
We only want to query on the search field entered (some of our tables are massive)
TopLink named queries are really what we are after, but we don't want to forgo all the other ADF BC functionality. The only examples of ViewCriteria in the developer guide had literals in the where clause and no bind variables. The View Criteria may still be an option, but it appeared quite complex compaired to directly adding and removing bind variables at runtime.
a couple of footnotes:
the following methods are used to clear the runtime variables prior to reusing the VO (thanks to John Stegman for the pointer on the exception handler):
    public void clearBindVariable(String bindVariableName){
        try
            removeNamedWhereClauseParam(bindVariableName);
        catch (NoDefException e)
    public void clearBindVariables(){
        clearBindVariable("P_INVOICE_ID");
        clearBindVariable("P_INVOICE_NUM");
        clearBindVariable("P_SUPPLIER_NAME");
        clearBindVariable("P_INVOICE_DATE_FROM");
        clearBindVariable("P_INVOICE_DATE_TO");
        clearBindVariable("P_SUPPLIER_NUMBER");
    }We are using 1=1 and 1=2 in the where clause to supress blind querying. 1=2 is applied when ever we are not explicitely searching for something. We had a problem with using the refresh condition ${adfFacesContext.postback == true} which I posted about here:
executeQuery called twice using ${adfFacesContext.postback == true}
Would still gladly hear other ideas on a better reuse design.
regards,
Brenden