Skip to end of metadata
Go to start of metadata

What's New in Sculptor

Version 2.1.x

Version 2.1.0 was released January 21, 2012.

Some highlights of the release:

  • JPA 2.0
  • Convenient ways to query the database by defining queries in the model, see documentation in Advanced Tutorial
  • Support for OpenJPA
  • Validation based javax.validation api
  • Builders with fluent interface for construction of domain objects, see documentation in Advanced Tutorial
  • Major performance improvement in generation by suppressing invisible logging in beautifier

Complete Release Notes.

Migration

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.

Update Eclipse and DSL Editor Plugin
Install Eclipse Indigo and latest Sculptor plugins as described in Installation Guide.

Change version
Change sculptor.version in the pom.xml of the parent project.

JPA 2.0

Sculptor Version 2.1.0 supports the JPA 2.0 persistence api, which is now the default.

Sculptor is backward compatible with JPA 1.0. If you like to stay with JPA 1.0 add the jpa.version to your sculptor-generator.properties file.

Otherwise you have to upgrade to a JPA 2.0 compatible jpa provider, e.g. hibernate 3.6.x.

Change hibernate.version and the hibernate entitymanager dependency in the pom.xml of your project.

Remove some unnecassary hibernate properties and dependencies

Remove the ununsed jpa.version and related dependencies in the pom.xml of your project. 

If you use the joda datetime api in your project upgrade the joda dependencies

Validation

Sculptor Version 2.1.0 now uses the javax.validation api. If you are using generated validations it is necessary to upgrade to a compatible validation provider, e.g. hibernate validator 4.1.x.

Change hibernate.validator.version in the pom.xml of the parent project.

Change log settings for generator

The logback configuration is important for the performance of the hybridlabs-beautifier.
In your project pom.xml <configuration> section of fornax-oaw-m2-plugin you should add the following settings:

mongo-java-driver 2.7.2
If you use MongoDB you should be aware of that we have upgraded the mongo-java-driver to version 2.7.2. You should generate new Eclipse .classpath with mvn eclipse:eclipse. It is a transitive dependency from fornax-cartridges-sculptor-mongodb.

Version 2.0.x

Version 2.0.0 was released March 13, 2011.

This release contains:

  • RESTful Services
  • Mixin composition with traits
  • Spring Remoting
  • Upgrade to Xtext 1.0 and Eclipse Helios
  • Upgrade to Maven 3
  • Upgrade to Spring 3.0
  • Upgrade of versions for Google App Engine, Apache Camel, Spring Integration, Spring Web Flow, Drools, MongoDB, JBoss, Ehcache, Joda
  • Change of logging API to SLF4J
  • Removal of deprecated features
  • Support DataTransferObject in CRUD GUI
  • Persistent DomainEvent
  • And a long list of other bug fixes and improvements...

Complete Release Notes.

Install new Sculptor DSL editor from update site. See Installation Guide.

Migration

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.

As user of previous versions you should not be afraid of upgrading to version 2.0. It contains a lot, but we have, as always, performed the changes carefully, with backwards compatibility or with well defined migration instructions. Don't hesitate to ask us in the Forum if you have any trouble with the migration.

Java 6
In case you are still using Java 5 you need to move to Java 6. Sculptor 2.0 doesn't support Java 5.

Maven 3
It is still possible to use Maven 2.2.x, but we encourage you to upgrade to Maven 3.0.x. The backwards compatibility is very good so it shouldn't be much trouble.

Update Eclipse and DSL Editor Plugin
Install Eclipse Helios and latest Sculptor plugins as described in Installation Guide.

Change version
Change sculptor.version in the pom.xml of the parent project.

Change Maven Repositories

Fornax Maven repository has been changed to Nexus at a new location. Update <repositories> section to use the following instead of old archiva.fornax-platform.org:

Similar for <pluginRepositories>:

Update the jboss.org repository also:

You can remove legacy java.net repository, since it is included in http://fornax-platform.org/nexus/content/repositories/public

Change Dependencies

Change the following version properties in pom.xml of the parent project. Thereafter you should generate new Eclipse .classpath with mvn eclipse:eclipse.

You must also change version of the JUnit dependency, to 4.6.

The artifactId of Ehcache is changed to ehcache-core:

Change dependency to joda-time-hibernate:

If you use JSF GUI you should change version of jsf-facelets to 1.1.15.

Due to a bug FACELETS-364 in jsf-facelets to 1.1.15 you need to define begin and step in c:forEach tags. Add that in template.xhtml:

You might have written other forEach elements in other files also.

You should also add this to your web.xml

If you use pure-ejb3 you should change dependency of openejb:

If you are using Spring and deploying as war file to JBoss 5.1.0.GA you need to add classifier without-ejb to the fornax-cartridges-sculptor-framework dependency.

If you use MongoDB you should be aware of that we have upgraded the mongo-java-driver to version 2.4. You should generate new Eclipse .classpath with mvn eclipse:eclipse. It is a transitive dependency from fornax-cartridges-sculptor-mongodb.

If you use Apache Camel you should change version property to:

If you use Spring Integration you should change the dependency of previous artifactId org.springframework.integration to:

If you use Google Appengine you should migrate to version 1.4.2 with these changes in pom.xml

  • appengine.version 1.4.2
  • datanucleus-appengine.version 1.0.8.final
  • remove exclude com.google.appengine:appengine-local-runtime from maven-eclipse-plugin
  • remove exclude com.google.appengine:appengine-tools-api from maven-eclipse-plugin
  • remove dependency appengine-local-runtime
  • remove dependency appengine-tools-api

Due to a bug in appengine-testing 1.4.2 we must use 1.4.2a for appengine-testing.

Update the GAE Eclipse plugin from update site: http://dl.google.com/eclipse/plugin/3.6

Update to new workflow system and new file layout for generator
In pom.xml change version of oAW plugin

and whole oAW plugin section to

Add following line to '.ignore-checksum.txt'

Create new directory 'src/main/resources/generator'. Create there new file 'Workflow.mwe2' with following content:

Move all generator specific files 'templates/SpecialCases.xpt', 'extensions/SpecialCases.ext' and 'sculptor-generator.properties' from 'src/main/resources' directory to 'src/main/resources/generator' subdirectory. Go to 'src/main/resources' directory and run following:

After this step you will have 4 files in 'src/main/resources/generator' (Workflow.mwe2, SpecialCases.xpt, SpecialCases.ext, sculptor-generator.properties).
Now you can remove empty directories 'templates' and 'extensions' and also old workflow file 'workflow.mwe' from 'src/main/resources'.

Run mvn eclipse:eclipse from the parent project to update Eclipse projects.

Static imports in JUnit tests
You might need to add static imports for assert methods in your JUnit tests.

Integration with SLF4J
New version was moved from log4j logging to SLF4J with Logback backend. SLF4J allow many backends and also have special bridges for many (legacy) logging frameworks. Following points lead to setup where you have log4j and commons-logging directed to SLF4J and through this to SLF4J native backend - Logback. Other setups are also feasible, check previous links. However for now SLF4J with Logback is considered to be best logging framework available.
1. Remove all references to commons-logging and log4j from pom.xml dependencies. Usually you have to REMOVE something like this:

2. It is also important to not include commons-logging and log4j as a transitive dependency. For example you must use exclude in the following dependencies:

M2Eclipse plugin or mvn dependency:tree are invaluable tools when analyzing dependencies.

3. Merge following to properties section of you pom.xml (check if you don't have already such properties, specially slf4j.version)

4. Add following to dependencies section of pom.xml

5. Initial configuration file for Logback will be generated in src/main/resouces and src/test/resources

Now all logging from commons-logging, log4j are redirected through SLF4J. Other setups are feasible, check SLF4J configuration guide. For example you can use log4j as backend.

When using log4j as backend you should not use log4j-over-slf4j, jcl-over-slf4j and logback-classic.

Even though not necessary when you use the bridge, it is recommended that you migrate your hand written log statements to use SLF4J instead of commons-logging. The API is very similar, so it isn't difficult. You can also use the migration tool.

6. Generate new Eclipse .classpath with mvn eclipse:eclipse.

Changed syntax in GUI DSL
A small non-backwards compatible change to the gui dsl (.guidesign) has been done to be able to improve code completion. You must add - in front of view properties.

New DSL keywords

We have added a few new keywords in the DSL, e.g. url. If you get a naming conflict with your existing names you can prefix it with ^, e.g. ^url.


SpecialCases.xpt - templates restructured
A structural refactoring of the code generation templates has been done. It will break code in your SpecialCases.xpt files. It should be easy to migrate since we have only moved template files to subdirectories and some templates has been divided into several files. The following changes has been done. CSC-608 contains descriptions with Subversion revision numbers in case you need to see the exact details of the changes.

DomainObjectProperties.xpt has been moved to templates::domain::DomainObjectProperties.xpt
DomainObject.xpt has been moved to templates::domain::DomainObject.xpt
DomainObject.xpt has been divided into:

  • templates::domain::DomainObject.xpt
  • templates::domain::DomainObjectAnnotation.xpt
  • templates::domain::DomainObjectAttribute.xpt
  • templates::domain::DomainObjectAttributeAnnotation.xpt
  • templates::domain::DomainObjectConstructor.xpt
  • templates::domain::DomainObjectKey.xpt
  • templates::domain::DomainObjectNames.xpt
  • templates::domain::DomainObjectReference.xpt
  • templates::domain::DomainObjectReferenceAnnotation.xpt
  • templates::domain::DomainObjectTrait.xpt
  • templates::domain::Enum.xpt

Service.xpt has been moved to templates::service::Service.xpt
Service.xpt has been divided into:

  • templates::service::Service.xpt
  • templates::service::ServiceTest.xpt
  • templates::service::ServiceEjb.xpt
  • templates::service::ServiceEjbTest.xpt

Consumer.xpt has been moved to templates::consumer::Consumer.xpt
Consumer.xpt has been divided into:

  • templates::consumer::Consumer.xpt
  • templates::consumer::ConsumerTest.xpt
  • templates::consumer::ConsumerEjb.xpt
  • templates::consumer::ConsumerEjbTest.xpt

Repository.xpt has been moved to templates::repository::Repository.xpt
AccessObject.xpt has been moved to templates::repository::AccessObject.xpt
AccessObjectFactory.xpt has been moved to templates::repository::AccessObjectFactory.xpt

Spring.xpt has been moved to templates::spring::Spring.xpt

JPA.xpt has been moved to templates::jpa::JPA.xpt
DataNucleus.xpt has been moved to templates::jpa::DataNucleus.xpt
EclipseLink.xpt has been moved to templates::jpa::EclipseLink.xpt
Hibernate.xpt has been moved to templates::jpa::Hibernate.xpt

Exception.xpt has been moved to templates::common::Exception.xpt
PubSub.xpt has been moved to templates::common::PubSub.xpt
Drools.xpt has been moved to templates::drools::Drools.xpt

DDL.xpt has been moved to templates::db::DDL.xpt
OracleDDL.xpt has been moved to templates::db::OracleDDL.xpt
MysqlDDL.xpt has been moved to templates::db::MysqlDDL.xpt
CustomDDL.xpt has been moved to templates::db::CustomDDL.xpt
DbUnit.xpt has been moved to templates::db::DbUnit.xpt
Datasource.xpt has been moved to templates::db::Datasource.xpt

UMLGraph.xpt has been moved to templates::doc::UMLGraph.xpt
ModelDoc.xpt has been moved to templates::doc::ModelDocCss.xpt
ModelDoc.xpt has been divided into:

  • templates::doc::ModelDoc.xpt
  • templates::doc::ModelDocCss.xpt

Version 1.9.x

Version 1.9.0 was released July 07, 2010.

This release contains:

Complete Release Notes.

Install new Sculptor DSL editor from update site. See Installation Guide.

Migration

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.

Change version
Change sculptor.version in the pom.xml of the parent project.

New DSL keywords

We have added a few new keywords in the DSL, e.g. to. If you get a naming conflict with your existing names you can prefix it with ^, e.g. ^to.

Note the new syntax for aggregates. You can still use the old not aggregateRoot, but I think it is more informative to use the new belongsTo.

ValueObjects and aggregates

We have added same kind of aggregate support for persistent ValueObjects as for Entities. That means that additional constraint validations are performed. If you run in to constraint validation errors you might need to specify not aggregateRoot (or belongsTo) for your ValueObjects that belongs to an aggregate.

Graphviz maven plugin
There is a new maven plugin fornax-graphviz-m2-plugin that generates images (.png) from the .dot files. Add the following plugin in your pom.xml, and install Graphviz, you need to have dot executable in path (or define dotCmd configuration of the plugin).

Replace hints joinTableName and joinColumnName

  • hint joinTableName is now supported with keyword databaseJoinTable
  • hint joinColumnName is now supported with keyword databaseJoinColumn

Documented in Advanced Tutorial

Appengine 1.3.5
If you are using Appengine target implementation you need to change the following to migrate to GAE SDK 1.3.5 and GAE Eclipse Plugin 1.3.3.

a) Install GAE Eclipse Plugin 1.3.3 from update site: http://dl.google.com/eclipse/plugin/3.5

b) Change version numbers in pom.xml

c) Modify excludes configuration of maven-eclipse-plugin in pom.xml. It should now be:

d) Replace appengine-api-1.0-labs and datanucleus-appengine dependencies of maven-dependency-plugin in pom.xml. It should now be:

e) Replace the following dependencies in pom.xml. appengine-api-1.0-labs, appengine-api-1.0-stubs, appengine-api-1.0-runtime, appengine-tools-sdk, datanucleus-appengine. It should now be:

f) Add another maven repository in pom.xml

g) Run mvn clean followed by mvn eclipse:eclipse

Version 1.8.x

Version 1.8.0 was released February 16, 2010.

This release has the same functionality as previous 1.7.0, but internally it has been migrated to latest openArchitectureWare, which is now part of Eclipse. This means that the usability of the DSL editor is much better.

  • Better content assist (ctrl+space)
  • Formatting (Pretty Printing) of model files (ctrl+shift+F)
  • Templates (ctrl+space). This is a good complement to ordinary content assist. For example collection references.

Installation

See Installation Guide for instructions of how to install Eclipse 3.5 Galileo and MWE/Xpand/Xtext 0.7.2, and the new Sculptor Plugins.

Migration

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.

2. Rename src/main/resources/workflow.oaw to workflow.mwe

3. Change workflow.mwe:

4. In pom.xml add workflowEngine mwe to the configuration of fornax-oaw-m2-plugin

Find dependency on hybridlabs-beautifier and remove whole dependency section.

5. We have removed the nested import feature, so you need to import all nested dependent models explicitly. That means that you might need to add some extra imports in model.btdesign.

6. Replace platform resource import with classpath import
For example:
import 'platform:/resource/myapp/src/main/resources/model_core.btdesign'
should be replaced with
import 'classpath:/model_core.btdesign'

7. To be able to use the new formatting feature of model files you might need to add some semicolons to define end of statement for attributes and references. It is still optional, and you don't need to add them, but then formatting will not be good.

8. External import feature has been removed. If you have used external import you can replace it with defining that the module should not be generated in in sculptor-generator.properties. E.g. to skip generation of module named 'foo':

Version 1.7.x

Version 1.7.0 was released January 29, 2010.

This release contains:

Fixed issues:

Migration

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.

Change sculptor.version in the pom.xml of the parent project.

fornax-cartridges-sculptor-framework-test
Test utilities have been moved to separate jar. You need to add the following dependency in both business tier and web projects.

Transitive dependencies from sculptor-framework are removed
All dependencies in sculptor-framework are now declared with scope provided and you must define the used dependencies yourself in your application project.

CGLIB dependency
The CGLIB dependency has been upgraded. In your business tier project you need to add an exclusion to the joda-time-hibernate dependency and you need to add an explicit dependency to the CGLIB library, see below.

Joda for auditable timestamps
When using joda the auditable fields are now also joda types. In case you prefer the old behaviour you can add in sculptor-generator.properties:

Checksum plugin (optional)
This maven plugin is responsible for deleting unchanged files from one-time-generate directories. Read more about it in Developer's Guide. You don't need to use the checksum plugin.

To use it you need to add the folling to pom.xml files in business-tier and presentation-tier projects.

JSF client
A lot of changes has been made to improve support for customization. The eaisiest way of figuring it out is to generate a new project in parallell and compare the differences. For more info about on explicit changes, see jira-issue's that starts with 'JSF client'.

Names interfaces not generated
For each domain object there was a corresponding interface containing string constants for all attribute and association names. This is not generated any more. If you need it you can turn on generation of it with sculptor-generator.properties:

However, we recommend that you migrate to the new type and refactoring safe Properties classes instead. They are intended to be used together with the new findByCondition and ConditionalCriteriaBuilder, but they can be used standalone also. E.g.

Version 1.6.x

Version 1.6.0 was released June 14, 2009.

This release contains:

  • Support for JPA
  • Support for Hibernate validator
  • Spring annotations instead of XML
  • JUnit 4 annotations
  • Jetty and inmemory Hsqldb
  • Spring Webflow 2
  • Don't generate gap classes by default
  • And a long list of bug fixes and improvements...

Fixed issues:

Migration

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.

Dependencies
We have upgraded several frameworks to latest version. Run the Sculptor archetypes for version 1.6 and compare pom files with your existing project.

Version overview:

Framework

Sculptor 1.5.x

Sculptor 1.6.x

Hibernate

3.2.5.ga

3.3.1.GA

hibernate-entitymanager

-

3.4.0.GA

hibernate-annotations

-

3.4.0.GA

hibernate-validator

-

3.1.0.GA

Spring

2.0.7

2.5.6

JUnit

3.8.1

4.4

DBUnit

2.1

2.4.4

Jetty

-

6.1.11

Spring Webflow

1.0.5

2.0.6.RELEASE

Maven clean plugin
To remove generated files before regeneration you need to add some settings for maven-clean-plugin. Grab correct settings by running the Sculptor archetypes for version 1.6.

Change file extension of .design to .btdesign
Due to naming conflict with another plugin we have changed the file extension of model.design. It is now .btdesign. bt stands for Business Tier. You need to rename the .design files and change references in pom.xml, workflow.oaw and model.guidesign. After installing the Sculptor Eclipse plugins you might need to start Eclipse with -clean.

sculptor-generator.properties
We have changed default values to use Jetty and Hsqldb. To use JBoss and MySQL, which was default in Sculptor 1.5.0, you need to add these properties:

JPA, Spring annotations and JUnit annotations are new default features in Sculptor 1.6.0. If you still want to use the old style you need to add these properties:

This setup requires DbUnit version 2.1.

Gap Class
Prior to version 1.6.0 Sculptor generated some files once, such as subclasses to domain objects. Now those classes are generated on demand. In model.design you can specify that you need a sub class for hand written code, a gap class.

To use the same behavior as before, i.e. always generate gap classes, you need to add the following property in sculptor-generator.properties.

JSP CRUD GUI
The JSP variant of the CRUD GUI has been removed, in favor of JSF.

Version 1.5.x

Version 1.5.0 was released February 1, 2009.

This release contains:

  • New DSL for customization of the CRUD GUI
  • New rich client dialect of the CRUD GUI
  • Upgrade to oAW 4.3.1
  • Port of the DDD Sample
  • And a long list of bug fixes and improvements...

Fixed issues:

Migration

You have to upgrade to oAW 4.3.1, and install the Sculptor features, 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.

2. Change fornax-oaw-m2.version in the pom.xml of the parent project.

3. If you use a web project. Create file src/main/resources/model.guidesign with content (replace with your own names):

4. If you use a web project. Edit src/main/resources/workflow-gui.oaw. It should now look something like this

5. Thereafter you need to run mvn eclipse:eclipse from the parent project to update the classpath of the Eclipse projects.

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.

2. Change fornax-oaw-m2.version in the pom.xml of the parent project.

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:

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:

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.

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:

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.

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 some migration tasks to start using 1.2.0.

Installation of Development Environment

The Installation Guide describes that you need to install Eclipse IDE for Java EE Developers (jee-europa 3.3.1.1) and plugins such as openArchitectureWare 4.2.

Note that the need for the previously manually installed Sun jar files in the maven repository has been eliminated, but you have to add java.net repository in maven settings.xml.

JBoss AS 4.2.2.GA is the application server we are using with Sculptor 1.2.

Migration of Maven pom.xml files

If you start from scratch you use the maven archetypes to create project structure and maven pom.xml files with correct dependencies. However, for existing projects you need to change some dependencies in the pom.xml.

Hibernate, add exclusion of jta:

spring-hibernate3, add exclusion of jta:

javaee, use javaee-api artifactId instead of javaee:

castor, add exclusion of jta:

Add hybridlabs-beautifier:

spring-webflow, version 1.0.5:

Add fornax-cartridges-sculptor-generator to web project.
Add hybridlabs-beautifier also.

Remove oaw-aaa-patch dependency:

maven-surefire-plugin version 2.3:

Change version properties in pom.xml in parent project:

Remove the following from pom.xml in ear project:

Run mvn eclipse:eclipse in the parent project to update the dependencies in the Eclipse projects.

Rename of sculptor-generator.properties

In web project the generator properties file should be named sculptor-gui-generation.properties. In the business tier project it is still named sculptor-generation.properties. If you have any properties that are identically defined in both of these files you can remove it from the web project sculptor-gui-generation.properties.

Version 1.1.x

Version 1.1.0 was released November 5, 2007. It include a lot of useful features.

  • A complete, but customizable, CRUD Gui is generated based on the domain model specified with the Sculptor DSL. The generated web application uses Spring Web Flow to achieve navigation of the associations in the domain model.
  • Scaffold simplifies generation of CRUD operations and is perfect for prototyping together with the CRUD Gui.
  • It is efficient to develop the domain model with a textual DSL, but for communication purposes it is useful to have a visual UML view. Sculptor automatically generates a class diagram of the domain model. Instantly updated documentation!

Version 1.1.1 was released November 26. It is a minor bug fix release.

{jiraissues:url=http://fornax.itemis.de/jira/secure/IssueNavigator.jspa?view=rss&&pid=10050&fixfor=100

  • No labels
  1. Anonymous

    Hi, is there any plan by when you like to release a version 2.0.x?
    BR, Roland

    1. I can't promise anything but it will likely be in February.

  2. Anonymous

    Hi, regarding the mwe2 file in version 2.0:
    It is written that
    "The projectName variable must correspond to the artifactId in pom.xml (and directory name) of the project."
    This is not very likely to make a hardcoding here, apart from the fact that svn allows you to checkout a project into a different directory name.
    Is there no way to pass the artifactId as a project specific varibale?

    1. Yes, it would be nice to be able to remove this property. It was added to solve issues with multi-module projects. Maybe this patch will solve it. I will take a look at it.