DataControl does not expose a Commit operation

Question

Hi all,
I'm using ADF & JDeveloperStudio Edition Version 11.1.1.3.0 PS2.
I'm trying to insert a new row in my database from an input screen, using a task flow.
My task flow has:
- Behaviour -> Transaction set to Always Begin New Transaction: to create a new transaction when the flow starts.
- method activity to call the Create operation from my DataControl
- view activity for data-entry screen.
- view activity for read-only, confirm screen to display the entered data and provide a Confirm button to proceed with inserting the data to the database.
- return activity: has Behaviour -> End Transaction set to Commit to complete the insertion to the database. NOTE: I did not drag the Commit operation from my DataControl to the command button that navigates to this return activity—I explain below.
Problem:
When I hit the Confirm button on the confirm screen I get an HTTP 404 Error (The server has not found anything matching the Request-URI.)
Nothing displays on either the Messages or Running: IntegragedWebLogicServer; nothing appears in the DefaultServer.log.
I'm following [this section|http://download.oracle.com/docs/cd/E14571_01/web.1111/b31974/web_form.htm#sthref1906] from the Fusion Developer's Guide. I have deviated from the instructions on point 6 ("Because you need to commit the new data, the application needs to execute the commit operation of the data control. To do this, you can add a button that navigates to a return activity that calls the commit operation.") because my DataControl does not have a Commit operation. I suspect this is the cause of my problem.
My DataControl was generated from a Session Bean, which was created from an Entity EJB, which was in turn generated from my database table (I have SELECT and INSERT grants on the table. All this is correct, I believe.
I've compared my DataControl to that from JDeveloper's Cue Cards tutorial "Build a Web Application with EJB, JPA and JSF"; that tutorial's DataControl does not have a Commit operation either, but the tutorial does not try to use task flows.
Any ideas as to why
- I'm getting the error when I try to navigate from the confirm page to the return activity responsible for committing the insertion to the database?
- my DataControl does not exhibit a Commit operation?
Thanks for your help.
Regards,
Ken.

Answer 1

Hi Shay,
Thanks for response.
I've tried your suggestion to call the persist... transaction method.
Here are my steps:
- Started with a fresh, even simpler task flow with only two activities: a view activity to display an input form, and a method activity to call the persistMyEntity(...) transaction method.
- Added method activity, and dropped persistMyEntity(...) from my data control onto it. (Data control created from Session Bean.)
- persistMyEntity(...) takes one parameter, a MyEntity object: I need to identify this parameter object using EL. There is no such object existing in any binding context at this point.
- Added managed bean, of type MyEntity to the task flow in page flow scope. Updated the EL for the persistMyEntity(...) parameter to refer to this managed bean in page flow scope - *#{pageFlowScope.myEntity}*.
- Added a view activity to task flow, and created the *.jspx* for it.
- Dropped input text components onto the page for each of the entity's attributes that I want to persist to the database.
- Manually bound the value for each input text component to the corresponding attribute in the managed bean - *#{pageFlowScope.myEntity.myAttribute}*
When I run my task flow, I get following exception: oracle.jbo.NoDefException: JBO-25058: Definition myAttribute of type Attribute is not found in myAttribute.
I would have thought I could expand the persistMyEntity(...) node within the Data Control panel and drag its parameter onto the screen as an ADF Form, with ADF looking after binding; then drag the persistMyEntity(...) method onto the method activity. My gut tells me I shouldn't have to add a managed bean to the task flow, of type required by the persistMyEntity(...) method, then manually bind it to the input text fields of the screen. It just seems 'wrong'.
Is my approach incorrect?
Many thanks,
Ken.