- sick of the xslt stuff (see martin fowlers moving away from xslt
)
- sick of new template languages like velocity
- sick of having to fight for java-like features like methods, classes, extension, polymorphism in template languages
- wanting something more java-like
if that is your feeling then the BEENERATOR IS FOR YOU!
- codegeneration can be separated into two parts:
- drivers to read some data, optionally combine this data with other data and feed these data as context into templates. in contrast to a lot of systems the driver as well as the template-system should be covered by the system (e.g. xslt does not address where the templates etc. come from and how they are combined (see ejen for an antish-solutions to this problem).
- templates that work on the data that is provided by the drivers.
- in contrast to a lot of systems the language in the system must be familar to java-programmers. it must be a powerful language (at least as powerful as java).we talk to java-programmers.
- Because today everything is in xml one typical szenario is codegeneration from xml-input. however it should be possible to work with arbitrary input to the template system (e.g. some businesslogic objects, java.lang.Class definitions, ...).
- The Beenerator should be usable from many different systems. support for different buildsystems is crucial as well as plugins for ides.
Next