How to add enter-in-insert mode without post-generation steps

Question

Hello,
We'd like to enter one of our pages in insert mode.
We found the trick how to do it, there is one step which is a post JHeadstart generation step (add code to Page Definition). I'd like to know if we can avoid this post-generation step
Here the complete list of steps
(1) Model project, set View Object, Tuning to 'No Rows'
(2) ViewController Project
2.1 JHeadstart settings for the page
- Single-row insert allowed Yes
- Single-row update allowed Yes
- SHow New Rows at Top Yes
2.2 Generate the JHeadstart application
2.3. Go to the Page which you'd like to enter in insert mode and click on 'Go to Page Definition'
Add in the <executable> part the following code
<invokeAction Binds="CreateAanmakenAdminEenheden" id="invokeCreate" Refresh="renderModel"
RefreshCondition="${!adfFacesContext.postback and empty
bindings.exceptionsList}"/>
(see also http://download-uk.oracle.com/docs/html/B25947_01/web_form006.htm for more information)
Make sure that the Binds part has the sam name as the <action id='Create...' which is available in the bottom part of the page definition.
My question is
How can we avoid this last post-generation step, the addition of code to the Page Definition file.
I know you can unclick the 'Generate Page Definition' property in JHeadstart, but that introduces a risk that functionality is not included after changing the page.
Regards Leon
By the way, this is a lot of of work, just for entering a page in directly in insert mode. I think there can be made some improvement in ADF to accomodate this (a lot wanted) functionality.....

Answer 1

Navid,
You need to create custom templates to achieve this. The easiest way to get everything in place, is to first generate the group as insert-only (without search and query).
This will generate the following:
- in the page definition the ControllerClass property will be set to a JSF EL expression, something like #{EmpWizardPageLifecycle}
- in the group beans config file, two beans are generated like this:
<managed-bean>
<managed-bean-name>EmpWizardPageLifecycle</managed-bean-name>
<managed-bean-class>oracle.jheadstart.controller.jsf.lifecycle.JhsPageLifecycle</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>beforePrepareRenderMethods</property-name>
<list-entries>
<value-class>oracle.jheadstart.controller.jsf.bean.InvokeMethodBean</value-class>
<value>#{CreateEmpWizardMethod}</value>
</list-entries>
</managed-property>
<managed-property>
<property-name>validateADFModel</property-name>
<value>false</value>
</managed-property>
</managed-bean>
<managed-bean>
<managed-bean-name>CreateEmpWizardMethod</managed-bean-name>
<managed-bean-class>oracle.jheadstart.controller.jsf.bean.InvokeMethodBean</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>methodBinding</property-name>
<!-- we leave out the JSF EL brackets, to prevent premature evaluation of the expression -->
<value>bindings.CreateEmpWizard.execute</value>
</managed-property>
<managed-property>
<property-name>executeCondition</property-name>
<!-- we leave out the JSF EL brackets, to prevent premature evaluation of the expression -->
<value>jsfNavigationOutcome=='StartEmpWizard' or param.StartEmpWizard=='true'</value>
</managed-property>
</managed-bean>
The executeCondition does the trick here: it causes the page to start in insert mode when the navigation outcome is 'StartEmpWizar' or there is a request param named StartEmpWizard with value true.
So, to get this functionality in a normal queryable group, you need to create a custom template for the groupFacesConfig.vm and add the two bean defs as above. And to get the ControllerClass property generated correctly, you can use the advanced group-level property Page Lifecycle class and set this to #{EmpWizardPageLifecycle}.
(and replace EmpWizard with your own group name)
Steven Davelaar,
JHeadstart Team.