Next week the ODTUG KScope conference kicks of in New Orleans.
During this conference I will present 3 sessions:
June 24th: Goodbye Nightmare: Tips and Tricks for Creating Complex Layouts with Oracle ADF Faces
June 25th: ADF Mobile: Best Practices for Developing Applications with Oracle ADF Mobile
June 26th: Don't Reinvent the Wheel: Tips and Tricks for Reuse in Oracle ADF
So we are running a quite a bit of automated UI testing and we have found over a large number of concurrent test nodes that even when the Xvnc plugin has correctly started that the environment is not always ready or reliable. This blog post looks at two changes we made that have improved our test stability in recent times.
Today Oracle published the first in a series of online eLearning
training materials. The ADF Academy presents free and online :
Developing Applications with ADF Mobile. The main goal is to deliver
technical training material to everybody that needs it. You get an
online training, where you can view audio and video to learn ADF.
Whenever you want to you can stop the recordings to try out
I should have done this a while ago but last month we released a new version of the wadl2java tools, primarily to deal with issues seen whilst writing a previous blog. The headline change was a move to the latest version of the jsonschema2pojo in order to resolve some class generation issues.
When a developer is working in Java there are a few failure cases you always want to know about even if you were trying to debug something else. Here is a list of the persistent breakpoints that should be enabled in every IDE. (IMHO of course)
Yes in theory you should be able to just get this from a good logging implementation; but often these problems are deep down in somebody else's library caused by changes that are beyond your control..... or just hidden in a large number of currently executing threads.
The Tyrus project, the RI implementation of the Web Socket JSR, has a little sub project added by Pavel Bucek that provides a very useful command line testing tool. (Along with a couple of bug fixes of my own) This blog post gives a quick introduction.
This entry might seem a bit trivial, but from experience I know that sometime new features that are added to the product are not detected by developers who just continue working in the "traditional way". Well here is a quick update on such a feature - PPR:
Way back in 2009 I did a blog entry that showed how to implement partial page rendering (PPR) in ADF by setting the partialTrigger attribute of a field to depend on another.
I posted before on how to do code level debugging in your ADF Mobile application, but sometimes debugging is an overhead and you would rather just put out some log messages that will allow you to track what's going on where.
ADF Mobile has built in support for a logging framework and it is documented in this chapter in the ADF Mobile Developer Guide.
You can use a line of code like this in your code:
A new component that showed up in the JDeveloper 184.108.40.206 release is the af:listView component. This component will become more and more popular as more people target tablet devices with ADF Faces UI. The component allows you to create a scrollable list from a collection of data, and it also does fetching with ranges so you don't get too much network traffic.
The dial gauge is a very visual way to show data in an application - and it has been there in Oracle ADF Mobile since 11.1.2. However in that release you could only use a range of 0-100 - well now you can do better with the new ADF Mobile version.
But there is one little trick to how this works compared to the way it works in the regular web ADF Faces gauge component, and if you don't notice it you might think you are still stuck in the 0-100 days - The trick is the new background property.