Torsten Juergeleit

The Spring Boot sample application #167 provides the reference for updating Sculptors templates.

@tavoda Pavel, I totally agree. Replacing the generation of XML config by Java config is no improvement. The advantages mentioned in the ticket's description are only valid for manually maintained...

> For this BackendConfig, do we have to generate it? Both classes from 9ae41ff are trivial and straight-forward to implement manually. They shouldn't be a deal breaker if not generated....

> Maybe we can create archetype for SpringBoot applications. Can we based it on springboot-example? Will it be useful than? Sure, it makes sense to provide an archetype which creates...

> Just one question, can you help me to create a RELEASE. Sure. I'll check the head version with `mvn -DdryRun=true release:prepare`. Hopefully the release script is still working and...

> First of all, if I am not wrong, the property settings of "cascade.aggregate" and "cascade.aggregate.oneToMany" in the sculptor-generator.properties file doesn't take effect at all in the lastest versions of...

Regarding Sculptors default settings Patrik wrote the following in a [forum post](https://groups.google.com/d/msg/fornax-platform/yKM4NDrn15A/CnLyJDxJsxYJ) as an answer to Pavels suggestion to change the default for cascade for one-to-one relations from `all` to...

> Do you have any idea? I've no clue (I'm not using JPA). But `orphanRemoval`is for `@OneToOne` and `@OneToMany` relations only (as described [here](https://docs.oracle.com/cd/E19798-01/821-1841/giqxy/)). In your model the users cardinality...

> I think it's another issue that why such a model will be mapped to "ManyToOne" and "ManyToMany" relations? Maybe this is due to the Users OneToOne (e.g. in "officialEmailAddress")...

> I tried bi-directional relationships as below. It leads to a OneToMany Relationship. > If for some reason I need to model a uni-directional OneToMany relationship, any idea? Quotes from...