ADF UIX doSelect override with PL/SQL fails to allow insert

Question

I've been trying to create an ADF-UIX web app for simple insert/update/delete of records to a table.
The schema simply has 2 tables - master and detail where the detail pk is made up of the master id and a start date:
CREATE TABLE master (
id NUMBER NOT NULL,
name VARCHAR2 (10) NOT NULL,
CONSTRAINT pk_master
PRIMARY KEY ( id ));
CREATE TABLE detail (
id NUMBER NOT NULL,
start_date DATE NOT NULL,
name VARCHAR2 (10) NOT NULL,
description VARCHAR2 (100),
CONSTRAINT pk_detail
PRIMARY KEY ( id, start_date ));
ALTER TABLE detail ADD CONSTRAINT d_m_fk FOREIGN KEY (id) REFERENCES master(id)
This works fine when I create it in a similar manner to that described in the "Complete ADF UIX Application ..." tutorial doc.
http://www.oracle.com/technology/products/jdev/collateral/tutorials/9050/adfuix_tut.html
I then tried to override the ADF doSelect and doDML methods as outlined in ADF_BC_StoredProcedures.zip example app allowing me to use PL/SQL stored pkg for dml.
http://www.oracle.com/technology/sample_code/products/jdev/10g/ADF_BC_StoredProcedures.zip
On trying to insert a new row my web app now fails with a null pointer exception when I press the Submit button. The app calls doSelect->handleStoredProcSelect which fails to get the value of a column.
void handleStoredProcSelect() {
CallableStatement st = null;
try {
String stmt = "BEGIN test_api.do_select(?,?,?,?,?); END;";
DBTransaction tr = getDBTransaction();
st = tr.createCallableStatement(stmt,1);
## This line works, I'm guessing because the value is populated from the master record I've selected in the form ...
st.setLong(1,getTestId().longValue());
##FAILS HERE st.setDate(2,getStartDate().dateValue());
Update,delete still work ok. And if I run the test app (right click on AppModule and select Test) all works ok.
I'm not sure why doSelect is called on an insert so I commented out:
doSelect
handleStoredProcSelect
handleStoredProcLock
compareOldAttrTo
Web App now lets me insert as expected.
So finally ....my question is:
Whilst the app now works does commenting out the doSelect leave me open to problems I haven't thought off
and if not if you did want to use it how can you allow inserts?
Any thoughts or similar experiences appreciated ...
Cheers
Ian

Answer 1

I've been trying to create an ADF-UIX web app for simple insert/update/delete of records to a table.
The schema simply has 2 tables - master and detail where the detail pk is made up of the master id and a start date:
CREATE TABLE master (
id NUMBER NOT NULL,
name VARCHAR2 (10) NOT NULL,
CONSTRAINT pk_master
PRIMARY KEY ( id ));
CREATE TABLE detail (
id NUMBER NOT NULL,
start_date DATE NOT NULL,
name VARCHAR2 (10) NOT NULL,
description VARCHAR2 (100),
CONSTRAINT pk_detail
PRIMARY KEY ( id, start_date ));
ALTER TABLE detail ADD CONSTRAINT d_m_fk FOREIGN KEY (id) REFERENCES master(id)
This works fine when I create it in a similar manner to that described in the "Complete ADF UIX Application ..." tutorial doc.
http://www.oracle.com/technology/products/jdev/collateral/tutorials/9050/adfuix_tut.html
I then tried to override the ADF doSelect and doDML methods as outlined in ADF_BC_StoredProcedures.zip example app allowing me to use PL/SQL stored pkg for dml.
http://www.oracle.com/technology/sample_code/products/jdev/10g/ADF_BC_StoredProcedures.zip
On trying to insert a new row my web app now fails with a null pointer exception when I press the Submit button. The app calls doSelect->handleStoredProcSelect which fails to get the value of a column.
void handleStoredProcSelect() {
CallableStatement st = null;
try {
String stmt = "BEGIN test_api.do_select(?,?,?,?,?); END;";
DBTransaction tr = getDBTransaction();
st = tr.createCallableStatement(stmt,1);
## This line works, I'm guessing because the value is populated from the master record I've selected in the form ...
st.setLong(1,getTestId().longValue());
##FAILS HERE st.setDate(2,getStartDate().dateValue());
Update,delete still work ok. And if I run the test app (right click on AppModule and select Test) all works ok.
I'm not sure why doSelect is called on an insert so I commented out:
doSelect
handleStoredProcSelect
handleStoredProcLock
compareOldAttrTo
Web App now lets me insert as expected.
So finally ....my question is:
Whilst the app now works does commenting out the doSelect leave me open to problems I haven't thought off
and if not if you did want to use it how can you allow inserts?
Any thoughts or similar experiences appreciated ...
Cheers
Ian