Bug: ADF BC VO bind variable attr editor control hints

Hi JDev team
Under JDev 11g TP, for an ADF BC VO "existing" bind variable in the VO editor, if you double click on the variable, and in the bind variable editor change any of the control hints, press ok, on returning to the bind variable control hints in the editor, your changes have disappeared.
Regards,
CM.

Hi ,
I like to fill the date properties of a data variable what do I need to do tow make it work , do I need to edit the vo.xml or do I make a resourcebundle
thanks

Similar Messages

ADF - ViewObject (with Bind Variable) Bind to Table- JDeveloper 10.1.3 EA

Hi all,
1.- This is the situation:
In JDeveloper 10g 10.1.3 EA I have two JSP JSF Pages with bind automatically coponents (backing bean).
- In the first page I can select a value from a list. Then, when I press the "Accept" ADF Command Button, the selected value is stored in a property called "rutEntidad" of a Session Managed Bean and the Flow Control is passed to the second page.
- In the second page I have an ADF Table (called tablePolizas) bind to a ViewObject (I drop the ViewObject from the Data Control Palette to the Page - ADF Read-Only Table ). The ViewObject has a Bind Variable called RUT_ENTIDAD. When this page is loaded, value in the rutEntidad property of Session Managed Bean is passed to the ViewObject in order the ADF Table show filtered data . Also in this page there is a "back" ADF Command Button to the first page. The filter mechanism is performed in the getTablePolizas method in the backing bean of the second page, like this:
//**** The backing bean of the second page *****
package cl.bicevida.view.backing;
public class CrearUsuario {
private CoreTable tablePolizas;
public CoreTable getTablePolizas() {
DCBindingContainer dcbc;
DCControlBinding cb;
String rutEntidad;
FacesContext ctx =FacesContext.getCurrentInstance();
ValueBinding vb =
ctx.getApplication().createValueBinding("#{SessionManager.rutEntidad}");
rutEntidad = vb.getValue(ctx).toString();
dcbc = this.getBindingContainer();
cb = dcbc.findCtrlBinding("VoPolizasAsociadasEntidadExterna1");
ViewObject vo = cb.getViewObject();
vo.setNamedWhereClauseParam("RUT_ENTIDAD", rutEntidad);
vo.executeQuery();
return tablePolizas;
2.- And this is the problem:
The first time all works fine... then I press the "back" ADF Command Button to the first page (and NOT the back button of the browser). The second time, if the numbers of rows returned by the ViewObject is different than the first time, the application throws this message (but not crash):
validation - JBO-29000: Unexpected exception caught: oracle.jbo.JboException, msg=JBO-35007: Row currency has changed since the user interface was rendered. The expected row key was oracle.jbo.Key[1 ]
validation - JBO-35007: Row currency has changed since the user interface was rendered. The expected row key was oracle.jbo.Key[1 ]
Well, I had read the "Generic Approach for Back-Button-Friendly Web Rowset Paging" article of Steve Muench in http://www.oracle.com/technology/products/jdev/tips/muench/paging/index.html
but I think here have another problem.
3.- The questions:
Which is the cause of this problem?
How I can solve it?
What another way I can programmatic pass a parameter to a ViewObject connected to a table?
Thanks!!!

Another thing: the used strategy to obtain a binding container is explained by Steve Muench http://www.oracle.com/technology/products/jdev/tips/muench/1013eabinding/index.html:
Next, you can use JDeveloper's Overview tab of the faces-config.xml file editor to configure a managed property. Define the managed property name as bindingContainer to match the property in your bean, and set the class to the fully-qualified name of the DCBindingContainer class. You can use the (Browse...) button to quickly locate the class using the new JDeveloper 10.1.3 class browser. Just type in the first few letters of the DCBindingContainer name, and then select the class. Edit the new managed property and set its Value to the JSF EL expression: #{bindings}.
************************

OBIEE Integration with ADF - Reports with bind variables

Hi,
I've managed to integrate obiee with ADF by following the steps described in:
http://www.oracle.com/technetwork/middleware/bi-publisher/adf-bip-ucm-integration-179699.pdf
This is all fine and all but what about reports with complex queries where bind variables are needed?
In short I need to send specific values from ADF application as parameters to the query of the report before building it, then create it and download the file as pdf.
I don't have problems with building the file and downloading it when the query in the report has no bind variables, but when it does I do not know how to send them to the report.
I can't seem to find such an implementation or example anywhere and I am stuck.
Could anyone please point me in the right direction, eighter by providing a solution, or a link to such an example?
Thank you!
P.S.
I'm using OBIEE 11.1.1.6.0 and JDeveloper 11.1.2.1.0
Mihai Cornean
Edited by: 885382 on Apr 11, 2013 11:10 PM

Hi,
try the BI Publisher forum for question towards this product BI Publisher
Frank

ADF BC / Why bind variables are mandatory in the sql query

I got this error during view object excecution in the component browser :
(oracle.jbo.SQLStmtException) JBO-27122: Erreur SQL lors de la préparation d'une instruction. Instruction : SELECT * FROM (Select distinct(socialgroup.socialgroup_i) from socialgroup, socialgroupmember, lodgingallocation, lodge
where socialgroup.socialgroup_i = socialgroupmember.socialgroup_i and socialgroupmember.t_socialgrouprole_i = t_rolegroup_ipar.fgetflextypologyclassitem_i(t_rolegroup_ipar.fisbeneficiary) and socialgroupmember.datefrom <= :DateTo and nvl(socialgroupmember.dateto, :DateFrom) >= :DateFrom and socialgroupmember.requester_i = lodgingallocation.requester_i and lodgingallocation.datefrom <= :DateTo and nvl(lodgingAllocation.DateTo, :DateFrom) >= :DateFrom and lodgingallocation.lodge_i = lodge.lodge_i) QRSLT ORDER BY "SOCIALGROUP_I"
----- LEVEL 1: DETAIL 0-----
(java.sql.SQLException) Tentative de définition d'un nom de paramètre qui ne se trouve pas dans le SQL: T_SICategory_I
The bind variables T_SICategory_I is not yet use in the sql query but will be used later so i defined it for the view object.
Is it a reason that the run time check this ? It would be more convenient to set the bind variables early when defining the view object and add them later during the development iteration.

Design-time defined named bind variables can be marked as required, or not.
This is decided by the use in the where clause or in view criteria. In my case the bind variable was not used in where clause neither in view criteria and that causes the error.
May be i would be nice to add a check box (a flag) that enable or disable the bind variables for this checking so we will be able to let it defined even we removed some part of the query corresponding to the corresponding restriction or we defined it earlier for a part of the query that is not yet defined.
In my current case i fully defined the bind variables but would refine my query later ... in that cause i would have to remove this bind variable and loose all the definitions to run this view object.
sorry for my english ...

ADF 11g:set bind variable

Hi All,
Requirement is to set the value of bind variable of the recursive view object(DynamicTreeMenuVO1) on which my af:tree is based at run time. The value of the bind variable is coming from DynamicMenuVO1Iterator view object at run time("#{rows.displayVal}"), when I am iterating the DynamicMenuVO1Iterator using af:forEach.
Following code is there on my jspx page:-
<af:panelAccordion id="acc" discloseMany="false" discloseNone="false">
<af:forEach items="#{data.view_DynamicGalleryTreePageDef.DynamicMenuVO1Iterator.allRowsInRange}" var="rows">
<af:showDetailItem text="#{rows.displayVal}" id="sdi1">
<af:tree value="#{bindings.DynamicTreeMenuVO1.treeModel}" var="node"
selectionListener="#{bindings.DynamicTreeMenuVO1.treeModel.makeCurrent}"
rowSelection="single" id="t1">
<f:facet name="nodeStamp">
<af:outputText value="#{node}" id="ot1"/>
</f:facet>
</af:tree>
</af:showDetailItem>
</af:forEach>
</af:panelAccordion>
Unable to find how to pass the value #{rows.displayVal} to the bind variable of DynamicTreeMenuVO1 at run time. Please help
Thanks,
Vikram

Will using the groovy expression to set the bind variable value by referencing desired attributes in DynamicMenuVO1Iterator work?
Can any one can give me the grovvy expression to "*Referencing attributes in other view objects*".
Any inputs please..........................
Edited by: Vikram K on Feb 25, 2010 7:23 PM

ADF View Accessor Validation with Bind Variable

Hi
I need to solve the following requirement using a view accessors and bind variables;
1. User can select a value for a attribute from LOV which is unfiltered.
2. User can manually edit code into the same attribute as in 1 above, which needs to be validated.
As the data set for the attribute is large, I need to be able to validate 2 using a query with a where clause.
My approach has been;
1. I have a view object for the source lookup table, ProductVO.
2. I have created a view criteria on ProductVO that accepts a bind variable, pProductCode.
3. On my OrderEO I have a attribute, productCode.
4. I create a new view accesor on the OrderEO using the view criteria created in point 2.
5. I have lft the bind variable parameter blank, as I need to be able to dynamically pass a product code at run time.
6. On my OrderVO for the productCode attribute, I have create a LOV, based on the ProductVO. This will ensure that the user can view and search all products if needed.
What I am not getting working;
1. How can I pass the attribute value to the view accessor at runtime when the value is manually captured.
2. Ensure that if a value is selected from the LOV, that the view accessor validation does not get invoked.
What I have tried to solve point 1;
1. I created a validator on the productCode attribute on the OrderEO as a list validator using the view accessor as my list. I am not sure how to get the bind variable populated. Leaving out the bind variable, I assume, would cause the value to be validated against all my products.
2. I then tried using a method validator and passing in the productCode value and querying the view accessor.
3. I have not yet tried using Key Exists, is this maybe the missing link/trick?
All help will be considered a early christmas gift!!

Hi
I have found that when using validation type Key Exists and the VO is in the local application, then the bind variable is available in the Create Validation wizard. When I try and create a validator on a VO that is core to all my applications, then I put that VO into an ADF library, the bind variable parameter is not available for mapping to my entity object attribute, even though I can select the VO to create a view accessor from the ADF library.
Possible bug?

BC4J bug with "bind variables" JBO-27122 ORA-01008

I think we are found a BUG using BC4J with bind variables in a view object.
If the bind variable appear in the WHERE condition two or more times at
the beginning of the query the above error occur.
oracle.jbo.SQLStmtException: JBO-27122: SQL error during statement preparation. Statement:
SELECT Emp.EMPNO,Emp.ENAME,Emp.JOB,Emp.MGR,Emp.HIREDATE,Emp.SAL,Emp.COMM, Emp.DEPTNO
FROM SCOTT.EMP Emp
WHERE :1 <=10000 and :1 <= sal and :2=20
java.sql.SQLException: ORA-01008: not all variables bound
Otherwise if bind variable apper two or more times, but not together
like this sample:
WHERE :1 <=10000 and :2=20 and :1 <= sal
the error not occur.
We prove this with:
JDeveloper 9.0.5.2 (build 1618)Business Components Version 9.0.5.16.0
JDeveloper 9.0.5.0 (build 1375)Business Components Version 9.0.5.13.52
I looking for a patch! or acceptable workaround.
Tx for your help!
diego.
/* the cliente app */
ApplicationModule am = Configuration.createRootApplicationModule("business_tier.AppModule","AppModuleLocal");
ViewObject vo = am.findViewObject("EmpView");
vo.setWhereClauseParam(0,"100");
vo.setWhereClauseParam(1,"20");
Row emp = vo.first();

This is a known bug (1326006). The workaround is to use:
vo.setWhereClauseParam(0,"100");
vo.setWhereClauseParam(1,"20");
vo.setWhereClauseParam(2,"20");
Hope this helps,
Lynn
Java Tools Team

Label of attribute when used as View Criteria item with Bind Variable

I've a VO attribute used in a named search with this requirement:
The attribute provides has an optional View Criteria item that has a bind variable operand. The bind variable is in the WHERE clause. The attribute has an LOV. The choice list for the specified View Criteria item should display the label "Effective Release". However, in all other contexts, including the search results table and the dropdowns the user can optionally add in an advanced search, the label displayed for the attribute must say "Release".
In other words, the default label for the attribute should be "Release" in all but one context - which is that when the dropdown list for the viewCriteria item using the bind variable is displayed, the label should say "Effective Release".
Note that if the user moves to Advanced Search and selects adds the attribute as a search criteria, this latter usage should be labeled as "Release". (in this case, in other words, the dropdown that displays by default and has the bind variable operand is labelled "Effective Release", the one the user added in advance search is labelled "Release")
here is the View Criteria item source xml:
      <ViewCriteriaItem
        Name="ReleaseId1"
        ViewAttribute="ReleaseId1"
        Operator="="
        Conjunction="AND"
        Value=":v_ReleaseId"
        GenerateIsNullClauseForBindVars="false"
        ValidateBindVars="true"
        IsBindVarValue="true"
        Required="Required"/>I've experimented by putting "Effective Release" as the label for the bind variable as below. However, ADF does not use that value to display, it defers to the attribute value:
<Variable
    Name="v_ReleaseId"
    Kind="viewcriteria"
    Type="oracle.jbo.domain.Number">
    <Properties>
      <SchemaBasedProperties>
        <LABEL
          ResId="EFFECTIVE_RELEASE_LOV"/>
      </SchemaBasedProperties>
    </Properties>
</Variable>The reason for the requirement, if it matters, is that the View Criteria item with the bind variable ("Effective Release" queries a range of values using the analytic function rank(); the bind variable is in the WHERE clause. Otherwise, the dropdown that can be added in advanced search ("Release") looks for exact matches on the attribute value. So since the search functionality is different, the label should be different.
Am using 11g.
Thanks for your help.

Hi
I have found that when using validation type Key Exists and the VO is in the local application, then the bind variable is available in the Create Validation wizard. When I try and create a validator on a VO that is core to all my applications, then I put that VO into an ADF library, the bind variable parameter is not available for mapping to my entity object attribute, even though I can select the VO to create a view accessor from the ADF library.
Possible bug?

Bind variables in double quotation marks are not recognized

Hello,
when I do "Execute Statement" (F9) in the SQL Worksheet and the statement incorporates a bind variable in the form :"Some Variable", i.e. variable name is in double quotation marks, I will get an error message "ORA-01008: not all variables bound". No prompt for entering the bind variables is displayed. Our application uses this kind of bind variables only and it is quite time consuming to change all the bind variable names before executing it especially when bind variable names contain spaces. Is there an option to enable recognition of this kind of bind variables? If not I would like to see this annoying issue fixed.
I am running Oracle SQL Developer 1.5.1 build MAIN-5440.
I am connecting from the Windows XP SP2 (32bit) box to Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 (64bit) using Basic connection type.

Hi mc1100 ,
Bug logged: Bug No: 7323289 F9 BIND VARIABLES SHOULD BE ABLE TO BE IN DOUBLE QUOTES AND HAVE SPACES.
-Turloch

BUG ? : ADF creating extra VO instance using bind variables in a LOV query

ADF 11.1.1.1.0
After "playing around" with bind variables Setting bind variables in view objects for LOV I've come across something strange that I've reproduce using the HR schema and tables Employees and Departments. Its a bit long but here goes :
Using the HR schema tables departments and employeesI'm trying to create a LOV (selectOneChoice) for the
employee department, the LOV having a bind variable that limits the values returned in this case returning only DepartmentId = 50
I've create a VO lovDepartment (not based on an EO) with the following query :
SELECT Departments.DEPARTMENT_ID,
       Departments.DEPARTMENT_NAME,
       Departments.MANAGER_ID,
       Departments.LOCATION_ID
FROM DEPARTMENTS Departments
where DEPARTMENT_ID = :pDeptIdA LOV has been defined on the DepartmentId attribute of the EmployeesView.
The lovDepartmentImpl overrides the executeQueryForCollection to set the bind variable value.
    @Override
    protected void executeQueryForCollection(Object object, Object[] object2,
                                             int i) {
        setNamedWhereClauseParam("pDeptId", "50");
        super.executeQueryForCollection(object, object2, i);
    }When using an ADF form to create a new employee the DepartmentId lov is empty.
Enabling SQL tracing shows the following :
[370] _LOCAL_VIEW_USAGE_model_EmployeesView_lovDepartment1_0 ViewRowSetImpl.doSetWhereClause(-1, pDeptId, null)
[371] _LOCAL_VIEW_USAGE_model_EmployeesView_lovDepartment1_0 ViewRowSetImpl.execute caused params to be "un"changed
[372] Column count: 4
[373] _LOCAL_VIEW_USAGE_model_EmployeesView_lovDepartment1_0 ViewRowSetImpl.doSetWhereClause(-1, pDeptId, null)
[374] _LOCAL_VIEW_USAGE_model_EmployeesView_lovDepartment1 ViewRowSetImpl.setNamedWhereClauseParam(pDeptId, 50)
[375] ViewObject: _LOCAL_VIEW_USAGE_model_EmployeesView_lovDepartment1 Created new QUERY statement
[376] _LOCAL_VIEW_USAGE_model_EmployeesView_lovDepartment1>#q computed SQLStmtBufLen: 235, actual=195, storing=225
[377] SELECT Departments.DEPARTMENT_ID,
       Departments.DEPARTMENT_NAME,
       Departments.MANAGER_ID,
       Departments.LOCATION_ID
FROM DEPARTMENTS Departments
where DEPARTMENT_ID = :pDeptId
[378] Bind params for ViewObject: _LOCAL_VIEW_USAGE_model_EmployeesView_lovDepartment1
[379] For RowSet : _LOCAL_VIEW_USAGE_model_EmployeesView_lovDepartment1_0
[380] Binding null of type 12 for "pDeptId"
[381] No Resource Bundle found but null value id:LOV_DepartmentId_LOVUIHints_NullValueId is defined in an ListBinding Definition.It would seem that 2 lovDepartment instances are used one at line 370 LOCALVIEW_USAGE_model_EmployeesView_lovDepartment1_0
and one at line 374 LOCALVIEW_USAGE_model_EmployeesView_lovDepartment1
The one at line 374 LOCALVIEW_USAGE_model_EmployeesView_lovDepartment1 gets the variable bound at line 374
however LOCALVIEW_USAGE_model_EmployeesView_lovDepartment1_0 gets a null value and would explain the empty LOV
Can anybody explain what is happening here ? (and how to use bind variables in LOV queries)
Regards
Paul
(bump)
Edited by: Paul (MITsa) on Jul 14, 2009 10:46 AM
I've now tried all types of LOV from ChoiceList to Radio groupe by testing the application module - none of them work.....
Edited by: Paul (MITsa) on 14-Jul-2009 22:52

when you rinvoke executeQueryForCollection the bind variables are allready set and they exist in Object[] object2 method parameters.
in order to change them you need something like:
private void changeGenericBindVariable(Object[] params, String paramName, Object paramValue) {
for (int i = 0; i < params.length; i++) {
if (paramName.equals(((Object[])params)[0].toString()))
((Object[])params[i])[1] = paramValue;
* executeQueryForCollection - overridden for custom java data source support.
protected void executeQueryForCollection(Object qc, Object[] params,
int noUserParams) {
changeGenericBindVariable(params, "pDeptId", "50")
super.executeQueryForCollection(object, object2, i);
But its better to set bind variables before you executeQueryForCollection. like when you invoke LOV.
For cascading LOVs and the problems i have check:
[http://adfbugs.blogspot.com/2009/07/jdeveloper-11-r1-cascading-lov-bugs.html]

View with Bind Variable and ADF table

Hi all,
Please note what i have noticed. I created a view with a bind parameter, overriden the prepareSession of my Application Module to set the bind parameter and execute the query. I then created a simple jsf page and included the view as an adf read-only table. When i run the page, the prepareSession is called, sets the bind parameter, however the selected record of the table is always the second record (Not the first record).
This behaviour can be reproduced with the HR schema. Please follow the below instructions for reproducing the problem.
1. Create a Fusion Web Application (ADF).
2. Create business components from tables.
3. Create a new connection with the HR schema.
4. Import the Departments table as an entity and then click finish.
5. Create a view based on the Departments entity.
6. Modify the Query to include a where clause (where DDepartmentsEO.DEPARTMENT_NAME LIKE :BindParam)
7. Provide an order by clause (DepartmentsEO.DEPARTMENT_ID DESC)
8. Creata a bind variable named "BindParam" of type string.
9. Create an Application Module and include the view object.
10. Open the Application Module Class and override the prepareSession method
11. include the following code after super.prepareSession(session):
ViewObject myView = this.getDepartments1();
myView.setNamedWhereClauseParam("BindParam", "%");
myView.executeQuery();
12. Create a jsf page
13. Drag the view object on the page as an adf read-only table, selecting the Row Selection, Sorting and Filtering
14. Run the page.
You will see that instead of the first record being selected, the second record in the table is selected.
Can anyone please help me?
Thank you

First of all i would like to thank you for replying to my thread.
Secondly, i would like to inform you that the example that i have provided is just for REPRODUCTION purposes.
The real scenario has to do with setting the where clause with the authenticated user so that the view will query for data only associated with the authenticated user.
The only way to overcome this behaviour is to include a view action (namedWhereClause in the page definition)
However, this is not how i want to implement this. This was working properly in 10g

How to populate bind variable in view objects where clause in ADF faces

I've got a page with 2 input items.
The user manually enters the first value.
On the second input item I have created a LOV for the item which opens in a popup. How do I restrict the data returned in the LOV using the value entered in the first input item. I have created a bind variable and have included it in the where clause for the view object but how do I populated it.

Here is an example:
Using the HR schema with the EMPLOYEES and DEPARTMENTS tables.
Example is using ADF BC and created an EMPLOYEES entity with an updateable view object for page,
and created a DEPARTMENTS view as a lookup
(SQL: select department_id, department_name from departments where department_name = :DeptName)
1: add method to the backing bean to filter the LOV
public void getTextValueToFilterLOV(ValueChangeEvent valueChangeEvent) {
Object value_from_form = valueChangeEvent.getNewValue();
FacesContext fctx = FacesContext.getCurrentInstance();
Application fapp = fctx.getApplication();
JUFormBinding formBinding = (JUFormBinding)fapp.createValueBinding("#{bindings}").getValue(fctx);
DCIteratorBinding dcBinding = (DCIteratorBinding)formBinding.get("DeptLOVIterator");
ViewObject vo = dcBinding.getViewObject();
vo.setNamedWhereClauseParam("DeptName",value_from_form);
vo.executeQuery();
2. add valueChangeListener to the inputText on the page with an id and autoSubmit="true"
<af:inputText value="#{bindings.LastName.inputValue}" label="#{bindings.LastName.label}" binding="#{backing_DeptForm.inputText3}"
id="inputText3"
autoSubmit="true"
valueChangeListener="#{backing_DeptForm.getTextValueToFilterLOV}">
</af:inputText>
3. reference the LOV with the id name on the partialTriggers property
<af:selectOneChoice value="#{bindings.EmployeesUpdView1DepartmentId.inputValue}"
label="#{bindings.EmployeesUpdView1DepartmentId.label}" binding="#{backing_DeptForm.selectOneChoice1}"
id="selectOneChoice1"
partialTriggers="inputText3">
<f:selectItems value="#{bindings.EmployeesUpdView1DepartmentId.items}"
binding="#{backing_DeptForm.selectItems1}"
id="selectItems1"/>
</af:selectOneChoice>
Summary:
When you entered a text (LastName), that value is passed into the backing bean method.
The Bean method code will find the LOV Iterator and put the value into the bind variable.
Cheers,
Jim

Update_Task results in ORA-01006: bind variable does not exist - bug?

Hi,
I have successfuly created projects/tasks, and updated projects. However, when I tried to call pa_project_pub.update_task, I get an error
U(nexpected):
PROCEDURE_NAME update_one_task
PKG_NAME PA_PROJECT_PVT
FND FND_AS_UNEXPECTED_ERROR
ERROR_TEXT ORA-01006: bind variable does not exist
As far as I can see, this must be a bug, because the API must have created an excecute immediate/dbms_sql statement with at least one extra bind variable (i.e. execute '... :a, :b' using a, b, c)
I've tried with different combinations of arguments to the API, all resulting in the same error:
The id's and data are taken from a an already created project/task in my apps-instance:
pa_project_pub.update_task(
p_api_version_number => 1.0
,p_commit => xxpa_opop2pa_interface_utils.g_FALSE
,p_msg_count => l_msg_count
,p_msg_data => l_msg_data
,p_return_status => l_return_status
,p_pm_product_code => l_pm_product_code
,p_pm_project_reference => '100394'
,p_pm_task_reference => 'add_task_1.0'
-- ,p_ref_task_id => ''
,p_task_number => 4
-- ,p_pa_task_id => '19079'
,p_task_name => 'add_task_1.0'
,p_long_task_name => 'p_task_name'
,p_task_start_date => p_start_date
,p_task_completion_date => p_completion_date
,p_task_description => 'update-task:'||p_description
,p_out_pm_task_reference => l_out_pm_task_reference
,p_out_pa_task_id => p_task_id_out
Am I missing anything, or this really must be a bug in the API?
Does anyone have any other idea?
I have looked at the API implementation, and found a use of dbms_sql, a long code constructing a statement then binding variables in if-then clauses.
Regards,
ps: ->
system info
Database Server
RDBMS : 11.1.0.6.0
Oracle Applications : 12.0.6
System Date : 11-MAY-2009 10:41:50
Forms Server
Current Form
Form Application : Application Object Library
Form Name : FNDPOMPO
Form Version : 12.0.2
Form Last Modified : $Date: 2006/03/23 13:54 $
Forms
APPSTAND : 12.0.6.12000000.3
FNDPOMPO : 12.0.2
FNDSCSGN : 12.0.14.12000000.3
Form Menus
FNDMENU : 12.0.2
Forms PL/SQL
APPCORE : 12.0.21.12000000.13
CUSTOM : 12.0.0
FNDSQF : 12.0.3
GHR : 12.0.22.12000000.26
GLOBE : 12.0.62.12000000.13
GMS : 12.0.42.12000000.11
IGILUTIL2 : 12.0.24.12000000.3
IGILUTIL : 12.0.1.12000000.3
OPM : 12.0.7.12000000.2
PQH_GEN : 12.0.7
PSA : 12.0.17
PSAC : 12.0.4.12000000.2
PSB : 12.0.2
VERT1 : 12.0.0
VERT2 : 12.0.0
VERT3 : 12.0.0
VERT4 : 12.0.0
VERT5 : 12.0.0
VERT : 12.0.0
**********************

Hello,
This issue is fixed in the bug 4692368. So you can get a patch from Oracle.
Hope this helps !
Thanks,
Sathish
www.projectsaccounting.com

ManagedBean and Bind Variables in ADF applications

Situation with Target Unreachable, 'TestBean'.
ManagedBean: TestBean, parameter objectId
ViewObject: sql-based: select * from someobject where id = :objectId
Unbounded taskflow with the one page: Start.jspx
Bounded TaskFlow "TestTaskFlow" with pagefragments: ButtonView.jsff and ObjectCard.jspx (as dialog).
On the ButtonView there is a button with: action="dialog:OBJECT", actionListener.
ActionListener handler I create by using the JDev Wizard. And the record was appeared in the adfc-config.xml. Is it correct? since the button is in the Taskflow. So in the taskflow there is no records about managed beans. May be it is Ok.
Than, on the ObjectCard.jspx add ExecuteWithParams VO method, and set bind variable from the managedbean attribute. and get an error:
SEVERE: Server Exception during PPR, #1
javax.servlet.ServletException: Target Unreachable, 'TestBean' returned null
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:270)
     at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
     at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
     at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:292)
     at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:181)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:279)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._invokeDoFilter(TrinidadFilterImpl.java:239)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:196)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:139)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at oracle.security.jps.wls.JpsWlsFilter.doFilter(JpsWlsFilter.java:102)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:65)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:42)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3496)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(Unknown Source)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2180)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2086)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1406)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
Caused by: javax.faces.el.EvaluationException: Target Unreachable, 'TestBean' returned null
     at org.apache.myfaces.trinidadinternal.taglib.util.MethodExpressionMethodBinding.invoke(MethodExpressionMethodBinding.java:58)
     at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcastToMethodBinding(UIXComponentBase.java:1227)
     at org.apache.myfaces.trinidad.component.UIXCommand.broadcast(UIXCommand.java:183)
     at oracle.adf.view.rich.component.fragment.UIXRegion.broadcast(UIXRegion.java:142)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:754)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:282)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:175)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
     ... 27 more
Than I add this managedbean in the Taskflow too. There is no exception, but bind variables has not been set.

Hi,
most likely the managed bean got created in the adfc-config.xml file. If then it has a scope of pageFlowsScope, then it cannot be found. Move the managed bean or use it with a scope of requestScope or backingBeanScope
Frank

BUG: Binding Variables, Position being reset to 0

IDE:
Studio Edition Version 10.1.3.0.4 (SU4)
Build JDEVADF_10.1.3_NT_060125.0900.3673
DB:
10g R2
(We have to be able to run our queries against MS SQL and Oracle. Using Oracle Binding is not an option)
SQL Flavor: SQL92
Data Type: Java
Scenario:
Working with View Object Editor. Opening a View Object for edit.
Symptom:
1. While working with bind variables the selected variable and the Bind Positions field does not stay in sync. When moving from one variable to the next the Bind Positions field remains on the last entered value for all variables.
2. Opening the editor resets all Bind Position fields to 0. This happens even if the Bind Variables node is not selected during the edit.
Our work-around:
We enter all bind varialbes, leaving all Bind Position at 0. Add all where clause (query builder does not support '?' by the way) manually in the same order (order not critical) and save view object. We then open the xml file outside of JDeveloper and add the correct Bind Positions.
Now, with all that said we could have missed something small that would correct this issue, but using the editor does present issues with the Bind Positions. For the mean time we will continue to edit the XML files outside of JDeveloper.
Thanks, Peter

This error didn't really have to do with the SQL Statement, rather using the editor to create bind variables. We have to use SQL92 with Java data typing. When using the editor the bind variables positioning does not stay in sync with listbox above resetting or setting the positions to 0.

Bug: ADF BC VO bind variable attr editor control hints

Similar Messages

Maybe you are looking for