Add functionality Via Coding

Question

Hi,
I have made a page to input new values in 2 View Objects (Dept & Employee) using "Create Insert" Operation for both VO's using a bean as coded below:
public String cb10_action() {
BindingContainer bindings = getBindings();
OperationBinding operationBinding2 = bindings.getOperationBinding("CreateInsert1");
Object result2 = operationBinding2.execute();
if (!operationBinding2.getErrors().isEmpty()) {
return null;
OperationBinding operationBinding = bindings.getOperationBinding("CreateInsert");
Object result = operationBinding.execute();
if (!operationBinding.getErrors().isEmpty()) {
return null;
return null;
. Now I need to submit the values entered in the Form but am unable to do so . Even if I drag "Commit" operation on button it gives foreign key error. Is there any code to submit the Value in 1 VO and then in 2nd VO like the above...
And also what if I want to route to next page after submitting Values. what code should I write.
Thanks ,
MB

Answer 1

I only quote the docs:
By default, when you commit the transaction the entity objects in the pending changes list are processed in chronological order, in other words, the order in which the entities were added to the list. This means that, for example, if you create a new Product and then a new Supplier related to that product, the new Product will be inserted first and the new Supplier second.
When two entity objects are related by a composition, the strict chronological ordering is modified automatically to ensure that composed parent and child entity rows are saved in an order that avoids violating any constraints. This means, for example, that a new parent entity row is inserted before any new composed children entity rows.
If your related entities are associated but not composed, then you need to write a bit of code to ensure that the related entities get saved in the appropriate order.
and etc...
Straight copy-and-paste from the link I posted. Further on it describes how, in detail, to write code so that the parent entity posts first.
If you have a composition association => no need to do anything.
If you do not have a composition association => you can force the parent to post first.
So, I think you have it backwards, Suganth.
MB, Are you sure that you are using an Employee VO instance that is a child of the Department VO instance in your application module (they should appear as the employee nested inside the department in the data control panel) - this could also be your problem.
John
John