So this document will need to have a getter that returns a date, a long, a decimal, and a string. What other data types do we want to test against?

James, I've committed my current work thus far to the 1.0.1.1 branch. See my comment on the parent issue for a list of the added and updated files.

Thanks; I'm taking a look.

Looks great. I think I will add some boolean and sql date versus timestamp stuff to test to the document since those are edge cases in the dd searchable attribute stuff.

Everything in the test looks great, though I'm curious where the data dictionary file for the new document is loaded into the data dictionary (I'm probably missing some test module config...)

Saw where the data dictionary stuff gets loaded.

I believe the DD files are loaded by the "testModule" bean defined in KnsTestSpringBeans.xml. Also, I'm currently modifying the unit test so that it follows the format of my other searchable attribute tests, and I'll have it use the bootstrapped data once that is set up. And thanks for adding the extra boolean and date/timestamp fields for covering extra use cases; I'll test those out in my unit tests as well.

James, I just realized something that might need to be added to the new document's database table. Do you know if the DB table needs FDOC_NBR, OBJ_ID, and VER_NBR fields as well?

It does. I'll need to make changes for my extra field as well - should I just go ahead and add these?

Yes, that's fine. Thanks!

Okay, Chad, I committed the changes.

My version of Oracle (XE based on 10g) didn't like "BIGINT" - I changed those to NUMBER(14) in kns.sql - hope that's okay.

James, I've just submitted a couple changes of my own, most notably to the unit test class itself. However, I've left the @Ignore annotation present on the unit test method for now because I'm getting this error when attempting to route the test document:

• SQLException during execution of sql-statement:
• sql statement was 'SELECT A0.DOC_HDR_ID,A0.OBJ_ID,A0.VER_NBR,A0.ACCT_NUM,A0.ACCT_OWNR,A0.ACCT_BAL,A0.ACCT_OPN_DAT,A0.ACCT_STAT,A0.ACCT_UPDATE_DT_TM,A0.ACCT_AWAKE FROM ACCT_DD_ATTR_DOC A0 WHERE A0.DOC_HDR_ID IN '
• Exception message is [ORA-00942: table or view does not exist
  ]
• Vendor error code [942]
• SQL state code [42000]

Any idea why it can't find the table (if that's what is causing this problem)? Or is this something that we won't need to deal with once the bootstrapping is fully configured?

Well, there's a question I wish I knew the answer to : - >

Do we need to run the kns.sql ourselves, perhaps on some test data source? I'm trying the test locally...

Chad, I'm at a point where I can resolve this, right? Thanks!

Yes, you can go ahead and resolve this; I have plenty of test documents to work with now. Thanks for your help!

Thanks Chad.