LOV refresh issue

Hi ,
I have a LOV switcher attribute in my VO. After saving my page, I need the getter of the switcher to be executed so that the page shows the correct LOV returned by the switcher.
How do I go abt it?
Appreciate your help on this.

Refreshing the switcher attribute can be taken care
1) By setting the dependent attributes
2) Groovy expression.
3) Based on the configuration for the switcher transient attribute (Always/Never/ Based on expression)
Hope you are using at least one of the above ways to refresh LOV switcher. You can debug the issue by generating the impl file and putting a break point at the getter of the variable. That might help you in getting more pointers.
Thanks,
Srini.

Similar Messages

Refresh issue in LOV Switcher

Guys,
I facing a issue from LOV Switcher.
Let me explain the scenario:
I have search page (SearchPage.jsff), i have created page (CreateEditPage.jsff).
CreatePage.jsff has a LOV (Lov is implemented using LOV swither, displays either LOV 1 or LOV2 depnding on the attribute in the viewobject)
1. I navigate from SearchPage.jsff to CreateEditPage.jsff. As per the logic, Lov 1 is displayed. (as expected)
2. Now am back to SearchPage.jsff, and again navigate to CreateEditPage.jsff. As per the logic LOV 2 is displayed. (as expected)
3. Now am back to SearchPage.jsff, and again navigate to CreateEditPage.jsff. As per the logc, LOV 1 should be displayed, but it is displaying Lov 2. (when i refresh the page using F-5, the proper LOV is displayed).
There seems to be some issue with the LOV refresh.
Anybody faced similar issue??
Any suggestions are welcome....

would this help you:
http://jobinesh.blogspot.com/2011/09/programmatically-switching-lov-queries.html

Problem with refresh issue in Table Overflow Area for LOV in edit mode

Hi Friends,
I am facing a problem with LOV if i keep this in Table Overflow area,
When i select a Employee name from the List of Value clicking on select button it will not refresh the lov to display the currently selected Employee Name, but if i click on show and hide link of Table overflow the selected employee name will be displayed.
But the if move the same lov item from Table Overflow area to Table layout it works fine.
I tried my best to look into this but i could not, can any one suggest me what i need to do for this refresh issue.
Regards,
Rahul

Hello Rahul,
Strange, it's working for me.
I assume you added Employees as reference entity to your updatable entity in your ViewObject.
Did you uncheck "Key attribute" in EmployeeId of your reference entity?
Anything in the log?
Groeten,
HJH

Refresh Issue in Oracle ADF In JDeveloper

Hi all,
My ADF Application is having around 350 Forms. Application size is 700MB. I am facing a refresh issue in this application. whenever i am modifying any queries in view objects or lookups it is not reflecting immediately. Say : i modified one query. Then i deployed the application means the query is taking the old query. to take the modified query i have to rebuilt the view object. Every time i am facing this same problem. Some times within 2-3 deployments the query is modified by itself(without rebuild) and working fine. Sometime after 10 times also it is taking the old query only. Every time i have to rebuilt to fix this issue. Please help me to fix this issue. I am using oralce 11g.

Try to invoke Clean All Operation before you deploy the application.
From Main Menu -- >Build --> Clean All

Scrollbar refresh issue in ADF Table

Hello, All
We have an issue regarding the ADF Tables. Please let me know if it is a Oracle bug. All of us know that 'ExecuteQuery' operation refreshes the cache in View Objects.
But, based on our testing results, there might be a table refresh issue on vertical scrollbars after this opertion is executed.
Settings:
In the attached example project, we have a ADF RichTable included in a PanelCollection.
In addition, We set 'AutoHeightRows' property on this ADF RichTable in order to show scrollbars on the PanelCollection.
Furthremore, a standard CommandButton is created on the toolbar to execute queries.
Experimental Steps:
1. Use your mouse to move the vertical scrollbar to around the center of its range. This behavior causes the scrollbar scrolling vertically.
2. Click on any row showing in the table right now, make it to be the active row.
3. Press the 'ExecuteQuery' button, waiting for the table refresh.
Results:
1. Active row moves to the first row in the rowset.
2. Vertical scrollbar stay in the center of its range without moving to the first row.
3. The first row is hidden from end users. The user can not see the active row in this case.
FYI:
The attached project can be accessed from the following link:
http://www.4shared.com/zip/Xn4Ki0DP/Application3.html
In this project, we tried to set 'partialTriggers' on RichTable and its surrounding PanelCollection separately. But, the refreshing issue still exists.
Regards,
David He

Welcome David to forums.
Always mention your exact Jdev version. For more information read this: https://forums.oracle.com/forums/ann.jspa?annID=56
I too faced the similar kind of issue in one of my application.
As you have not mentioned the exact jdev version, I will tell you what I did in my application which was developed using Jdev 11.1.2.0
After the VO is executed, you can write the below line of code to show the first rows in the table.
applicationsRichTable.setDisplayRow(applicationsRichTable.DISPLAY_ROW_FIRST);
//applicationRichTable is the binding for the RichTable in managed beanHope it helps.

5.1.0 sp11 Connection pool refresh issue, revisited....again...!!!

"Hello,
From reading of these newsgroups I've seen many different manifestations
of what seems to be the same root cause with connection pools and
connections which are refreshed/replaced when found broken. In our
case weblogic server hangs.
Kit: 2xWeblogic 5.1.0 sp11 (not clusterd), Solaris 8,
java 1.3.1_01, 1xoracle 8.1.6, latest JDBC 2.0 drivers from oracle. Each weblogic instance and oracle have their own machines.
We do indeed have a firewall employed to run our subnets, and hence
our weblogic servers and oracle databses are in different DMZ's, but are
allowed to communicate to each other via rules set up on the firewall and
inspection of the logs show no such connections being dropped.
As far as the db is concerned, lookups (no writes) never take more than a few
hundred milliseconds and are then closed and given back to the connection pool
immediately from within the 'finally' block of code, hence hard to see when,if ever, the db is
is closing them due to excessive idle time.
weblogic.jdbc.connectionPool.RecipeDBPool=\
url=jdbc:oracle:thin:@foo:1521:BAA,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=30,\
maxCapacity=50,\
capacityIncrement=1,\

Alkesh wrote:
Hi Joe,
The fix you suggested has been implemented and has been running fine
now for the past 3 days. I'm delighted with the result,Great. Glad to help.
but am concerned as to why this problem wasnt highlighted during our
load-testing phases...It's a possibility that your load-testing didn't present the same sort
of load that your actual runtime does.
Thanks for your time on this.Well sure. We want you successful.
Joe
Alkesh
At 01:52 PM 2/22/2002 +0000, you wrote:
Hi Joe,
Thanks for your reply
Please find attached a copy of the jvm thread dump we got from thelast time
that weblogic blocked upon trying to refresh a broken connection.
We have turned off JIT with the environment settingJAVA_COMPILER=NONE.
FYI hotspot is enabled with '-hotspot', these settings can be foundin the
attached 'startWeblogic.sh'.Hi. I found a serious problem by reading the thread dump:
"ExecuteThread-11" daemon prio=5 tid=0x179d40 nid=0x19 waiting for
monitor entry
[0xeee80000..0xeee819e0]
at java.sql.DriverManager.getConnection(DriverManager.java:144)
- waiting to lock <f8e77ad0> (a java.lang.Class)
at com.akqa.sainsburys.jv_recipe.ejb.session.RecipeBean.getConnection(Re
cipeBean.java:759)
It is important to never call DriverManager methods in a multithreaded
application
such as Weblogic, because these JVM methods are alloverly synchronized
at
the class level. One such method, DriverManager.println(), is called
continuously
by all JDBC drivers as well as the SQLException constructor. If one
server thread
makes a long-lasting or hanging call to DriverManager.getConnection(),
it can halt
all JDBC in the whole JVM including work on other open driver
connections.
Please show me the code for RecipeBean.java, and I will send you an
altered version
that should solve this problem. In fact, I can infer from the thread
dump what is needed.
Change the one method getConnection() to this:
// Make once and re-use a driver instance directly, avoiding
DriverManager
Driver d = (Driver)class.forName("weblogic.jdbc.jts.Driver").newInstance();
public Connection getConnection()
return d.connect("jdbc:weblogic:jts:yourPoolNameHere", null );
Also, change your pool definition. I assume you have
testConnsOnReserve set to true.
(You should). Also, you should change your refresh minutes to
something huge, like
9999999. The refresh is interfering with your online performance and
is unnecessary
if you have testConnsOnReserve set. I recommend:
weblogic.jdbc.connectionPool.RecipeDBPool=\
url=jdbc:oracle:thin:@foo:1521:BAA,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=50,\ <------ note that this should be the
same as max, so all cons are made at startup
maxCapacity=50,\
testTable=dual,\
testConnsOnReserve=true,\
refreshTestMinutes=9999999,\
etc.
Joe
I've also attached some firewall logs around the time of weblogicblocking
(12.09). I could only get screen dumps for you, this may or maynot be
useful.
For the firewall logs use the following legend :-
195.110.64.205 - DNS
172.16.160.195 - host webserver 1 (i.e. what our licenses are boundto)
172.16.160.196 - host webserver 2
172.16.160.220 - website 1
172.16.160.230 - website 2
Thanks
Alkesh
-----Original Message-----
From: Joe [mailto:[email protected]]
Sent: 20 February 2002 22:09
To: [email protected]
Subject: Re: 5.1.0 sp11 Connection pool refresh issue,
revisited....again...!!!
At 02:47 PM 2/20/2002 +0000, you wrote:
Hi Joe,
Please find attached a copy of our thread dumps for the most recentoccasion
that weblogic server has stopped.
Apologies for any misunderstandings with my previous post, it appears to
have been cropped. Full posting below (yes we do have testConnOnReserve and
testTable properties set).
Thanks for your time.sure, but first let's get you running OK. These dumps seem to be
very cryptic, as if you're running a highly optimized JVM that
loses almost all of the Java class references I'd normally see.
Can you run again with a more basic JVM? I am beginning to suspect
the JIT JVM...
Joe
Alkesh
Joseph Weinstein wrote:
Hello,
From reading of these newsgroups I've seen many
different manifestations of what seems to be the sameroot cause with connection pools and connections
which are refreshed/replaced when found broken. In our
case weblogic server hangs.
Kit: Weblogic 5.1.0 sp11 (not clusterd),
Solaris 8, java 1.3.1_01, oracle 8.1.6,
latest JDBC 2.0 drivers from oracle.
We do indeed have a firewall employed to run our subnets,
and hence our weblogic servers and oracle databses are
in different DMZ's, but are allowed to communicate to each
other via rules set up on the firewall and inspection of
the logs show no such connections being dropped.
As far as the db is concerned, lookups (no writes) never
take more than a few hundred milliseconds and are then
closed and given back to the connection pool immediately
from within the 'finally' block of code, hence hard to
see when,if ever, the db is is closing them due to excessive idle time.
weblogic.jdbc.connectionPool.RecipeDBPool=\
url=jdbc:oracle:thin:@foo:1521:BAA,\
driver=oracle.jdbc.driver.OracleDriver,\
loginDelaySecs=1,\
initialCapacity=30,\
maxCapacity=50,\
capacityIncrement=1,\
allowShrinking=false,\
testTable=dual,\
testConnsOnReserve=true,\
shrinkPeriodMins=1,\
refreshTestMinutes=10,\ // has been 1 and 5 but 10 'more' stable.
Fequently however, connections are found to be broken
(either by periodical refresh - refreshTestMinutes or
testing connection before granting it to the
application - testConnsOnReserve=true), this has been
confirmed by viewing JDBC.log .
When this is so, weblogic attempts to replace these
broken connections with new ones and then proceeds
to grant it to the application. Once in a while however
(and by no means 'x' refreshes later), weblogic will not
come back.
One of 2 errors occur in our deployment which cuase weblogic
to refresh a connection.
<JDBC Pool RecipeDBPool> java.sql.SQLException: No more data to read fromsocket
and
<JDBC Pool RecipeDBPool> java.sql.SQLException: Io exception: Broken pipe
I believe these settings to all be correct, JDBC drivers
in the correct point BEFORE weblogic.aux in classpath, yet
still have the issue of broken connections.
Any ideas ? I've been reading a lot into this probelm
on various postings now, and i'm completely stumped.
Thanks for your time.
Alkesh

Long posts in I.E. 8 refresh issue

Recently I've had to upgrade to I.E. 8 on some PCs I work with, and posting from them, I've noted the that editing long posts have refresh issues. I type and the cursor returns to the beginning of the post, and I have to keep scrolling back down. Is this a known bug? Or is there a workaround with I.E. 8?

Hi Dave,
I'm obviously far too tolerant of bugs. I'm running IE8 both at home and at work, but this has only ever happened on my work machine. I've meant to look into the cause before now, but I only notice when I'm in the middle of a large post and by the time I've got that out of the way it's usually time to deal with other matters. I've often just put up with the text snapping up and down the screen as I type, but occasionaly have started composing in Notepad or switched browsers. I've just implemented the fix so hopefully I won't need to worry again.
Many thanks,
tt2

Dynamic LOV refresh problems

I have a project site LOV that is set up to only show the sites relating to a particular client. The client is a dynamic LOV as well. Once the Client has been selected and the page/region refreshes the sites LOV should have the possible choices for the client showing. The code is fine as it has worked and I have got it working again but I had to change a lot of settings in the item linked to the LOV. I have a couple duplicate development apps that both work but the settings in the items are different. My question is what is the correct setting?
Sorry if the post seems confusing.
cheers
Ian

Hello
If I understand your problem well, you are using a form based on a database table. The way it works is this: everytime the page is displayed, the database values corresponding to the record being displayed are fetched from the database (this is the setting "always - replacing any value in the session state"). This is correct as you want the page to display the most up-to-date information from the DB.
Hence, when you submit the page in order to refresh the second LOV, that rule applies and you lose the value you just changed in the client field and things get messed up.
Do you have this problem creating a new record or updating an existing one? I think this could work if you are creating a new record, as there is no DB values to overwrite the local values, but I am not sure if this can work if you are updating a record.
Usually people use a "ajax" LOV refresh so the page does not need to be submitted.
I hope this makes sense...
Luis

Refresh issues

I wish to know if there are any refresh issues in the following scenario.
Consider the same application running in 2 distinct VM, jvm1 and jvm2 in a
simple
configuration without L2 cache.
In jvm1 I have:
PersistenceManager pm = pmf.getPersistenceManager();
pm.currentTransaction().begin();
Object oid = xxx;
Object o = pm.getObjectById(oid)
System.err.println(o.xxxx);
pm.currentTransaction().commit();
pm.close():
Then in jvm2:
PersistenceManager pm = pmf.getPersistenceManager();
pm.currentTransaction().begin();
Object oid = xxx;
Object o = pm.getObjectById(oid)
o.setSomeAttribute(xxxx);
pm.currentTransaction().commit();
pm.close():
Now if I execute in jvm1 the first code fragment, do I see the modification
applied in
jvm2 ?
Thanks in advance,
Guido Anzuoni.
BTW, are you going to include oid (and hopefully, class) keyword in
projection in kodo3 ?

Guido,
Yes, you will see the modification in the next PM. The only "stale data"
issues you might see are when you get object ID X in JVM1, modify and
commit object ID X in JVM2, and then continue to reference it in JVM1
(without any closing or refreshing): you will continue to see the cached
version of object ID X.
When this situation is intolerable, you can use pessimistic
transactions: that will guarantee up-to-date views of the object, at the
cost of keeping database locks on the rows open.
In article <[email protected]>, Guido Anzuoni wrote:
No, no, just for confirmation. I have read some posts on this topic and I
have only shown my tipical usage.
Is this behaviour somehow dependent on optimistic settings ?
What if the DB schema is a preexisting one and there is no column for
optimistic locking check ?
Thanks again,
Guido.
"Stephen Kim" <[email protected]> ha scritto nel messaggio
news:[email protected]...
Yes. Are you not seeing this behavior?
As for oid and class keywords, I'm not sure if the feature has been
resolved one way or another yet.
Guido Anzuoni wrote:
I wish to know if there are any refresh issues in the following
scenario.
Consider the same application running in 2 distinct VM, jvm1 and jvm2 ina
simple
configuration without L2 cache.
In jvm1 I have:
PersistenceManager pm = pmf.getPersistenceManager();
pm.currentTransaction().begin();
Object oid = xxx;
Object o = pm.getObjectById(oid)
System.err.println(o.xxxx);
pm.currentTransaction().commit();
pm.close():
Then in jvm2:
PersistenceManager pm = pmf.getPersistenceManager();
pm.currentTransaction().begin();
Object oid = xxx;
Object o = pm.getObjectById(oid)
o.setSomeAttribute(xxxx);
pm.currentTransaction().commit();
pm.close():
Now if I execute in jvm1 the first code fragment, do I see themodification
applied in
jvm2 ?
Thanks in advance,
Guido Anzuoni.
BTW, are you going to include oid (and hopefully, class) keyword in
projection in kodo3 ?
Stephen Kim
[email protected]
SolarMetric, Inc.
http://www.solarmetric.com
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Calendar Refresh Issues

Here's a strange refresh issue with the Apex Calendar. None of the built-in buttons (Monthly, Weekly, Daily, Previous, or Next) are refreshing the calendar with any entries at all when I first load the page. The grid and labels will be updated correctly but the data is not there.
The weird thing is that after a page refreshes, everything suddenly works. I've tried apex.widget.calendar.ajax_calendar('M','same'); etc to no avail. Any help on this would be most appreciated.
Thanks.
mwt

Same thing happening on my iMac. Can't do much on the computer.

Screen refresh issue with SQL Developer 1.5.5 on Vista 64 bit

I am using the latest version of SQL Developer.
I have screen refresh issues in sql developer. On scrolling up and down the display gets jumbled, some time screen do not display at all. Its making working with SQL Developer very difficult. I don't have such an issue with any of my other editors.
Is this something specific to Vista? Is there any know solution to this issue.
Thanks
Edited by: user5899685 on Sep 1, 2009 11:14 AM

Specific? Not really, but judging from the posts here Vista is more prone. It usually indicates incompatibility between Java and video drivers.
If updating your JDK or video driver doesn't work or isn't an option, just disabling DirectDraw in \sqldeveloper\bin\sqldeveloper.conf usually works too:
AddVMOption -Dsun.java2d.noddraw=trueHope that helps,
K.

Enkitec Modal LOV refresh value on screen when updated programmatically

Apex version 4.2.0.00.27
Firefox version 20.0.1
I am using the Enkitec Modal LOV. I have a region button which, when pressed, calls a PLSQL procedure to copy values (including the Modal LOV item) from a previous record into the current one. The Modal LOV item is not showing the new value on screen - it is blank. Looking at the session info, the value is being copied to the item, so does anyone know how I can make the Modal LOV refresh itself to show the new value on screen?
Thanks,
Nick.

Hi,
I am facing the same problem. I used the Modal LOV on modal region. There was the standard popup LOV before - everything went correct. Even if i replaced existing standard LOV with LOV plugin.
I use this plugin in normal forms and it works good. But i have a empty item only in here.
1) In my previous assignation for the item i use (no plugin):
$s('#ITEM_NAME', 'value')
after modal region is opened. (it works OK)
2) If i use the plugin: the item value is null (value="").
3) If i use for value assignation jQuery:
$('#ITEM_NAME').val('value');
assignation is done (value is shown) but the item seem like empty if validation of item occur. (if i press the submit button on modal window it throws "Empty item value")
It is strange...
EDIT: I used jQuery selector for set and get value (when compare to existing records in AJAX call)
$('#ITEM_NAME').val('value'); or $('#ITEM_NAME').val();
It works now.
It will help to you, maybe.
Regards
J

Refreshing issue - Adobe forms!!

Hello,
We are facing a Refreshing issue - Adobe forms, whenever we open the adobe form through open processes, the window doesn't open fully, so again when we refresh it, the size is maximised but the abode forms doesn't open to the full size & we see a small scroll bar on the right hand side.
Please help!
Regards,
Poornima Saligram

Updates: Just found out that this issue rises only to the clients using Wyse terminals. Has anyone had any issue using Adobe forms and Wyse terminals?

CUE 2.1 script refresh issues

At times I am not able to upload new scripts to CUE 2.1 (2.1.0). It gives a script refresh error. Also is there any difference between the script editors for versin 2.1.3, 2.2.2 2.1.1 etc..?? Can I use a script edited using 2.1.3 in version 2.1.0 ?

The scripts are only forward compatible... I.e. you can use a script created with an older version of script editor in a newer version of CUE, but NOT vice-versa. The reason (among other things) is that occasionally there are newer steps added that aren't supported in the older versions. In some cases it'll work, in others it won't work at all; and in some you'll get weird things, such as the date/time steps won't work right.
The bottom line is that you want to use the script editor that matches the oldest version of CUE that you plan on deploying with.
There weren't any real changes in the 2.1 editors. 2.1 added steps like Extension To User. Version 2.3 will add a few more things, as well (and it'll also include a debugger for scripts, which is nice).
About the refresh issue. I recall there were some problems in 2.1.1 and earlier where one could get a refresh issue. For one instance, it was something that would work if you would upload the script via the CLI (from an FTP server) instead of the GUI to work around the problem. For another issue (there's a bug ID...would have to check the release notes to be sure) that was fixed--I believe in 2.1.3--which also had symptoms like that. Basically once you'd get the error there was no way around it until you'd reload CUE. It was a fairly rare event (but annoying nonetheless). One thing that I do remember was that it was so rare that it was basically unreproducible. We found a potential problem, fixed it and then so far haven't heard anyone report such an issue since; but since it was rare to begin with, there's still a slight chance that there's something else causing the problem.

RealVNC with Quad Core Mac Mini "Refresh Issues"

Upgraded my Mac Mini server from a dual core to Quad Core machine. Headless machine, hence used RealVNC to administrator it. So when I utilised RealVNC, connecting via an ipad and the quad core machine had "Refresh Issues"!! Went back to the Dual Core machine and you can view everything in real-time! Can't explain it and the RealVNC people can't understand it either, yet!!!???

It has a wired ethernet connection, the wireless is on but more for "location" services. And no USB 2.0 or 3.0 devices attached, in fact it's headless, and only the power and ethernet connection attached. But interesting to learn of the wireless issues on the new mini's. Thanks!

LOV refresh issue

Similar Messages

Maybe you are looking for