Persistency and transaction problem

Question

In CAF, if my model has a cardinality 0..1 (nullable in database), how can I make the generated create entity service to accept the parameters that are optional? I found that CAF will drop off those parameters by default.
Moreover, is it strange that both update and delete will accept a BO as parameter while the create is using parameters instead? Is there any rational behind?
At last, can someone give me a reference to the general overview of transaction management in CAF?
Thanks!

Answer 1

Hi,
Are you using NW 7.0?.
In this version create method will take only mandatory attributes as arguments. But this is enhanced in CE 7.1.In CE 7.1, you can declare an optional(0..1) attribute as an argment  of create.
Transaction management :
Tranasaction management of CAF is nothing but J2EE Transaction management only.
Follow this links
[link1 |http://help.sap.com/saphelp_nwce10/helpdata/en/44/b79f1e352056a4e10000000a1553f6/content.htm]
[link 2|http://help.sap.com/saphelp_nwce10/helpdata/en/45/01a2b031c16c30e10000000a114a6b/content.htm]
For your second question, I don't know whether there is a special reason.But one thing i can say that is :
Initially,we can create a record with all the mandatoryor(optional also)
and later we can update it with remaining attribute.
Sampath