Templates: Provide support for Spring Java Config #166
Comments
|
The Spring Boot sample application #167 provides the reference for updating Sculptors templates. |
|
Hello Torsten, I'm not big fun of Spring Java Configuration. XML configuration have one, for us huge advantage. You can override definition in more.xml. For example if you want override 'dataSource', you can define new one in more.xml and later definition win. I guess it's not possible with Java configuration. |
|
@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 configuration and not generated one. So in 9ae41ff I updated the Spring Boot example #167 to use the generated XML configuration instead of manually maintained Java config classes. But how about generating the corresponding wrapper configuration classes which import the XML configuration ( |
|
Hello @tjuerge, i would like to finish release and cleanup issues. For this BackendConfig, do we have to generate it? It can be static with simple import for applicationContext.xml. Or do you have some idea for improvement? |
Both classes from 9ae41ff are trivial and straight-forward to implement manually. They shouldn't be a deal breaker if not generated. But in the long run it would be convenient to generate them. So let's postpone this ticket and finish the release :) |
|
But they all look 'static'. I had before some SpringBoot integration requirements. 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 a Spring Boot app based on the springboot-example. |
|
Great, now I'm improving old archetypes, I will create one based on
springboot example.
Just one question, can you help me to create a RELEASE. I'm working now
towards 3.2 release, everything is working, travis builds are OK however I
will be very happy if you can 'check it', maybe provide some feedback and
RELEASE it. I mean as really to 'install' it to central repos.
Thanks
/Pavel
…On Tue, Feb 23, 2021 at 4:22 PM Torsten Juergeleit ***@***.***> wrote:
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 a Spring Boot
app based on the springboot-example.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#166 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYJM7P6EGXXKZKUB4MB3CLTAPB3DANCNFSM4AZXUNXQ>
.
|
Sure. I'll check the head version with |
|
Great, thanks. I hope I can finish it in a week or two. Than most difficult
task, documentation. This is my nightmare because of my poor english.
Regards
/Pavel
…On Wed, Feb 24, 2021 at 7:40 PM Torsten Juergeleit ***@***.***> wrote:
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 my credentials are still
valid - last release was back in 2015 :-)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#166 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAYJM7NDCS5A6DTAMZEI2LLTAVBYVANCNFSM4AZXUNXQ>
.
|
Starting with version 3 Spring provides an alternative to XML for configuring the bean container - Java Config.
With Java Config the XML files are replaced by
@Configurationannotated classes with@Beanannotated methods returning bean instances. This java-based approach has few advantages:@Configurationannotated classes are automatically detected by component-scan (they are Spring managed beans as well)The text was updated successfully, but these errors were encountered: