Good Morning Ralf, it seems like this was indeed the issue… I am running java 1.8.0_181 so the downgrade worked and it works like expected.
Thank you very much! Have a great week! ____________________________________________ Daniel Wenning Tel. +49 7531 / 45716-19 Fax +49 7531 / 45716-16 E-Mail: [email protected]<mailto:[email protected]> ESTEAM Software GmbH Obere Laube 46 D-78462 Konstanz Geschäftsführer: Rainer Döbele Sitz: Konstanz, Amtsgericht Freiburg HRB 381845 Internet: www.esteam.de<http://www.esteam.de/> ____________________________________________ Von: Ralf Eichinger <[email protected]> Gesendet: Freitag, 13. August 2021 17:20 An: [email protected] Betreff: Re: Evaluating empire-db with Spring Boot Hi Daniel, seems that you are trying to compile with a java version < 11? (what does "java -version" print?) I downgraded required java version now from 11 to 8 in pom.xml. https://github.com/datazuul/empire-db/tree/spring-boot/empire-db-examples/empire-db-example-spring-boot So try again after pulling... On Fri, Aug 13, 2021 at 2:39 PM Daniel Wenning <[email protected]<mailto:[email protected]>> wrote: This also fails for me. [INFO] Compiling 4 source files to E:\Java\Empire-DB\EmpireDatazuul\empire-db-examples\empire-db-example-spring-boot\target\classes [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 1.563 s [INFO] Finished at: 2021-08-13T14:37:54+02:00 [INFO] Final Memory: 18M/309M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project empire-db-example-spring-boot: Fatal error compiling: invalid target release: 11 -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project empire-db-example-spring-boot: Fatal error compiling at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116) at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80) at org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288) at org.apache.maven.cli.MavenCli.main(MavenCli.java:199) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356) Caused by: org.apache.maven.plugin.MojoExecutionException: Fatal error compiling at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1145) at org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:187) at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134) at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207) ... 20 more Caused by: org.codehaus.plexus.compiler.CompilerException: invalid target release: 11 at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:173) at org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:174) at org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:1134) ... 23 more Caused by: java.lang.IllegalArgumentException: invalid target release: 11 at com.sun.tools.javac.main.OptionHelper$GrumpyHelper.error(OptionHelper.java:103) at com.sun.tools.javac.main.Option$12.process(Option.java:216) at com.sun.tools.javac.api.JavacTool.processOptions(JavacTool.java:217) at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:156) at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:107) at com.sun.tools.javac.api.JavacTool.getTask(JavacTool.java:64) at org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:125) ... 25 more [ERROR] [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException But i think this has nothing to do with the previous error… ____________________________________________ Daniel Wenning Tel. +49 7531 / 45716-19 Fax +49 7531 / 45716-16 E-Mail: [email protected]<mailto:[email protected]> ESTEAM Software GmbH Obere Laube 46 D-78462 Konstanz Geschäftsführer: Rainer Döbele Sitz: Konstanz, Amtsgericht Freiburg HRB 381845 Internet: www.esteam.de<http://www.esteam.de/> ____________________________________________ Von: Ralf Eichinger <[email protected]<mailto:[email protected]>> Gesendet: Freitag, 13. August 2021 14:15 An: [email protected]<mailto:[email protected]> Betreff: Re: Evaluating empire-db with Spring Boot sorry, had a typo: maven does not exist, it is "mvn" ``` $ cd empire-db/empire-db-examples/empire-db-example-spring-boot $ mvn clean install $ java -jar target/empire-db-example-spring-boot-2.5.3.jar ``` On Fri, Aug 13, 2021 at 11:41 AM Daniel Wenning <[email protected]<mailto:[email protected]>> wrote: Hello Ralf, i tried to get the example working but I am struggeling with the Datasource. I got a first issue resolved, where the Logger was twice found in the sourcetree but i think this is a local issue for me. The issue I currently cannot resolve comes up, as soon as the datasource tries to get a connection. It tells me the HikariDatasource is null „HikariDatasource (null)“, unfortunatly i do not get a Stacktrace. The error occurs in SampleApp.java:240 as soon as the Connection shall be fetched in the run() Method. As Rainer I have not much experience with Spring too, but tried get it working non the less. If you can have a look into it and hopefully have a solution for me. Thanks in advance and have a great weekend Greetings Daniel Von: Ralf Eichinger <[email protected]<mailto:[email protected]>> Gesendet: Dienstag, 10. August 2021 18:12 An: [email protected]<mailto:[email protected]> Betreff: Re: Evaluating empire-db with Spring Boot Hi Rainer, I am glad to contribute. The example is without Spring JDBC Templates, just pure Empire-DB, but configured over the convenience configuration features of Spring Boot (application.yml, profiles and reading them with ConfigurationProperties). The DataSource is automatically instantiated when Spring Boot detects the hsqldb driver on classpath and when dependency to spring-boot-starter-jdbc is in pom.xml and by using standard datasource properties (see https://docs.spring.io/spring-boot/docs/current/reference/html/application-properties.html#application-properties.data.spring.datasource.url ) The DataSource uses automatically Hikari-ConnectionPool. Many greetings Ralf On Tue, Aug 10, 2021 at 4:21 PM Rainer Döbele <[email protected]<mailto:[email protected]>> wrote: Hello Ralf, thank you very much for your Spring-Boot Example. We are happy that you are interested in Empire-db and every contribution to our project is very much appreciated. We will gladly take a look at the example, but it might take a few days before we can comment. Unfortunately I personally do not have experience with Spring Boot and other Spring related components. But if I need some help to understand it, I will let you know. Best Regards, Rainer Von: Ralf Eichinger <[email protected]<mailto:[email protected]>> Gesendet: Montag, 9. August 2021 23:12 An: [email protected]<mailto:[email protected]> Betreff: Re: Evaluating empire-db with Spring Boot ok, managed to implement a working spring boot example. opened a pull request for the new example: https://github.com/apache/empire-db/pull/11 please review if done properly On Mon, Aug 9, 2021 at 7:55 PM Ralf Eichinger <[email protected]<mailto:[email protected]>> wrote: I have to questions: 1. Is there an example code using empire-db with spring boot? e.g. using common application properties for connection/database setup currently I am using jdbi but do not like the "functional programming" row mapping... the code example here: https://github.com/apache/empire-db/tree/master/empire-db-examples/empire-db-example-spring seems to map empire-db to spring jdbc templates... but I want a barebones empire-db setup in a spring boot (without jdbc template - for now) to get used to it. any tutorial/documentation beside this one: http://empire-db.apache.org/documentation/tutorial.htm ? 2. I have JSONB columns in my postgres database. How to handle json functions with empire-db? https://www.postgresql.org/docs/12/functions-json.html
