Skip to main content

ADF 11g RC: Manipulating a components toolbar.

Last week I had a question regarding the Rich Text Editor in ADF 11g RC.

Is it possible to disable/enable or add/remove components form the rich text editor's toolbar? At first I didn't know the answer, but after some investigation it appears to be very simple.

The most important piece of the puzzle is to understand how the toolbar is constructed. According to the components documentation, the toolboxLayout property allows control over the layout of the toolbar. This is actually just an Array of Strings.

The built in strings the component recognizes are:
1) "all"
2) "font"
3) "history"
4) "color"
5) "formatAll"
6) "justify"
7) "list"
8) "indent"
9) "link"
10) "newline"
11) "stretch"

For more information on what these built in Strings do, refer to the online help of the component.

One of the options you have to change the toolbar is to bind the editor component to a backing bean. In this bean you can manipulate the list with the built in Strings.

Each of the entries in this select many checkbox correspondents with one of the properties in the toolbar.

Every time a checkbox is selected or deselected, the corresponding item in the toolbar will (dis-)appear. This happens because the autosubmit property of the checkbox is set to true, and in the toolbarItems() method, not only the list with selected checkboxes is updated, but also the bound richTextEditor is changed by calling its setToolboxLayout() method with the list of checked boxes as argument.

public void setToolbarItems(String[] toolbarItems) {
this.toolbarItems = toolbarItems;
for (int i = 0; i < toolbarItems.length; i++) {
toolbarItemMap.put(toolbarItems[i], Boolean.TRUE);

This results in a runtime changeable toolbar.

Note that with this knowledge we are also able to change the toolbar of a calendar component, because this toolbar consists of a set of built in Strings as well.
You can download a workspace with the toolbar functionality here.


Anonymous said…
Great Help for me.The richTexteditor stop working when i set the local of the application to indian language such as hindi(hi).I need to disable the font for that case.
Luc Bors said…
Do you have more info for this ? What version are you using, and what is it exactly that you want to achieve
Rolling Stone said…
Jdeveloper version is Studio Edition Version am toggling the local between English and Hindi(Indian language) using FacesContext.getCurrentInstance().getViewRoot().setLocale(new Locale("hi"))in the login page;
When the local is hindi Richtexteditor of the landing(home page) is failing with some javascript nullpointer exception internally.
Luc Bors said…
Hi there, It looks like a bug in the RichTextEditor. I suggest you either post the question on the JDeveloper ADF forum, or you file a SR on metalink.
Rolling Stone said…
Thanks Luc.I have posted the issue in the ADF forum.Same issue is happening for af:inputDate also.Seems internal adf javascript bug.
Luc Bors said…
FYI: The forumpost can be found here:
Rolling Stone said…
Thanks Luc. RichtextEditor is working by discarding the font from the toolbar. RichInputdate is not working with 'hi' locale.
Using jquery date instead of richInputdate for the time being.

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 the f…

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 butto…

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 AssistantAlexaDigital 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 exposes two REST …