You express your design intent in a textual DSL, from which Sculptor generates high quality Java code and configuration. It is not a one time shot. The application can be developed incrementally with an efficient round trip loop.
Sculptor is useful when developing typical enterprise or web applications that benefit from a rich and persistent domain model. Sculptor also provides a sophisticated CRUD GUI for administrative sections of the application or to serve as a scaffolding for your manually created pages.
The generated code is based on well-known frameworks, such as JPA, Hibernate, Spring Framework, Spring Web Flow, JSF, RCP, and Java EE.
Product characteristics:
- Easy to learn, intuitive syntax of the textual DSL, editor with error highlight, code completion, and outline
- Quick development round trip, it is not a one time generation
- Existing IDE tools, such as refactoring, code assist and debugger will continue to be of service to you
- High quality of generated code, based on well known frameworks, best practices, and a lot of experience
- Great extensibility and customization options
- Easy to remove the tool, no runtime magic
Posts
Hello, I don`t know if this is the right place to put my question but since I can't find answers in the web I think you're the best person to solve my doubt.
ReplyDeleteIn Developer's Guide you say: "Two meta models are used. One for the DSL...Another meta model is used by the code generation templates...They serve different purposes, which motivates why two meta models are needed."
So I still can't see in a clear way what is the main purpose of each one and why do we need to have the both of them.
It will be great if you could explain that to me or give the documentation where I can clear my doubts
Thanks in advance,