Everything that is Oracle related.
One of the great features of ADF is the easy out-of-the-box support for Partial Page Rendering (PPR) using the partialTriggers, autoSubmit and partialSubmit properties. And when things get a bit more complex there is a very easy API to do it programmatically. But what if
- you don’t know beforehand what attribute or column will change, or
- you don’t want to replicate this “Model logic” in the View layer (e.g. because you want to adhere to the Model-View-Controller pattern), or
- components are scattered across Taskflows (in which case you cannot use the declarative support and the programmatic approach is suddenly very hard)?
Fortunately, ADF has a solution: Automatic Partial Page Rendering (or Auto PPR). If you have used ADF with Business Components, you might have seen or used it already, but it is less obvious that you can also use it with ordinary Beans or Bean DataControls.
A little while ago I got a very nice challenge: play around with the ADF client-side framework.
It was implemented using autoSubmit and partialTriggers. Due to the roundtrip to the server the response time was low when having a lot of rows. To speed it up, I was asked to look if (de)selecting all rows could be done on the client.
Never having worked with that part of ADF yet, I started searching and quickly found the Oracle documentation, but actual examples to clarify some topics.. hmmm not so much. The use case is quite specific but I thought it would still be nice to blog about it to be at least an example of some of the client-side functionality for other people in need. (more…)
When you write a lot of code, no matter what sophisticated framework you use, there are pieces of code that you end up writing over and over again (especially when using Java). Writing logging code in Java is a good example. A common pattern is to initialize a static logger variable in every class you want to log something. Fortunately, JDeveloper has a feature called “Code Templates” that can make your life a lot easier! I have seen several blogs that explain how to use Code Templates for logging code (I saw one from as early as 2006; the feature itself has actually been available since 2004!). But still a lot of people are not aware of this feature (or perhaps simply forget to use it).
To be useful, data held and used in information systems has to live up to a number of expectations. The data should be an accurate representation of its source. It should be reliable. The data should have internal consistency. The data should adhere to rules based on the logic of the real world. This accuracy, internal quality, and reliability of data is frequently referred as data integrity.
Safeguarding the integrity of data is a challenge, one that increases in complexity when multiple users access and manipulate the data simultaneously , obviously a common situation. And that challenge reaches new heights when the data is managed in multiple independent data stores rather than a single database.
Earlier this month, the Oracle Technology Network published an article that I recently wrote on this subject: http://www.oracle.com/technetwork/articles/soa/jellema-data-integrity-1932181.html. I was triggered into writing it by two recent experiences.
One was at a customer of mine where we are designing a service oriented architecture, based on a number of distinct and independent data domains. These domains are exposed through elementary (entity) services. A second tier of More >
Oracle Designer is a windows client-server development tool that is meant to be manually operated by a developer. Anyone trying to integrate Designer with an automatic build environment will find that it does not provide an API or a commandline version to kick-off any generation automatically.
There is however a hook that can be exploited by generating so-called GBU files directly from the Designer Repository. These GBU files are then fed to an executable called dwzrun61.exe that executes the actual generation of DDL scripts and forms.
This article describes how this can be done using examples from a real world situation. It shows how to generate the GBU files, the different strategies that can be followed and some of the pitfalls you might run into trying to pull this off yourself.
The code of the program we wrote can be found on here and is free to be adjusted to fit any other situation than ours.
Lucas Jellema heeft voor Computable zijn ervaringen van de twee weken durende conferentie tour, Yathra 2013, samengebundeld. In het verslag ‘Verkenning van de IT-sector in India’ wordt ingegaan op de verwachtingen, vooroordelen, het algemene beeld en op de ontwikkelingen van de IT in India en schetst een beeld over de nabije toekomst. Nieuwsgierig naar zijn India-belevenissen en ervaringen?