Keyword expansion for TAPI's

Question

I extended keyword expansion also for TAPI's. The headstart CAPI generator utility and the keyword expansion module were changed such that a revision label is now added to both the TAPI and the CAPI.
The revision label added to the TAPI reflects the version of it's corresponding table in the designer repository whereas the revision label of the CAPI reflects the version of the CAPI PL/SQL Definition in the repository.
The revision label added to the TAPI has the following format :
REVISION_LABEL CONSTANT VARCHAR2(240) := '$revision 1.2$';
The headstart CAPI generator was changed in order to add an input parameter to the CAPI function 'revision' under the name 'p_tapi_or_capi' and is of type varchar2. When called as <CAPI package>.revision ('TAPI') it returnes the revision string of the TAPI (based upon the same table as the CAPI).
When called as <CAPI package>.revision ('CAPI') it returnes the revision string of the CAPI.
Here's how it works :
The headstart CAPI generator creates a CAPI with a modified revision function as described above. The revision function takes an input parameter to return either CAPI or the TAPI revision label.
When called with 'CAPI' it returnes the local REVISION_LABEL string present in the CAPI body. When called with 'TAPI' it returnes the tapi revision label <TAPI package>.REVISION_LABEL. How do these revision labels end up in the TAPI and the CAPI??
The headstart CAPI generator utility was changed to do the following things:
1) It creates a unique key constraint for the table definition under the name 'REVISION_LABEL'.
The unique key constraint is generated without correponding column elements.
The property 'Complete' is set to 'Y'.
The property 'Validate in' is set to 'Server'.
The property 'Error message' is set to '$revision'. (The expansion keyword).
When the table definition is checked in, the error message property of the table definition is
expanded since it contains the keyword '$revision$'. (NOTE : To this end the standard keyword expansion
module was modified!!)
With the additional unqiue key constraint, the TAPI can be generated. It will contain the constant
REVISION_LABEL CONSTANT VARCHAR2(240) := '$revision x.y$' ment as a user error message string to be
raised when the unique key constraint is violated. However the constraint itself will not be generated
for the table since the columns for the constraint are missing. The constraint is not validated in
the client!
2) It adds a line to the CAPI PL/SQL Definition's property 'Private Declaration' wit the following
syntax :
REVISION_LABEL constant varchar2 (20) := '$revision$'; When checked in the keyword will be expanded.
When the CAPI is generated the private declaration will be added to the CAPI body, hence the CAPI will
have a local constant reflecting the revision of the CAPI.
3) The headstart CAPI utility adds a revision function to the CAPI with the additional 'p_tapi_or_capi'
parameter.
Since the changes in the headstart and keyword expansion code are to much to be summoned here, I will make them available for use by mailing them to Oracle.
With kind regards,
Jan Wicherink
NOTE : The headstart CAPI generator changes of course will only work in combination with keyword exapansion!!

Answer 1

Jan,
Well done!
I logged this as Headstart enhancement request 2586375,
though we must find a solution that keeps the old functionality if you don't do keyword expansion.
kind regards,
Sandra