Urgent:JPublisher's default typemapping for PL/SQL Boolean not working

Question

I have a procedure that accepts a boolean.
I have created this procedure on 2 oracle database installations. One is on Oracle8i and the other on Oracle9i.
I invoke JPublisher with the following jpub.properties file:
jpub.user=scott/tiger
jpub.url=jdbc:oracle:thin:@database:1521:oracle
jpub.dir=C:\Jpub
jpub.package=BooleanMapping
jpub.plsqlmap=always
jpub.plsqlfile=C:\Jpub\BoolProc.sql
jpub.plsqlpackage=BoolWrapper
jpub.adddefaulttypemap=BOOLEAN:boolean:INTEGER:SYS.SQLJUTL.INT2BOOL:SYS.SQLJUTL.BOOL2INT
This is the output of JPublisher from SCOTT schema in 8i and 9i databases respectively:
Output from 8i:
J2T-137, WARNING: mapping BOOLEAN:boolean was redefined to BOOLEAN:boolean.
SCOTT.<top-level scope>
Output from 9i:
J2T-137, WARNING: mapping BOOLEAN:boolean was redefined to BOOLEAN:boolean.
SCOTT.<top-level scope>
J2T-138, NOTE: Wrote PL/SQL package BoolWrapper to file C:\Jpub\BoolProc.sql
Why is the PL/SQL wrapper file not created in case of Oracle8i database?
Is there a way to enable this?
NB: I had to do a few workarounds to make this happen on 8i database.
I copied over the .jar library files from sqlj folder from 9iHome to 8iHome. I also copied the jpub.exe from the bin folder. This is because the JPublisher in 8i does not accept addtypemap, defaulttypemap kind of arguments.

Answer 1

Alex,
For the predicate groups that are indexed/stored, the exact operator types (as in equality, inequality, like etc) that are indexed are specified while assigning the default index parameters. In the following example, exf$indexoper is used to specify the list of indexed operators.
BEGIN
  DBMS_EXPFIL.DEFAULT_INDEX_PARAMETERS('Car4Sale',
    exf$attribute_list (
       exf$attribute (attr_name => 'HorsePower(Model, Year)',
                      attr_oper => exf$indexoper('=','<','>','>=','<='),
                      attr_indexed => 'FALSE')    --- stored predicate group
END;
/You can find more information about exf$indexoper at
http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28419/t_expfilobj.htm#ARPLS153
Could you confirm that you chose to index 'is null' and 'is not null' while assigning the default index parameters ? This information is available in OPERATOR_LIST column of the USER_EXPFIL_DEF_INDEX_PARAMS view.
Hope this helps,
-Aravind.