What's New in Sculptor
Version 1.4.x
Version 1.4.1 was released October 6, 2008.
The most important features of this release:
- JSF dialect of CRUD GUI.
- Possibility to split model.design into several files.
- Upgrade to oAW 4.3
- Support for Eclipse 3.4 Ganymede. Europa 3.3.2 is also supported.
Fixed issues:
JSF dialect still in beta
There are some known issues with the JSF dialect of the CRUD GUI. JSF will be our future default choice and we are working hard to make it good. Please, try it and report issues
Migration
You have to upgrade to oAW 4.3, see Installation guide.
If you start from scratch you use the maven archetypes to create project structure, and you can of course skip these migration instructions.
If you have an existing project you need to do the following tasks.
1. Change sculptor.version in the pom.xml of the parent project.
<sculptor.version>1.4.1</sculptor.version>
2. Change fornax-oaw-m2.version in the pom.xml of the parent project.
<fornax-oaw-m2.version>2.1.0</fornax-oaw-m2.version>
3. The fornax maven repository has moved and therefore you need to change the repositories settings in pom.xml of the parent project. It should be like this:
<repositories>
<repository>
<id>releases.archiva.fornax-platform.org</id>
<name>Archiva Managed Release Repository</name>
<url>
http: </url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
<repository>
<id>snapshots.archiva.fornax-platform.org</id>
<name>Archiva Managed Snapshot Repository</name>
<url>
http: </url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
<repository>
<id>java.net</id>
<url>http: <layout>legacy</layout>
</repository>
</repositories>
<pluginRepositories>
<pluginRepository>
<id>releases.archiva.fornax-platform.org</id>
<name>Archiva Managed Release Repository</name>
<url>
http: </url>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>false</enabled>
</snapshots>
</pluginRepository>
<pluginRepository>
<id>snapshots.archiva.fornax-platform.org</id>
<name>Archiva Managed Snapshot Repository</name>
<url>
http: </url>
<releases>
<enabled>false</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
</pluginRepository>
</pluginRepositories>
4. Thereafter you need to run mvn eclipse:eclipse from the parent project to update the classpath of the Eclipse projects.
5. If you have an existing project and need correction of "CSC-207 Not possible to deploy several applications" you have to change the pom.xml in the ear project. Change version of maven-ear-plugin to 2.3.1 and add the following
You have to upgrade to oAW 4.3, see Installation guide.
jboss element to the configuration:
<plugin>
<artifactId>maven-ear-plugin</artifactId>
<version>2.3.1</version>
<configuration>
<generateApplicationXml>true</generateApplicationXml>
<jboss>
<loader-repository>${groupId}.${artifactId}:archive=${artifactId}.ear</loader-repository>
</jboss>
Version 1.3.x
Version 1.3.1 was released April 11, 2008.
The most important feature of 1.3 is a totally new metamodel for the CRUD GUI. In version 1.1 we implemented theyou need to change the version of fornax-oaw-m2-plugin. You have to change the pom.xml in the parent project.
<fornax-oaw-m2.version>2.1.0</fornax-oaw-m2.version>
If you have an existing project CRUD GUI without a separate gui metamodel. The gui generation was using the business tier model. This was a good start, but the experience was that the templates and helper extensions became rather complicated. A special purpose gui metamodel simplified the templates and moved some of the logic to a transformation instead. This is important as we see the need for different dialects of the GUI. In the initial version we are using Spring WebFlow and JSP. We have also started a JSF dialect. More is likely to come, such as rich client (RCP). Another motivation for the gui metamodel is the possibility to customize the GUI by using a separate DSL (in next release).
The release also contains several other improvements and new features.
Some more bug fixes in 1.3.1.
Migration
If you start from scratch you use the maven archetypes to create project structure.
For existing projects you have to do some migration.
1. workflow.oaw
You need to rename workflow.oaw in web project to workflow-gui.oaw and also change the reference to this file in pom.xml in the same web project:
<plugin>
<groupId>org.fornax.toolsupport</groupId>
<artifactId>fornax-oaw-m2-plugin</artifactId>
<version>${fornax-oaw-m2.version}</version>
<configuration>
<workflowDescriptor>workflow-gui.oaw</workflowDescriptor>
<checkResources>
<checkResource>
../fornax-cartridges-sculptor-examples-library/src/main/resources/model.design
</checkResource>
</checkResources>
<properties>
<modelFile>model.design</modelFile>
<appProject>${artifactId}</appProject>
</properties>
</configuration>
<executions>
<execution>
<phase>generate-sources</phase>
<goals>
<goal>run-workflow</goal>
</goals>
</execution>
</executions>
</plugin>
2. Rename foreign key columns
The naming conventions for foreign key columns in the generated DDL file has been changed. Basically the new naming is based on names of the references, instead of names of the referred objects. Make a copy of previously generated DDL file and compare that to the new one see what has been changed. Rename columns in existing database, if you can't recreate the database.
ALTER TABLE MOON CHANGE COLUMN PLANET_ID PLANET BIGINT NOT NULL
ALTER TABLE DEPARTMENT CHANGE COLUMN EMPLOYEE_ID HEADOFDEPARTMENT BIGINT
With this version it is possible to define database table and column names in the DSL, i.e. if you can't change the database you can define the old names. See Advanced Tutorial.
Version 1.2.x
Version 1.2.0 was released December 9, 2007.
It is a technical upgrade of several core products such as Eclipse and openArchitectureWare. You have to do
Closed
Resolved
