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:
Before:
<af:commandButton actionListener=”#{bindings.Commit.execute}”
action=”#{backing_TerminalEditMode.flipToViewMode}”
rendered=”#{backing_TerminalEditMode.editMode == \’edit\’
text=”Commit”/>
After:
<af:panelGroup rendered=”#{backing_TerminalEditMode.editMode == \’edit\’}”>
<af:commandButton actionListener=”#{bindings.Commit.execute}”
action=”#{backing_TerminalEditMode.flipToViewMode}”
text=”Commit”/>
<af:commandButton actionListener=”#{bindings.Rollback.execute}”
text=”Rollback” immediate=”true”>
<af:resetActionListener/>
</af:commandButton>
</af:panelGroup>
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.
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.
Sorry for the lack of posts lately. My blog software got corrupt on my hosting company. This week I made the move over to DreamHost and everything seems to be going very very well. I’m really happy with them so far.