Extracting Schemas in Sections
You can use the JadeBatchExtract application in the jadclient program to extract schemas in sections. This enables you to store schemas in Subversion or in any other suitable version control system in smaller chunks than complete schema files.
To extract schemas in sections, specify the optional "<sections>" argument in the JadeBatchExtract application for the Every or EL, Multiple or ML, and Single or SL extract arguments.
The following example extracts in sections every schema to directory C:\temp2\userSchemas.
jadclient path=e:\jadesystems\jade\system ini=c:\jade\system\jade.ini app=JadeBatchExtract schema=JadeSchema server=singleUser startAppParameters Every C:\temp2\userSchemas\schemas.mul "<sections>"
When a schema is extracted in sections, a schema-name folder is created in addition to the schema‑name.scm and schema-name.ddb
The Types subfolder contains a *.cls file for each type (that is, class, primitive type, and interface) in the schema. If a class is a Form class, there is also a .ddx file, which is an XML format form representing the layout of the form in every locale.
The .sec files, which do not have to be present, can be broken into the following two types.
-
Those that represent the corresponding section of the .scm file, as follows.
-
schemaDefinitions.sec
-
importedPackageDefinitions.sec
-
constantDefinitions.sec
-
localeDefinitions.sec
-
libraryDefinitions.sec
-
externalFunctions.sec
-
inverseDefinitions.sec
-
databaseDefinitions.sec
-
schemaViewDefinitions.sec
-
_exposedListDefinitions.sec
-
exportedPackageDefinitions.sec
-
externalFunctionSources.sec
-
-
Those that contain a list of types whose .cls file contributes to the corresponding section of the .scm file, as follows.
-
typeHeaders.sec
-
interfaceDefs.sec
-
membershipDefinitions.sec
-
typeDefinitions.sec
-
externalKeyDefinitions.sec
-
memberKeyDefinitions.sec
-
typeSources.sec
-
If addedFiles and deletedFiles files are created, these contain a list of .cls or .ddx files that have been added or deleted during the current extract, by comparing with the files that were present before the extract began. These files can be useful when you need to add new files to or delete files from the version control system. For example, in Subversion you could use these as arguments to the delete and add commands of svn, as shown in the following examples.
svn delete --targets deletedFiles svn add --targets addedFiles