[Aplaws-devel] Create SQL problem with Aplaws+ Beta Release

[<Paw...@ne...>]

When creating a new application using the Aplaws+ Beta Release of February 
2004 and creating new content types in this application the ccm load 
(without option or specifically with the --schema option) fails with the 
following error message:
        > 2004-02-26 10:13:35,602 [ main] INFO  packaging.Loader - Loading 
schema for edemocracy
        >Exception in thread "main" java.lang.IllegalArgumentException: no 
such file: [application]/oracle-se-create.sql
        >        at 
com.arsdigita.installer.SQLLoader.load(SQLLoader.java:54)
        >        at 
com.arsdigita.installer.SQLLoader.load(SQLLoader.java:36)
        >        at 
com.arsdigita.loader.PackageLoader.load(PackageLoader.java:99)
        >        at 
com.arsdigita.packaging.Loader.loadSchema(Loader.java:89)
        >        at com.arsdigita.packaging.Load.run(Load.java:315)
        >        at 
com.arsdigita.packaging.MasterTool.main(MasterTool.java:90)

The Ant deploy job do create the required and valid SQL to create the 
table and constraints for a content type, but they are located and named 
as:
        > [application]/build/sql/[application]/ddl/oracle-se/create.sql
        > [application]/build/sql/[application]/ddl/oracle-se/deffered.sql
        > 
[application]/build/sql/[application]/ddl/oracle-se/drop-constraints.sql
        > 
[application]/build/sql/[application]/ddl/oracle-se/drop-tables.sql
        > 
[application]/build/sql/[application]/ddl/oracle-se/table-[table-name]-auto.sql

Executing the table-[table-name]-auto.sql and deffered.sql manually create 
the required structure and afterwards doing ccm load with the --config and 
--data option succed loading the application, whereas a ccm load wihtout 
options or ccm load with the --schema options now fails because the table 
already exists

Paw Hammerlund Andersen 
Principal Consultant, http://www.net2s.com