Cascaded LOV loose value when pooling disabled

Hi All,
I am using jdev 11.1.1.5
my scenario is i have search VO with transient attributes.Most of attribute are LOV using accessor.
Few of LOV are dependent on each other. When i am running by enabling pooling true.it is working fine.
But when pooling disabled, cascaded LOV are not persisting value in the VO. It is happening only for dependent LOVs . I am not sure why is it so.?
I am creating a new row of Search VO usng Create Method of VO operation.Should i try anything else?
Is anyone faces this issue earlier? any suggestion to handle this. All attribute are passivated and VO have key attribute.
Please suggest?

Hi Frank,
Well all LOV are transient attribute.Problem is this - Everything working with AMPooling enbaled.But when AMPool disabled then only attribute whose value are depend on other LOV are not persist or loose.
Yes they are marked passivate. and i also override afterRollback and beforeRollback in all ViewObjectImpl.java with commenting super call.
Seems , variable are setting by bind variable are not passivated the value. I am not sure, is it some strange behavior or i am doing anything wrong.
What you suggest to investigate further more on this?
Regards
Vinay

Similar Messages

Cascading LOV not working when the page is public

Hi ,
I have a cascading LOV in a tabular form which I have built using Denes Kubicek example from
http://apex.oracle.com/pls/otn/f?p=31517:176:2702932664861989:::::
Thanks to this wonderful examle I was able to make my cascading lov work.
However when I make the page public , the second lov(which is based on the first one) does not work.
Inorder to debug i changed get.get('XML') to get.get() and put an alert on it; to check if the select list string is being returned correctly by the application process - it returns null. The same alert returns the select list string when I put the authentication back on the page.
Also I noticed when the page is public the application item (TAB_CASCADING_ITEM) is not getting populated with the value of the first select list.
has anybody encountered the same issue ?
Appreciate any suggestions?
Thanks,
Dippy

One of the parameters in the htmldb_get is the page the process runs on. You should change that to the current page or make page 0 public as well.

How to pass value when inputbox disabled?

HI,
<h:inputText id="exdigits" value="#{dnRange.exchangeCode}" disabled="true"/>
I am enabling and disabling the checkboxes using java script. but even after I enable I could not get the
values in managed bean. how to do that?
Thanks,
Krishna

The 'disabled' value is not true in the next request.
Apparently you need readonly rather than disabled.

IviSwitch looses value when sending, "configure switch" configuration = TRUE

Hi all,
we are currently evaluating Teststand 4.1 with a keithley 3706 system switch multimeter.
After a first enthusiasm, thinking this tool together with the switch multimeter fits perfect our needs, real life seems some harder.
Between several other problems, we need to tell the device, that the channel "s1com1" and "s1com2" are configuration channels.
Configuring the teststand step : Edit IVI Switch Step -> IVI switching, Configure Switch : Channels "s1com1", Configuration = True
leads to two actions observable in Ni Spy:
GetAttributeViBoolean(...,"s1com1", _IS_CONFIGURATION_CHANNEL , VI_FALSE)
SetAttributeViBoolean(...,"s1com1", _IS_CONFIGURATION_CHANNEL , VI_FALSE)
manually calling this class functions from an interactive CVI fp works as expected (setting it to VI_TRUE)
Does anybody have any hint what we could do wrong? Currently we are just before writing wrappers in cvi and skipping all the wonderful IVIStep Types in teststand.
Looking forward to any feedback
David Clus
Solved!
Go to Solution.

David -
This might the same problem that we recently discovered in our internal testing. For the problem that we found, we will likely include our fix in an upcoming maintenance release. Can you verify whether the problem still occurs if you change your regional settings to English in the control panel? If the problem no longer occurs, can you use this as a workaround for now?
Message Edited by Scott Richardson on 10-06-2008 10:48 AM
Scott Richardson
National Instruments

Cascading LOV does not work when setting the value of the parent LOV with DA

Hello All,
Using APEX 4.2.2.
I have tow LOVs
Parent LOV item is: P50_TYPE
Child LOV item is : P50_PROJECT_ID
In other words in the attributes of the item P50_PROJECT_ID we have :
> Cascading LOV Parent Item(s): P50_TYPE
> Page Items to Submit: P50_TYPE
> List of values definition: something similar to:
Select * from mytable where type = :P50_TYPE
I use DA that execute JS code to set the value of the P50_TYPE item
something similar to:
> $('#P50_TYPE').val(2);
Having done this, the P50_PROJECT_ID item does not get refreshed, when the value of P50_TYPE is changed. Namely, P50_PROJECT_ID remains empty, unless end user manually changes the value of P50_TYPE.
Any help please ?
Regards,

Thanks Scott,
By the way, I remember reading a thread posted by you about Sumneva Drag & Drop Report Region plugin that was answered by Tom . But, I cannot find this plugin anywhere. Does not it supported in APEX 4.2 ? Is there any alternative out there ?
If you use it, and it works find with you, can you please send it to me on [email protected] ?
Regards,
Fateh

4.2.1 Bug: Current values of child cascading LOVs are LOST.

Hello, ApEx Team!
This bug affected 4.1.1 and 4.2.1 but with different behavior. It seems that someone was trying to fix it.
According to docs "whats new in 4.1" a value of refreshed child cascading lov is derived from default value settings of select list.
Please follow these steps to see the bug.l builder-work done for you here http://apex.oracle.com/pls/apex/f?p=14110:1
1.Create primary select list P1_SEL1.
Display null value: Yes
LOV definition:
    select 'aaa' name,'a' id
      from dual
     union all
    select 'bbb' name,'b' id
      from dual
     union all
    select 'ccc' name,'c' id
      from dual2.Create child select list P1_SEL2.
Cascading LOV Parent Item: P1_SEL1
Page Items to Submit: P1_SEL2 (I strongly believe that this item should be submitted automatically along with Parent Item)
Display Null Value: Yes
LOV definition:
    select 'aaa' name,'a' id
      from dual
     union all
    select 'bbb' name,'b' id
      from dual
     where :P1_SEL1 in ('b','c')
     union all
    select 'ccc' name,'c' id
      from dual
     where :P1_SEL1 in ('c')
Default: return :P1_SEL2;
Default Value Type: PL/SQL Function Body3.Run app. and manually change P1_SEL1 and P1_SEL2 to 'bbb'.
4.Manually change P1_SEL1 to 'ccc'.
h2.
In apex 4.1.1..
you see that P1_SEL2 is resetted to NULL automatically. The value of P1_SEL2 is LOST. Although I tell apex to submit P1_SEl2 value to set its session state, but the session state still remains NULL.
The session state of P1_SEL2 is always NULL and I have no idea how to set it as it is set in a browser at the moment of changing parent LOV P1_SEL1.
h2.
Now apex 4.2.1.
It seems this bug is fixed. Indeed it is NOT fixed.
To see this bug in 4.2.1 just...
5.Create a third child select list P1_SEL3 which depends on P1_SEL2.
Cascading LOV Parent Item: P1_SEL2
Page Items to Submit: P1_SEL3 (Again, I hope you will always submit current item automatically as you do for the parent item)
Display Null Value: Yes
LOV definition:
    select 'aaa' name,'a' id
      from dual
     union all
    select 'bbb' name,'b' id
      from dual
     where :P1_SEL2 in ('b','c')
     union all
    select 'ccc' name,'c' id
      from dual
     where :P1_SEL2 in ('c')
    Default: return :P1_SEL3;
    Default Value Type: PL/SQL Function Body6.Run app. again. Manually set P1_SEL1, P1_SEL2 and P1_SEL3 to 'bbb'.
7.Change P1_SEL1 to 'ccc' and see the bug:
1) P1_SEL2 is reset to NULL for just a short time and than restored to 'bbb'.
2) P2_SEL3 is reset to NULL. So the session state was NULL for this item at the moment of calculating default value. As a result the value of child cascading lov is LOST.
So this bug is still present in 4.2.1.
Can I hope to get workaround for this problem in 4.1 and 4.2?
Thank you,
Vladimir
Edited by: vgoncharov on 17.12.2012 19:37
Edited by: vgoncharov on 17.12.2012 22:45

Good to hear this is already being worked on.
When we tried to work around the "Automatic detection" bug - changing the "Application Language Derived From" to "Application Preference" or "Session" - we hit issue that some page processes were not firing in translated application.
See Page processes not firing in Translated applications
Jan

Cascading LOVs (APEX 4.1) problem, using in report does not set values

Hi,
i am using APEX 4.1.0.00.32 and i have a simple report as
SQL:*
SELECT * from region
WHERE region like '%'||P3_REGION||'%'
and country like '%'||P3_COUNTRY||'%'
and city like '%'||P3_CITY||'%'
Items:*
P3_REGION:
select distinct region as d, region as r from region
Display Null value: YES
Null display value: - select -
Null return value: +0+
P3_COUNTRY:
select distinct country as d, country as r from region where region = :P3_REGION
Display Null value: YES
Null display value: - select -
Null return value: +0+
Cascading LOV Parent Item(s): P3_REGION
P3_CITY:
+select distinct city as d, city as r from region where country = :P3_COUNTRY
Display Null value: YES
Null display value: - select -
Null return value: +0+
Cascading LOV Parent Item(s): P3_COUNTRY
The LOVs work fine and the correct values are displayed if cascading through them
So in the last step i want to filter the report with the values that were selected in the lovs. And this i get not working.
I tried to add a button with SUBMIT of the page. After choosing values in all LOVs and clicking the SUBMIT button the page submits, alle LOVs are cleared (with value - select -) and the report shows all rows.
I tried to change the button to "redirect to Page 3" and setting the values P3_REGION, P3_COUNTRY, P3_CITY to &P3_REGION., &P3_COUNTRY., &P3_CITY. but without success.
I tried to use the setting "Page Action when Value Changed" to "Submit" and/or "Redirect and set value" for all Item LOVs and/or only the last item LOV, but then the cascade of the LOVs does not work properly and the report does not change too.
I am confused as i don´t know what i can do until now. I think this should be an easy requirement to limit/filter the report with values in the LOVs.
Furthermore it should be possible to choose only the region LOV and then limit the report with that region (without choosing country and city)
Thanks in advance!

Hi Dan,
thank you for your answer. I have the solution now from Kleber_M, this works.
Dan McGhan wrote:
1. Use bind variables in my query. It would look something like:
SELECT *
FROM region
WHERE region LIKE '%'|| :P3_REGION ||'%'
AND country LIKE '%'|| :P3_COUNTRY ||'%'
AND city LIKE '%'|| :P3_CITY ||'%'
This was only a mistake when writing the post, i forgot the colon. I use bind variables of course.
2. Make sure you have a comma separated list of item names that the report depends on beneath the SQL Query where it says Page Items to Submit. This will make sure that the value of those items on the page are bound into session state prior to the query executing.I tried this, too, but without success...
3. Use Dynamic Actions to perform the refresh action when any of the three items changes. This would be both more performant and a better experience for the end user than a full page refresh.How can i do this. This sounds good, because when refreshing the page often some items oder actions are done that i don´t want to.
Regards,
Matze

APEX 4.0.2 Multi-selection on a cascade LOV select list only pass 1 value

Hello everyone,
I am struggling to make a cascading LOV select list has multi-selection.
On one report page.
I have 2 select list
The first one lists the court name (P4_COURT_NAME), the second one (P4_DEFENDANT) list all defendants who currently engaged in the court.
The problem is when I allow the defendant select list become multi-select, when it submit it only pass the first selected value.
So I create just a simple select list based one list of value, and make it allow multi-selection. When it submit, the normal select list can pass selected values properly, while the cascade LOV select list pass only the first selected value.
Please help if any of you have an idea why.
We use APEX 4.0.2.00.07, Oracle data version iis 11g
The some configuration settings I set for the P4_DEFENDANT IS
Value required: Yes
Page Action When value changed: None
Allow Multi Selection: Yes
Named LOV: --Select Named LOV-
Display Extra value : Yes
Display Null Value: Yes
Null Display Value: --Select—
Null return value:
Cascading LOV Parents Items: P4_COURT_NAME
Page Items to Submit: P4_DEFENDANT
Optimize refresh: YES
List of value definition
SELECT def.first_name || ' ' || def.surname || ' (PRN: ' || def.prn || ' )' as d, def.def_id as r
FROM defendant def INNER JOIN court_engagement ce
ON def.def_id = ce.defendant_id
WHERE (ce.date_joined_aodt_court IS NOT NULL
AND (ce.date_terminated IS NULL OR to_date(ce.date_terminated,'dd/mm/yyyy') > to_date(sysdate,'dd/mm/yyyy'))
AND UPPER(ce.court_name) LIKE UPPER(:P4_COURT_NAME)
AND ce.active = 1)Source Used: Only when current value in session state is null
Source Type: Static Assignment
Maintain session state: Per session
The rest is default.
Thanks in advance.
Ann

Hi Chintan,
The "Source used" for those items are "Always, replacing any value in the session state". To set them to "Only when current value in session state null" sounds a good solution to me.
However, a strange thing just happened - now I will not lose the values of the items after the page reloading, although I have changed nothing in the page in my application since I asked the question. I don't understand why all of a sudden the reloading doesn't make me lose changed values any more. Let me dig it tomorrow to see what I'll find.
Thanks so much for your help.
Christine

Apex 4 Cascading LOV's how to set a child LOV back to null return value

Hi,
My problem is I am using the new Dynamic Actions to implement Cascading LOV functionality in Apex 4 which means not having to submit the page to update child LOVs after parent LOV changes.
What I am finding is that when you change the parent LOV value then the child LOV (which has a null return value) is not defaulting to the null return value (in my case no selection should return -1) if its list is filtered to a different set of values which doesnt have a valid selection. The child LOV is left without a selection when I need it to default back to the null return value (-1, representing all values).
Also I was hoping to do this before the page is submitted so the filtering down the hierarchy of LOVs will work where the child is null (-1, meaning all values) and in turn its child LOV(s) will filter also from the null child value.
Any help would be much appreciated.
Thanks

Hi 804641,
I'm not sure if I get your problem and I tried to reproduce it.
http://apex.oracle.com/pls/apex/f?p=2672:6 is my example with a cascading LOV where I have also defined a dynamic action which fires when P6_EMPNO changes and it shows the current selection.
Maybe it helps if you setup an example on apex.oracle.com and provide the workspace/user/pwd so that I can have a look. I'm also not sure about your sentence "using the new Dynamic Actions to implement Cascading LOV functionality", because dynamic actions are not needed for cascading LOVs. It's a feature of the item types themselves where you just have to set the "Cascading LOV Parent Item(s)" attribute.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Cascading LOVs losing default values

All,
I am using APEX 4.0 and my questions is in regards to the behavior of cascading LOVs.
Users are barking.
Consider the following simple example...
LOV1 (States)
ALL (default)
ALABAMA
ALASKA
LOV2 (Cities)
ALL (default)
ANCHORAGE
ALBANY
AUSTIN
LOV2 is dependant on LOV1. When I make a change of any kind to LOV1, LOV2 loses it's default value.
This occurs even if LOV1 and LOV2 selections are valid (in the event of TEXAS, HOUSTON or ALL, HOUSTON)
Would I need to create a dynamic action to re-populate (or re-validate) LOV2??
Thanks!
Monty

Hi Monty,
APEX doesn't really know that LOV2 includes the same value also the a different parent value has been selected in LOV1.
But as you already mentioned, you can use a dynamic action with an "After Refresh" event for the LOV2 and use a "Set Value" action to set the LOV2 to its original value.
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX 4.0 Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Cascading LOV - Keep Existing Value

Need to stop Cascading LOV to reset the values and keep existing selected options IF VALID
please have a look at the scenario
Col-1     Col-2     Col-3
A     AA     1
A     BB     2
A     CC     3
B     AA     1
B     AAB     2
B     AAV     3When Col-1 value is A the LOV of Col-2 has values AA BB CC and Col-3 has 1 2 3
and if Col-2 value is B the LOV of Col-2 has values AA AAB AAV and Col-3 has 1 2 3
What is happening :
» when user changes Col-1 from A to B Col-2 & Col-3 resets the user selected value (I think the default behavior)
what is needed if user has selected "3" in Col-3 and changes Col-1 from A to B Col-2 & Col-3 should have user selected values IF VALID

Yes, just to show it works. In your case, the second dynamic action has to be something like this:
DECLARE
   v_empno   NUMBER;
BEGIN
   SELECT empno
     INTO v_empno
     FROM emp
    WHERE deptno = :p292_deptno AND empno = :p292_empno;
   RETURN v_empno;
EXCEPTION
   WHEN OTHERS
   THEN
      RETURN v_empno;
END;since it needs to check if the value is in the range of alowed values. In my example I created a fake second entry which has the same ID and there it is enough to do RETURN item value session state.
Denes Kubicek
http://deneskubicek.blogspot.com/
http://www.apress.com/9781430235125
http://apex.oracle.com/pls/apex/f?p=31517:1
http://www.amazon.de/Oracle-APEX-XE-Praxis/dp/3826655494
-------------------------------------------------------------------

Cascading LOVs (v4) and retaining the child value

I've implemented the default delivered implementation in version 4 (4.0.2.00.07 to be exact) of cascading LOVs. Working fine except for one thing...after refresh of a child LOV, the previously selected value is wiped out even when it's still a valid value in the child LOV. If it's an invalid value, I can understand that it would be wiped out, but if it's still valid, I'd like it to be retained.
Example...let's say I have these two select-lists (parent and child).
P100_PARENT
P100_CHILD
P100 Child's SQL references P100_PARENT:
where b.child = NVL(a.parent,b.child)
Optimize refresh is also set to 'No' because I need the child to refresh to all children selections when parent is null.
In short, the parent is optional. If Parent is null, show all child options regardless of Parent. If Parent is defined, show only the child options for the parent.
So when parent is null, I get all child options (OK). I pick one.
If I go to parent and change it to a specific value that IS the parent of the child I chose, my expectation is the child select list should refresh (it does) but if my chosen value is still in the list, it should scroll to it and select it. Instead, it wipes it out.
To put some values into the example...
Let's say parent values are:
A
B
C
null
Let's say child values are numbers such that valid values are:
1 through 10 when parent is A
11 through 20 when parent is B
20 through 30 when parent is C
1 through 30 (any child value) when parent is null.
So I have a null parent LOV value and the child shows me 1 through 30 (OK). I pick 15.
I change the parent to 'B'. Child list refreshes (OK). But while 15 is still a valid value in the list, it is not selected again (my value is wiped out). I still want it to have '15' selected.
Any workaround? Is this a bug? Enhancement opportunity?

Hi Matt,
have you had a look at Skill Builders "Save Value on Cascade" dynamic action plug-in? See http://skillbuilders.com/oracle-apex/Application-Express-APEX-Consulting-Training.cfm?tab=free-plugin-downloads
Regards
Patrick
My Blog: http://www.inside-oracle-apex.com
APEX Plug-Ins: http://apex.oracle.com/plugins
Twitter: http://www.twitter.com/patrickwolf

Problem with cascading dependent LOV query running when it should not

I have a page fragment with a regular ADF form on it that I use to add new entries to a table. This form has many fields on it with LOV’s associated with them. I have dependent LOV’s on some of them. The one case I have is I have three fields A, B, and C. Field C is dependent on A and B. The problem I seem to be having is when I enter a value for field A using it’s LOV, I get an hourglass for a long time after I select it and before it is displayed on the form. If I delete field C from the form the problem goes away. If I change the query behind the view for the LOV for field C to include a rownum < 20 in the where clause the problem goes away. My question is, why would the selection of a value for field A cause the query to fire for field C’s LOV view and how can I stop it. I don’t really want to use the rownum in the where clause.

i had lot of question?
The problem I seem to be having is when I enter a value for field A using it’s LOV, I get an hourglass for a long time
ok. are using? any complex query to pick the lov 'a' .
Answer: The LOV for A is based on a read only non-EO view with a SQL that is not really very complex. The LOV definition does set multiple values when the selection is made to blank out dependent fields in the data model used by the main form.
after I select it and before it is displayed on the form.
here i cant undestud?
Answer. The order of things is I open the main form, I click the mag glass to open the LOV popup, I select the row I want and click the OK button. Navigation returns to the main form where I get the hourglass waiting for the selected value to be displayed in the field on the main form.
If I delete field C from the form the problem goes away. If I change the query behind the view for the LOV for field C to include a rownum < 20 in the where clause the problem goes away.
ok.
why are you going to delete the value of c?. At intial stage you can make empty after selecting a and/or b you can load into c.
Answer: I physically deleted field C from the main form to see if that was what was causing the long delay. When I run the main form without field C I do not get the hourglass. That is how I know they are related.
My question is, why would the selection of a value for field A cause the query to fire for field C’s LOV view and how can I stop it.
you may set partial trigger to c depends for 'a'.
or else lov 'c' query depends on 'a'
Answer. The query for C's LOV does depend on the value returned when I select a value for A. They are cascading LOV's. Will setting the partial trigger stop the SQL for field C from running? Is the SQL running because I'm blanking out field C when I change the value for field A?
am not sure i understud correctly. can you pictuarize you problem with an example.

Cascading List of Values does not work when SQLBuilder is SQL 92.

Hi,
I followed the link http://download.oracle.com/otn_hosted_doc/jdeveloper/11/demos/ADFBC_Cascading_LOV/ADFBC_Cascading_LOV.html to create Cascading LOV. The LOV comes up fine when sqlbuilder and type map is specified as Oracle. However, the same fails when we specify the sqlbuilder as SQL92 and type map as Java. Is this a known issue?
An Invalid Column index exception is being thrown.
The following is the error we see in the stack trace:
# Detail 0 ##
java.sql.SQLException: Invalid column index
     at oracle.jdbc.driver.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
     at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:199)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:263)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:271)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:445)
     at oracle.jdbc.driver.OraclePreparedStatement.setBigDecimalInternal(OraclePreparedStatement.java:4965)
     at oracle.jdbc.driver.OraclePreparedStatement.setObjectCritical(OraclePreparedStatement.java:7694)
     at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:7555)
     at oracle.jdbc.driver.OraclePreparedStatement.setObjectInternal(OraclePreparedStatement.java:8212)
     at oracle.jdbc.driver.OraclePreparedStatement.setObject(OraclePreparedStatement.java:8193)
     at oracle.jdbc.driver.OraclePreparedStatementWrapper.setObject(OraclePreparedStatementWrapper.java:230)
     at oracle.jbo.server.BaseSQLBuilderImpl.bindParamValue(BaseSQLBuilderImpl.java:2133)
     at oracle.jbo.server.BaseSQLBuilderImpl.bindParametersForStmt(BaseSQLBuilderImpl.java:3807)
     at oracle.jbo.server.ViewObjectImpl.bindParametersForCollection(ViewObjectImpl.java:18278)
     at oracle.jbo.server.QueryCollection.buildResultSet(QueryCollection.java:1035)
     at oracle.jbo.server.QueryCollection.executeQuery(QueryCollection.java:815)
     at oracle.jbo.server.ViewObjectImpl.executeQueryForCollection(ViewObjectImpl.java:5892)
     at oracle.jbo.server.ViewRowSetImpl.execute(ViewRowSetImpl.java:1021)
     at oracle.jbo.server.ViewRowSetImpl.executeQueryForMasters(ViewRowSetImpl.java:1178)
     at oracle.jbo.server.ViewRowSetImpl.executeQueryForMode(ViewRowSetImpl.java:1098)
     at oracle.jbo.server.ViewRowSetImpl.executeQuery(ViewRowSetImpl.java:1092)
     at oracle.adf.model.bc4j.DCJboDataControl.executeIteratorBinding(DCJboDataControl.java:1317)
     at oracle.adf.model.binding.DCIteratorBinding.doExecuteQuery(DCIteratorBinding.java:2132)
     at oracle.adf.model.binding.DCIteratorBinding.executeQuery(DCIteratorBinding.java:2093)
     at oracle.jbo.uicli.binding.JUSearchBindingCustomizer.applyAndExecuteViewCriteria(JUSearchBindingCustomizer.java:590)
     at oracle.jbo.uicli.binding.JUSearchBindingCustomizer.applyAndExecuteViewCriteria(JUSearchBindingCustomizer.java:625)
     at oracle.adfinternal.view.faces.model.binding.FacesCtrlSearchBinding.performQuery(FacesCtrlSearchBinding.java:510)
     at oracle.adfinternal.view.faces.model.binding.FacesCtrlLOVBinding$ListOfValuesModelImpl.performQuery(FacesCtrlLOVBinding.java:966)
     at oracle.adfinternal.view.faces.renderkit.rich.SimpleInputListOfValuesRendererBase$InternalLOVQueryListener.processQuery(SimpleInputListOfValuesRendererBase.java:1254)
     at oracle.adf.view.rich.event.QueryEvent.processListener(QueryEvent.java:48)
     at org.apache.myfaces.trinidad.component.UIXComponentBase.broadcast(UIXComponentBase.java:671)
     at oracle.adf.view.rich.component.UIXQuery.broadcast(UIXQuery.java:107)
     at org.apache.myfaces.trinidad.component.UIXCollection.broadcast(UIXCollection.java:147)
     at org.apache.myfaces.trinidad.component.UIXTable.broadcast(UIXTable.java:271)
     at oracle.adf.view.rich.component.UIXTable.broadcast(UIXTable.java:140)
     at oracle.adf.view.rich.component.rich.data.RichTable.broadcast(RichTable.java:364)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.broadcastEvents(LifecycleImpl.java:787)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl._executePhase(LifecycleImpl.java:280)
     at oracle.adfinternal.view.faces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:165)
     at javax.faces.webapp.FacesServlet.service(FacesServlet.java:265)
     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:56)
     at oracle.adf.model.servlet.ADFBindingFilter.doFilter(ADFBindingFilter.java:191)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.adfinternal.view.faces.webapp.rich.RegistrationFilter.doFilter(RegistrationFilter.java:85)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at oracle.adfinternal.view.faces.activedata.AdsFilter.doFilter(AdsFilter.java:54)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl$FilterListChain.doFilter(TrinidadFilterImpl.java:420)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl._doFilterImpl(TrinidadFilterImpl.java:247)
     at org.apache.myfaces.trinidadinternal.webapp.TrinidadFilterImpl.doFilter(TrinidadFilterImpl.java:157)
     at org.apache.myfaces.trinidad.webapp.TrinidadFilter.doFilter(TrinidadFilter.java:92)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.security.jps.wls.JpsWlsFilter$1.run(JpsWlsFilter.java:96)
     at java.security.AccessController.doPrivileged(Native Method)
     at oracle.security.jps.util.JpsSubject.doAsPrivileged(JpsSubject.java:313)
     at oracle.security.jps.wls.util.JpsWlsUtil.runJaasMode(JpsWlsUtil.java:146)
     at oracle.security.jps.wls.JpsWlsFilter.doFilter(JpsWlsFilter.java:140)
     at oracle.security.jps.ee.http.JpsFilter.doFilter(JpsFilter.java:70)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at oracle.dms.wls.DMSServletFilter.doFilter(DMSServletFilter.java:202)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.RequestEventsFilter.doFilter(RequestEventsFilter.java:27)
     at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
     at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.run(WebAppServletContext.java:3588)
     at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
     at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
     at weblogic.servlet.internal.WebAppServletContext.securedExecute(WebAppServletContext.java:2200)
     at weblogic.servlet.internal.WebAppServletContext.execute(WebAppServletContext.java:2106)
     at weblogic.servlet.internal.ServletRequestImpl.run(ServletRequestImpl.java:1428)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
We are using jdev 11g build 5407. Any pointers on these would be really helpful.
Edited by: balasubramanian on Nov 19, 2009 10:37 AM

Set Page and Line#
SCROLL LIST INDEX sy-lsind
            TO PAGE page_no
               LINE line_no.
Set Column position
SCROLL LIST INDEX sy-lsind
          TO COLUMN colm_no.

How to disable an LOV wrt value in another LOV?

I have a javascript function that works fine if P2_BANK_ASSIGNED is a text item. But if I change it to an LOV is doesn't work. How do I disable an LOV on value of another LOV?



<script type="text/javascript">
function disBankAssigned(){
var lReturn = $x('P2_TRIAL').value;
if (lReturn == 0 ) {
     $x('P2_BANK_ASSIGNED').readOnly = false;
else {
     $x('P2_BANK_ASSIGNED').readOnly = true;
</script>
onchange="disBankAssigned();"
regards
Paul P

Try $x('P2_BANK_ASSIGNED').disabled = true;     (or false)

Cascaded LOV loose value when pooling disabled

Similar Messages

Maybe you are looking for