Large ADF Applications - Best Practice

Hi
We have a single ADF project (one model, one view/controller) with the following model components:
68 AMs
387 VOs
175 EOs
This project is ever expanding, and we are suffering some well-known performance problems when open JDeveloper or open the view/controller project.
Are there any best-practice guidelines on how to structure your ADF projects?
e.g. what is the maximum recommended number of AMs/VOs/EOs in a single project?
We have kept everything in a single project after some advice from Oracle to help us to re-use common modules easily.
We use JDeveloper v10.1.3 and use JHeadstart v10.1.3 SU 1 to generate our view/controller layer, using multiple faces-config files.
Thanks
Denis

Hi Denis,
We have exactly the same problem in expanding our application but we have a single AM and less EOs, VOs than you right now. There are some threads discussing this issue but I haven't found a complete and standard solution yet. The only thing I know is that almost every thing can be segmented in ADF like projects, application module, faces-config.xml, ...
Another thing which is very important is that segmenting an application is a tradeoff, it has some advantaes but problems in SCM, security, ...
S/\EE|)

Similar Messages

Could you point me to a ADF development best practice recommendation doc

Could you point me to a ADF development best practice recommendations document for ADF 11g that could be used as a guideline for developers.
Naming conventions
Usage of Models, Implement validation in BC...
Best practices for the UI with ADF Faces...
Recommendations.
Thanks

The right place to start :
http://groups.google.com/group/adf-methodology
Also you may take a look at this:
http://www.oracle.com/technology/products/jdev/collateral/4gl/papers/Introduction_Best_Practices.pdf
Also
http://groups.google.com/group/adf-methodology/browse_thread/thread/e7c9d557ab03b1cb?hl=en#
There're some interesting tips there.

Routing error in Application Best Practice App (TDG) ?

Hi All,
i try Application Best Practices ...
but if i select always another product ...
the category and the Vendor are always the same. But if we check the json files there
are different.
Or should it not work in mock modus?
regards
Bernard

Hi,
I'm not talking about the add. if you select a product ....
the Vendoraddress is always the same ... but in the mockdata json file is different !
cheers
Bernard

Slow starup of Java application - best practices for fine tuning JVM?

We are having problems with a java application, which takes a long time to startup.
In order to understand our question we better start with some background info. You will find the question(s) after that.
Background:
The setup is as follows:
In a client-server solution we have a win xp, fat client running java 1.6.0.18.
(Sun JRE). The fat client containt a lot of GUI, and connects to a server for DB access. Client machines are typical 1 to 3 years old (there are problems even on brand new machines). They have the client version of JRE - standard edition installed (Java SE 6 update 10 or better) Pretty much usual stuff so far.
We have done a lot of profiling on the client code, and yes we have found parts of our own Java code that needs improving. we are all over this. Server side seems ok with good response times. So far, we havent found anything about shaky net connections or endless loops in the java client code or similiar.
Still, things are not good. Starting the application takes a long time. too long.
There are many complicating factors, but here is what we think we have observed:
There is a problem with cold vs. varm starts of the application. Apparently, after a reboot of the client PC - things are really, really bad - and it takes (sometimes) up to 30-40 secs to start the application (until we arrive at the start GUI in our app).
If we run our application, close it down, and then restart
without rebooting, things are a lot better. It then usually takes
something like 15 - 20 sec. which is "acceptable". Not good, but acceptable,
Any ideas why?
I have googled it, and some links seems to suggest that the reason could be disk cache. Where vital jar are already in disk cache on th warm start? Does that make any sense? Virus scanners presumable runs in both cases.
People still think that 15 - 20 sec in start up on the warm start is an awful long time, even though there is a lot, a lot, of functionality in the application.
We got a suggestion to use IBMs JRE - as it can do some tricks (not sure what) our SUN JRE cant do concerning the warm and cold start problem. But thats is not an option for us. And noone has come up with any really good suggestions with the SUN JRE so far?
On the Java Quick Starter (JQS) -
improves initial startup time for most java applets and applications.
Which might be helpful? People on the internet seem more interested
in uninstalling the thing than actually installing it though?
And it seems very proprietary, where we cant give our Jar files to it?
We could obviously try to "hide" the problem in some way and make it "seem" quicker. Where perceived performance can be just as good as actual performance. But it does seem a bad solution. So for the cold start we will probably try reading the jar files and thereby have them in disk cache before startup of our application. And see if that helps us.
Still, ok the cold start is the real killer, but warm start isn't exactly wonderfull either.
People have suggested that we read more on the JVM and performance.
java.sun.com.javase/technologies/performance.jsp
java.sun.com.docs/hotspot/gc5.0/gc_tuning_5.html
the use of JVM flags "-Xms" "-Xmx" etc etc.
And here comes the question .. da da ...
Concerning various suggested reading material.
it is very much appreciated - but we will like to ask people here - if it is possibe to get more specific pointers. to where the gold might be buried.
I.e. in a an ideal world we would have time to read and understand all of these documents in depth. However, in this less than ideal world we are also doing a lot of very timeconsuming profiling in our own java code.
E.g. java garbage collection is is a huge subject - and JVm settings also. Sure, in the end we will probably have to do this all very thoroughly. But for now we are hoping for some heuristics on what other people are doing when facing a problem like ours..?
Young generation, large memory pages, garbage collection threads ect. all sounds interesting - but what would you start with?
If you don't have info to decide - what kind of profiling would you be running and then adjust what JVM setting in your trials?
In this pressed for time scenario. Ignorance is not bliss. But makes it hard to pinpoint the or those JVM parameters to adjust. So some good pointers from experienced JVM "configurators" will be much appreciated!
Actually, If we can establish that finetuning of these parameters is a good idea, it will certainly also be much easier to allocate the time for doing so. - reading, experimenting etc. in our project.
So, All in all , what kinds of performance improvements can we hope for? 5 out of 20 secs on the warm start? Or is it 10 % nitpicking? Whats the ball park figure for what we can hope to achieve here given our setup? What do you think based on above?
Maybe someone out there have done some finetuning of JVM parameters in a similiar PC environments like, with similiar fat clients...? Finetuning so and so - gave 5 secs. So start your work with these one-two parameters?
Something like that - some best practices? Thats what we are hoping for.
best wishes
-Simon

Thanks for helpful answer from both you and kajbj.
The app doesn't use shared network drives.
What are you doing between main starts to get executed and the UI is
displayed?
Basicly, Calculating what to show in the UI. Accessing server - not so much, there are some reads from a cache, but the profiling doesnt indicate that it should be a problem. Sure, I could shift the startup time to some other slot, but sofar I havent found a place where the end-user wouldnt be annoyed.> Caching of something would seem most obvious. Normal VM stuff >seems unlikely. With profiling i basicly find that ''everything'' takes a lot longer in the cold start scenario. Some of our local java methods are going to be rewritten following our review. But what else can be tuned?You guys dont think the Java Quick Start approach, with more jars in disk cache will give something? And how should that be done/ what does people do?I.e. For the class loader I read something about
1.Bootstrap class loader
2.Extensions class loader
3.System class loader
and is wondering if this has something to do with the cold start problem?
The extensions class loader loads the code in the extensions directories (<JAVA_HOME>/lib/ext
So, we should move app classes to ext? Put them in one jar file? (We have many). Best practice about that?
Otherwise it seems to me that it must be about finetuning the JVM?
I imagine that it is a question about:
1. the right heap size
2. the right garbage collection scheme
Googling heap size for XP
CHE22 writes:
You are right; -Xms1600M works well, but -Xms1700M bombs
Thats one best practice or what?
On garbage collection, there are numerous posts, and much "masters of Java black art" IMHO, And according to profiling GC is not really that much of a problem anyway? Still,
Based on my description I was hoping for a short reply like "try setting these two parameters on your xp box, it worked for me" ...or something like that. With no takers on that one, I fear people are saying that there is nothing to be gained there?
we read:
[ -Xmx3800m -Xms3800m
Configures a large Java heap to take advantage of the large memory system.
-Xmn2g
Configures a large heap for the young generation (which can be collected in parallel), again taking advantage of the large memory system. It helps prevent short lived objects from being prematurely promoted to the old generation, where garbage collection is more expensive.
Unless you have problems with pauses, try granting as much memory as possible to the virtual machine. The default size (64MB) is often too small.
Setting -Xms and -Xmx to the same value increases predictability by removing the most important sizing decision from the virtual machine. On the other hand, the virtual machine can't compensate if you make a poor choice.
The -XX:+AggressiveHeap+ option inspects the machine resources (size of memory and number of processors) and attempts to set various parameters to be optimal for long-running, memory allocation-intensive jobs]
So is Setting -Xms and -Xmx and -XX:AggressiveHeap
best practice? What kind of performance improvement should we expect?
Concerning JIT:
I read this one
[the impact of the JIT compiler is obvious on the graph: at startup the time taken is around 500us for the first few values, then quickly drops to 130us, before falling again to 70us, where it stays for 30 minutes,
for this specific issue, I greatly improved my performances by configuring another VM argument: I set -XX:CompileThreshold=50]
The size of the cache can be changed with
-Xmaxjitcodesize
This sounds like you should do something with JIT args, but reading
// We disable the JIT during toolkit initialization. This
// tends to touch lots of classes that aren't needed again
// later and therefore JITing is counter-productiive.
java.lang.Compiler.disable();
However, finding
the sweet spots for compilation thresholds has been tricky, so we're
still experimenting with the recompilation policy. Work on it
continues.
sounds like there is no such straigth forward path, it all depends...
Ok, its good, when
[Small methods that can be more easily analyzed, optimized, and inlined where necessary (and not inlined where not necessary). Clearly delineated uses of data so that usage patterns and lifetimes are apparent. ]
but when I read this:
[The virtual machine is responsible for byte code execution, storage allocation, thread synchronization, etc. Running with the virtual machine are native code libraries that handle input and output through the operating system, especially graphics operations through the window system. Programs that spend significant portions of their time in those native code libraries will not see their performance on HotSpot improved as much as programs that spend most of their time executing byte codes.]
I have the feeling that we might not able to improve performance that way?
Any comments?
otherwise i was wondering about
-XX:CompileThreshold=50 -Xmaxjitcodesize (large, how large?)
Somehow, we still feel that someone out there should have experienced similiar problems? But obviously there is no guarantee that the someone should surf by here!
In c++ we used to just write everything ourselves. Here it does seem to be a question about the right use of other peoples stuff?
Where you are kind of hoping for a shortcut, so you dont have to read endless number of documents, but can find a short document that actually addresses your problem ... well.
-Simon
Edited by: simoncpm on Mar 15, 2010 3:43 PM
Edited by: simoncpm on Mar 15, 2010 3:53 PM

SOA composite application best practice

Hi All,
We are running SOA Suite 11g. One of my colleagues said that we should always have a mediator in our composite applications instead of just exposing the BPEL Process as a SOAP service. Is this a correct statement? If so why is that good practice. Still trying to grasp the concepts and best practices for SOA so any information is greatly appreciated.
Thanks,
S

if you place a mediator in between them, you can change the bpel interface without having to change your composite soap interface
that's one thing which could be a best practice

Oracle Service Bus - Large Configuration Space Best Practices

Does anyone have any best practices for handling large configurations in Oracle Service Bus (formerly ALSB)? We are going to have hundreds of HTTP services defined. Any best practices for handling proxy service granularity, cross cutting areas and componentization to help us create a high level of quality and consistency?
Thanks

We are going to face the similar situation soon. Any real world experience would be great.

Hotfix Application Best Practices

I have a twofer with regards to applying a hotfix. We deployed Config Manager 2012 RTM, upgraded to SP1, and then upgraded to R2. We have never applied a hotfix or CU before, so there is a bit of mysteriousness with regards to what the best practices are.
We are applying hotfix 2910552 to address slow imaging speeds. These questions are pretty basic but I wanted to get some informed opinions.
What is the best rollback procedure in the event of problems? I consider the hotifx a low risk but there is some concern from some others above me. We are planning on taking snapshots of the 3 site servers and the DB server in our hierarchy, but not the
DPs. Does this seem sound or is there a better technique?
How essential is it to update the clients in our environment in a timely fashion, or at all? I am going to have the packages created, but I did not know if I should deploy them immediately or not. Our server group has some concerns about applying the patch
to the config manager clients on our servers during our patching windows.
Any insight is appreciated. Thanks!
Bryan

There's more risk in taking snapshots as they are completely and explicitly unsupported and almost certainly would cause issues particularly since your DB is separate from your site server.
Rollback is simply uninstalling the hotfix. That hotfix addresses a very niche issue that only manifests itself during OSD, thus, it's only important roll it out to clients before you reimage them in a refresh scenario. An alternative rollback is simply
reinstalling the site and restoring your DB. This sounds painful and while it would take a bit of time, it's actually rather painless and works quite well.
This all begs the question though, you really should just do CU3. There are tons of other meaningful and impactful fixes in the CUs that will improve the overall stability and even functionality of the site and clients.
Concerns for applying hotfixes should be addressed by performing the update in a lab first. There is no other way to comfort risk averse folks except by showing them that it works. Additionally, you put forth evidence from the community that CU application
to ConfigMgr is almost always smooth and uneventful. Can something go wrong? Of course. I could get hit by lightning sitting in my chair but that doesn't mean I stay in bed all day.
Jason | http://blog.configmgrftw.com | @jasonsandys

Web application best practice...

I'm creating a web site with heaps of Flash stuff on it. I'd
like it to load plenty of information from a database server and
save plenty of information back again. It's not a vast amount of
information by the way - i don't need to load video clips and
things, but there will be loads of different flash resources on the
site and so plenty of different occasions when there'll need to be
some loading and saving going on.
So to the question - what's best to use?
1) LoadVars? (or XML Object) - I'm pegging this option
together as I can see that loading some of the info in XML format
from say an ASP page could be a good idea
2) Web services? I don't know much about webservices, but
plenty of big companies seem to be offering them out - google,
yahoo and flickr for example (- but dya reckon they use them
themselves?) I realise i'd have to learn something a bit different
like .net (so maybe VB.net or c# or something any opinions about
which to go for there too??) or maybe perl or python or
something...
3) Flash Remoting? I have bad feelings about this one - i
don't want to pay for extra stuff if it doesn't do much for me -
and i understand that with this one i'll still need my server side
application anyway - so it makes me wonder what the point is? And
I've also heard that the latest flash version doesn't really
support it very welll.....
So does anyone have any thoughts? I'd love to hear some
opinions... I DO care about performance and I DO care about how
fussy and complicated the programming will be. My gut reaction is
that web services are the way to go, because to my naive mind they
seem like they'll be simpler to code and potentially have less bugs
and therefore be more reliable. But then I'm not trusting my naive
mind, I'm asking you clever forum types instead!
Best Wishes,
Neil

I don't think I can offer any definitive advice. Partly
because it should be based on what your requirements are longer
term I guess, and (probably mostly) because I don't know that much
about it myself. I'll share what little I know.
For flash, in terms of my understanding remoting is the
fastest/most efficient means of communicating with a service you
expose on your server , and I'd assume its more scalable as an
approach longer term. There's the Adobe versions with Coldfusion
and, I think .net, but there are open source options e.g. AMFPHP as
well. I think that CS3/as3 will ultimately have no problems with
remoting - I read somewhere that although the remoting components
are not there now, flash cs3 can use flex non-visual components and
also somewhere else that the remoting components are not necessary
for remoting to be possible (but I guess they make it easier). I
have no idea whether either is true, but I'd be surprised if long
term flash cs3 can't do remoting as well as previous versions. The
amf encoding method that is used for remoting is more readily
accessible in as3 I think, so I can't see it being a problem.
There's another framework for a type of remoting based on
what I assume is some form of XML serialisation called XMLPC , but
I don't know much about it.
Both flash remoting and XMLRPC give you the ability to not
worry about how the data is translated and transferred between
flash client and server. You just deal with it in the native data
structures in a similar way to making function/method calls
locally. LoadVars is great if you just want to transfer name value
pairs...eg sets of variables, XML is great for transferring
structured representation of data. I've become more accustomed to
working with XML as it is and using it as a the basis for my data
in flash when I need to use it, which saves having customer
encoding/decoding functions to change the way its dealt with
locally. This is not always possible or convenient... but with
XPathAPI in as2 it is a little easier, and I'm looking forward to
using the new CS3 xml representation.
LoadVars and XML are also great and if you're starting out,
and are probably essential in terms of having them as an option
anyhow so may not be a bad option to begin with just so you're
familiar with them. I would suggest that you always know how to
work with these approaches and maybe they'll be enough for you for
now anyway .
I know nothing about SOAP or any other type of webservice.
Don't know if that helps.

Schema Design for Worklist Application - best practice?

Hello,
we are designing the Schema for a workflow application now. I'm wondering what kind of XML Schema would be best suited for the JSP generation of the Workflow Wizard.
So far I've found out with some tests (please correct me if I'm wrong):
- Only elements will be mapped to JSP fields, not attributes
- If elements have single-letter name, the field label will be eliminated totally in JSP (bug?!)
- For EVERY parent node, an HTML table is generated in the JSP containing all the simple nodes in the parent. If a parent node contains another parent node, both tables will be generated on the same level.
And I haven't found any way to create drop-down list or checkbox/radiobuttons out of the XSD definition (enumeration as element type).
I would really appreciate it if someone could share some experience in this area, many thanks in advance!
regards
ZHU Jia

Hello,
we are designing the Schema for a workflow application now. I'm wondering what kind of XML Schema would be best suited for the JSP generation of the Workflow Wizard.
So far I've found out with some tests (please correct me if I'm wrong):
- Only elements will be mapped to JSP fields, not attributes
- If elements have single-letter name, the field label will be eliminated totally in JSP (bug?!)
- For EVERY parent node, an HTML table is generated in the JSP containing all the simple nodes in the parent. If a parent node contains another parent node, both tables will be generated on the same level.
And I haven't found any way to create drop-down list or checkbox/radiobuttons out of the XSD definition (enumeration as element type).
I would really appreciate it if someone could share some experience in this area, many thanks in advance!
regards
ZHU Jia

Large object model best practices

Are there recommended practices for mapping large object models? Seems like there should be API support for this so that developers can automate map generation. I just can not see mapping 100s of classes by hand.
What about change management? How do folks manage schema changes?
Feel free to point me at the docs and tell me to FTFM. ;-)

Thanks for the reply James but I'm still unsure how to avoid hand mapping 100's of classes. Are you suggesting that TopLink can load my object model (1000+ classes) and generate DLL and mappings that will simply work?

MCX to Configure Client Dock Applications best Practice?

I want to use WGM preferences to manage which applications show up on a user's dock when they login. The server does not have the same applications installed as the client machines thus do not show up as an available option to add using WGM.
_The Question:_ *Is is bizarre to install client applications on the server so it may be available to to add to a user's dock preference in WGM?*
Currently I'm using changes I've made to the default user template as a work around to getting the dock configured to our needs. Not my favorite way to administer 6 labs, but functional right now. If it's okay, I was thinking about installing all the software we use on our client machines on the server.
Is there a better way of managing the dock for clients in a multiple lab environment?

Run the WGM application from a workstation that has the same applications installed in the same locations as on your client workstations. Do not make changes to the user templates on the server or the workstations. When setting the preferences for the user's dock, do not select the checkbox, 'Merge with User's Dock', as that combines the customized settings you create with the dock settings from the user template.

Best Practice for Deploying ADF application

I am tasked with developing a best or prefered practice of feploying a large ADF application. Background: we are in the process of redeveloping a UI for a large system. We have broken the system down into susbsytems. Each of these susbsystems UI will be a ADF aaplicaion(?). This is a move from a MS .Net front end. The backend (Batch processes etc) is being dveloped in Java. So my question is if I have several ADF projects for each subsystem and common components that they all will use - what is the best practice to compile package and deploy? The deployment will be to weblogic server or servers(Cluster).
We have a team of at least 40 -50 developers worldwide so we are looking for an automated build and deploy and would like to follow Oracle best practice. So far I have read Deploying ADF Applications (http://download.oracle.com/docs/cd/E15523_01/web.1111/e15470/deploy.htm#BGBJHGFH) and have followed the links. I have also look at the ADF evangalist blogs - lots of chatter about ojdeploy. My concern about ojdeploy is that dependent files are also being compiled at the same time. I expected that we want shared dependent files compiled only once (Is that a valid concern)?
So then when we build the source out of subversion (ojdeploy ? Ant? ) then what is best practice to deploy to a weblogic server (wslt admin console) - again we want it to be automated.
Thank you in advance for replies.
RK

Rule 1: Never use the "Automatically Expose UI Componentes in a New Managed Bean" option, create your bindings manually;
Rule 2: Rule 1 is always right;
Rule 3: In doubts, refer to rule 2.
You may also want to check out :
http://groups.google.com/group/adf-methodology
And :
http://www.oracle.com/technology/products/jdev/collateral/4gl/papers/Introduction_Best_Practices.pdf

Where to put java code - Best Practice

Hello. I am working with the Jdeveloper 11.2.2. I am trying to figure out the best practice for where to put code. After reviewing http://docs.oracle.com/cd/E26098_01/web.1112/e16182.pdf it seemed like the application module was the preferred spot (although many of the examples in the pdf are in main methods). After coding a while though, I noticed that there were quite a few libraries imported, and wondered whether this would impact performance.
I reviewed postings on the forum, especially Re: Access service method (client interface) programmatically . This link mentions accessing code from a backing bean -- and the gist of the recommendations seems to be to use the data control to drag it to the JSF, or use the bindings to access code.
My interest lies in where to put java code in the first place; In the View Object, Entity Object, and Am object, backing bean.....other?
I can outline several best guesses about where to put code and the pros and cons:
1. In the application module
Pros: Centralized location for code makes development and support more simple as there are not multiple access points. Much like a data control centralizes services, the application module can act as a conduit for different pieces of code you have in objects in your model.
Cons: Everything in one place means the application module becomes bloated. I am not sure how memory works in java -- if the app module has tons of different libraries are they all called when even a simple query re-execute method is called? Memory hog?
2. Write code in the objects it affects. If you are writing code that accesses a view object, write it in a view object. Then make it visible to the client.
pros: The code is accessed via fewer conduits (for example, I would expect that if you call the application module from a JSF backing bean, then the application module calls the view object, you have three different pieces of code --
conts: The code gets spread out, harder to locate etc.
I would greatly appreciate your thoughts on the matter.
Regards,
Stuart
Edited by: Stuart Fleming on May 20, 2012 5:25 AM
Edited by: Stuart Fleming on May 20, 2012 5:27 AM

First point here is when you say "where to put the java code" and you're referring to ADF BC, the point is you put "business logic java code" in the ADF Business Components. It's fine of course to have Java code in the ViewController layer that deals with the UI layer. Just don't put business logic in the UI layer, and don't put UI logic in the model layer. In your 2 examples you seem to be considering the ADF BC layer only, so I'll assume you mean business logic java code only.
Meanwhile I'm not keen on the term best practice as people follow best practices without thinking, typically best practices come with conditions and people forget to apply them. Luckily you're not doing that here as you've thought through the pros and cons of each (nice work).
Anyway, back on topic and off my soap box, as for where to put your code, my thoughts:
1) If you only have 1 or 2 methods put it in the AppModuleImpl
2) If you have hundreds of methods, or there's a chance #1 above will morph into #2, split the code up between the AppModuleImpl, ViewImpl and ViewRowImpls. Why? Because your AM will become overloaded with hundreds of methods making it unreadable. Instead put the code where it should logically go. Methods that work on a specific VO row go into the associated ViewRowImpl, methods that work across rows in a VO go into the ViewImpl, and methods that work across VOs in the associated AppModuleImpl.
To be honest which you ever option you choose, one thing I do recommend as a best practice is be consistent and document the standard so your other programmers know.
Btw there isn't an issue about loading lots of libraries/imports into a class, it has no runtime cost. However if your methods require lots of class variables, then yes this will have a memory cost.
On a side note if you're interested in more ideas around how to build ADF apps correctly think about joining the "ADF EMG", a free online forum which discusses ADF architecture, best practices (cough), deployment architectures and more.
Regards,
CM.

Best practice for mouseless ADF applications

I am developing an ADF application where the users do not want to use the mouse.
So I would like to know if there are a best practice for this?
I am already using the accessKey functionality and subforms defaultCommand
But I have had problems setting focus to objects on a page like tables. I would like a button to return the focus to the table after it has made the command like delete.
I have implemented a solution where I have found inspiration several threads and other webpages (see below).
Is this solution okay?
Are there any problems with it?
I would also like to know if there are better pathways to go like
out of the box solutions,
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/79-global-template-button-strategy-360139.pdf (are there an example implementation?), or
http://one-size-doesnt-fit-all.blogspot.dk/2010/11/adf-ui-shell-supporting-global-hotkeys.html
in advance thanks
Inspiration webpages
https://blogs.oracle.com/jdevotnharvest/entry/how_to_programmatically_set_focus
http://technology.amis.nl/2008/01/04/adf-11g-rich-faces-focus-on-field-after-button-press-or-ppr-including-javascript-in-ppr-response-and-clientlisteners-client-side-programming-in-adf-faces-rich-client-components-part-2/
how to Commit table by writting Java code in Managed Bean?
Table does not refresh and getting error as UIComponent is Null
A short description of the solution:
(jdeveloper version 11.1.1.2.0)
--- Example where I use onSetFocus in jsff page
<af:commandButton text="#{hrsusuiBundle.FOCUS}" id="cb10"
partialSubmit="true" accessKey="f"
shortDesc="Alt+Shift+F"
actionListener="#{managedBean_clientUtils.onSetFocus}">
<af:clientAttribute name="focusField" value="t1"/>
</af:commandButton>
--- Examples where I use doTableActionAndSetFocus in jsff page
--- There have to be a binding in the jsff page to delete, commit and rollback
<af:commandButton text="#{hrsusuiBundle.DELETE}" id="cb4"
accessKey="x"
shortDesc="Alt+Shift+X"
partialSubmit="true"
actionListener="#{managedBean_clientUtils.doTableActionAndSetFocus}">
<af:clientAttribute name="focusField" value="t1"/>
<af:clientAttribute name="actionField" value="Delete"/>
</af:commandButton>
<af:commandButton text="#{hrsusuiBundle.COMMIT}" id="cb5"
accessKey="s" shortDesc="Alt+Shift+S"
partialSubmit="true"
actionListener="#{managedBean_clientUtils.doTableActionAndSetFocus}">
<af:clientAttribute name="focusField" value="t1"/>
<af:clientAttribute name="actionField" value="Commit"/>
</af:commandButton>
<af:commandButton text="#{hrsusuiBundle.ROLLBACK}" id="cb6"
accessKey="z" shortDesc="Alt+Shift+Z"
partialSubmit="true"
actionListener="#{managedBean_clientUtils.doTableActionAndSetFocus}"
immediate="true">
<af:resetActionListener/>
<af:clientAttribute name="focusField" value="t1"/>
<af:clientAttribute name="actionField" value="Rollback"/>
</af:commandButton>
--- This is the java class I use
--- It is published in adfc-config.xml as a request scope managedbean
public class ClientUtils {
public ClientUtils() {
public void doTableActionAndSetFocus(ActionEvent event) {
RichCommandButton rcb = (RichCommandButton)event.getSource();
String focusOn = (String)rcb.getAttributes().get("focusField");
String actionToDo = (String)rcb.getAttributes().get("actionField");
UIComponent component = null;
String clientId = null;
component = JSFUtils.findComponentInRoot(focusOn);
clientId = component.getClientId(JSFUtils.getFacesContext());
if ( "Delete".equals(actionToDo) || "Commit".equals(actionToDo) || "Rollback".equals(actionToDo) ){
BindingContainer bindings = BindingContext.getCurrent().getCurrentBindingsEntry();
OperationBinding operationBinding = bindings.getOperationBinding(actionToDo);
Object result = operationBinding.execute();
AdfFacesContext.getCurrentInstance().addPartialTarget(component);
if (clientId != null) {
makeSetFocusJavaScript(clientId);
public static String onSetFocus(ActionEvent event) {
RichCommandButton rcb = (RichCommandButton)event.getSource();
String focusOn = (String)rcb.getAttributes().get("focusField");
String clientId = null;
if (focusOn.contains(":")) {
clientId = focusOn;
} else {
clientId = findComponentsClientIdInRoot(focusOn);
if (clientId != null) {
makeSetFocusJavaScript(clientId);
return null;
private static void writeJavaScriptToClient(String script) {
FacesContext fctx = FacesContext.getCurrentInstance();
ExtendedRenderKitService erks = null;
erks = Service.getRenderKitService(fctx, ExtendedRenderKitService.class);
erks.addScript(fctx, script);
public static void makeSetFocusJavaScript(String clientId) {
if (clientId != null) {
StringBuilder script = new StringBuilder();
//use client id to ensure component is found if located in
//naming container
script.append("var textInput = ");
script.append("AdfPage.PAGE.findComponentByAbsoluteId");
script.append ("('"+clientId+"');");
script.append("if(textInput != null){");
script.append("textInput.focus();");
script.append("}");
writeJavaScriptToClient(script.toString());
public static String findComponentsClientIdInRoot(String id) {
UIComponent component = null;
String clientId = null;
component = JSFUtils.findComponentInRoot(id);
clientId = component.getClientId(JSFUtils.getFacesContext());
return clientId;
}

Hi,
I am developing an ADF application where the users do not want to use the mouse. So I would like to know if there are a best practice for this?
Well HTML (and this is the user interface you see) follows a tab index navigation that you follow with "tab" and "shift+tab". Anything else is a short cut for which you use mnemonics (as you already do) or shortcuts (explained in http://one-size-doesnt-fit-all.blogspot.dk/2010/11/adf-ui-shell-supporting-global-hotkeys.html). There is a distinction to make between non-web environments (which I think you and your users have abackground in) and client desktop environments. Browsers block some keyboard functionality for their own purpose. So you may have to find a list of keys first that work across browsers. Unlike desktop clients, which allow you to "press a button" without the button to take focus, this cannot be done on the web. So you need to be clever here, avoiding buttons at all.
The following paper is about JavaScript in ADF and explains the basics for what Chris Muir explains in : http://one-size-doesnt-fit-all.blogspot.dk/2010/11/adf-ui-shell-supporting-global-hotkeys.html
http://www.oracle.com/technetwork/developer-tools/jdev/1-2011-javascript-302460.pdf
It has the outline for how to register short cut keys that perform a specific action (e.g. register ctrl+d to delete the current row you are on, or press F11 to execute a query (similar to Oracle Forms frmres files)). However, be aware that this includes some code you have to write (actually quite some code to be honest).
http://www.oracle.com/technetwork/developer-tools/adf/learnmore/79-global-template-button-strategy-360139.pdf (are there an example implementation?), or
http://one-size-doesnt-fit-all.blogspot.dk/2010/11/adf-ui-shell-supporting-global-hotkeys.html
Actually these are implementations as they come with example code for you to use and customize, do they? So what is this question asking for more ? Also note that global buttons don't quite have anything in common with the question you asked. I assume you want to see it as an implementation of the Forms toolbar that operates on the form or table the focus is in. This however does not work for the web as there is nothing that keeps track of which component has a focus and to what iterator (data block) it belongs. This would involve even more coding (though possibly doable)
Frank

Best practices for large ADF projects?

I've heard mention (for example, ADF Large Projects of documentation about dealing with large ADF projects. Where exactly is this documentation? I'm interested in questions like whether Fusion web applications can have more than one ViewController project (different names, of course), more than one Model project, the best way to break up applications for ease of maintenance, etc. Thanks.
Mark

I'd like to mention something:
Better have unix machines for your development.
Have at least 3 GB of RAM on windows machines.
Create all your commonly used LOVs & VOs first.
If you use web services extensively, create it as a seperate app.
Make use of popups, it's very user friendly and fast too. You no need to deal with browser back button.
If you want to use common page template, create it at the beginning. It's very difficult if you want to apply it later after you developed pages.
Use declarative components for commonly used forms like address, etc.
Search the forum, you will see couple of good util classes.
When you check-in the code, watch out some of the files don't show up in JDev like connections.xml
Make use of this forum, you will get answers immediately from great experts.
http://www.oracle.com/technology/products/jdev/collateral/4gl/papers/Introduction_Best_Practices.pdf

Large ADF Applications - Best Practice

Similar Messages

Maybe you are looking for