May 25

Was seeing this error on some pages of our application. I found that it only happened on pages that used more than one Application Module (AM). After a lot of googleing and trail and error I found a solution. In our Logout class I added the following code before the redirect with the critical piece in bold:

FacesContext fc = FacesContext.getCurrentInstance();

ValueBinding vb = fc.getCurrentInstance().getApplication().createValueBinding(“#{data}”);

BindingContext bc = (BindingContext)vb.getValue(fc.getCurrentInstance());

if( session != null ) {

Turns out if you use more than one AM on a page you must release it.

Appartly Oracle has patched this known issue (bug # 6416122, base bug# 6365500) but some people mentioned that the fix did not fix their problem. I did not bother applying the patch.

Below is also the helpful pages durning my search.

Tagged with:
May 20

This is how to create a email address link using af:golink;

<af:goLink text=”#{row.EmailAddress}”
destination=”#{\”mailto:\”} #{row.EmailAddress}”/>

Tagged with:
Apr 24

I added a render attribute on one of my commit buttons in order to hide the button based on some business logic. I quickly found out that this will kill the ability for your form to commit. The fix is to move the render logic out to a enclosing af:panelGroup. Here is the change:

<af:commandButton actionListener=”#{bindings.Commit.execute}”
rendered=”#{backing_TerminalEditMode.editMode == \’edit\’

<af:panelGroup rendered=”#{backing_TerminalEditMode.editMode == \’edit\’}”>
<af:commandButton actionListener=”#{bindings.Commit.execute}”
<af:commandButton actionListener=”#{bindings.Rollback.execute}”
text=”Rollback” immediate=”true”>

Tagged with:
Apr 21

I kept getting this error on my page. After a little bit of reading it seems to be a bug with JDeveloper. Something about a naming bug with the page def.

The easy fix. Backup what you have then delete your form components in the Structure and then just re-drag them onto the page.


Tagged with:
Apr 21

What this means:Your jsp/jspx file has grown too big.
Fix:Do a JSP include.

It helps split the file up and yet to the browser the page still looks like it is one file.

Here is what the include looks like:
<%@ include file=”/includes/NewFile.jspf”%>

There is a trick where you can get ADF not to create a Page Def file for NewFile’s but rather point to point to the first one. I never figured that out. What I did was let ADF create the NewFile’s page def and just mirror it from the old file. I know, this is really bad but it had to be done at the time.

Tagged with: