Skip to main content

ADF 11g: My new publications.

I have had a very busy month. I spent most of my evenings writing. Writing code? Nope, writing text! It looked like it all came at the same moment. I had 3 deadlines in January, 2 of which were in the last week.

One of the things I wrote was a blog post at the AMIS blog. It was a post that I started to write some time ago, but I never took the time to finish it. It describes how to create a dynamic updateable table. An overview of my blog-posts on the AMIS technology blog can be found here: http://technology.amis.nl/blog/author/luc

The next one was for my own column in Optimize Magazine. As of this year (2010) I have a column about ADF in Optimize Magazine. The column is called ADF@WORK, and it is about the daily work with ADF. The first edition, which will be printed in the February issue, is about View Criteria, and how they can be used declaratively and programmatically.

And as if that was not enough, I had the opportunity to write an article for OTN about a brand new ADF feature that was announced at OOW 2009. I cannot say much about it. It will be printed at the OTN site somewhere in February. Once it is out there I will write more about it on this blog.

So all in all that’s 3 publications of which I’m proud. I hope to write a lot more this year.

Comments

John Flack said…
I was curious about your statement that you have an article scheduled to appear in Optimize Magazine. I did a little quick research, and the only references to "Optimize Magazine" that I could find were for a magazine from the editors of Information Week that ceased publication in April 2007. Besides, it was more business related - not information for developers like you and me.
Luc Bors said…
Hi JCFlack,
this article in optimize magazine is in dutch. Optimize is a magazine for oracle developers.

http://www.optimize.nl/

I will try and post a translated version of the column somewhere shortly.

Popular posts from this blog

ADF 12.1.3 : Implementing Default Table Filter Values

In one of my projects I ran into a requirement where the end user needs to be presented with default values in the table filters. This sounds like it is a common requirement, which is easy to implement. However it proved to be not so common, as it is not in the documentation nor are there any Blogpost to be found that talk about this feature. In this blogpost I describe how to implement this. The Use Case Explained Users of the application would typically enter today's date in a table filter in order to get all data that is valid for today. They do this each and every time. In order to facilitate them I want to have the table filter pre-filled with today's date (at the moment of writing July 31st 2015). So whenever the page is displayed, it should display 'today' in the table filter and execute the query accordingly. The problem is to get the value in the filter without the user typing it. Lets first take a look at how the ADF Search and Filters are implemented by

How to: Adding Speech to Oracle Digital Assistant; Talk to me Goose

At Oracle Code One in October, and also on DOAG in Nurnberg Germany in November I presented on how to go beyond your regular chatbot. This presentation contained a part on exposing your Oracle Digital Assistant over Alexa and also a part on face recognition. I finally found the time to blog about it. In this blogpost I will share details of the Alexa implementation in this solution. Typically there are 3 area's of interest which I will explain. Webhook Code to enable communication between Alexa and Oracle Digital Assistant Alexa Digital Assistant (DA) Explaining the Webhook Code The overall setup contains of Alexa, a NodeJS webhook and an Oracle Digital Assistant. The webhook code will be responsible for receiving and transforming the JSON payload from the Alexa request. The transformed will be sent to a webhook configured on Oracle DA. The DA will send its response back to the webhook, which will transform into a format that can be used by an Alexa device. To code

ADF 11g Quicky 3 : Adding Error, Info and Warning messages

How can we add a message programatically ? Last week I got this question for the second time in a months time. I decided to write a short blogpost on how this works. Adding messages is very easy, you just need to know how it works. You can add a message to your faces context by creating a new FacesMessage. Set the severity (ERROR, WARNING, INFO or FATAL ), set the message text, and if nessecary a message detail. The fragment below shows the code for an ERROR message. 1: public void setMessagesErr(ActionEvent actionEvent) { 2: String msg = "This is a message"; 3: AdfFacesContext adfFacesContext = null; 4: adfFacesContext = AdfFacesContext.getCurrentInstance(); 5: FacesContext ctx = FacesContext.getCurrentInstance(); 6: FacesMessage fm = 7: new FacesMessage(FacesMessage.SEVERITY_ERROR, msg, ""); 8: ctx.addMessage(null, fm); 9: } I created a simple page with a couple of buttons to show the result of setting the message. When the but