sun | A MCBE Proxy supporting fast transfer | Proxy library

I'm assuming you have missing dependencies on your code generation class path. Once you update your question, I'll update my answer.

jOOQ won't support your generated composite types in generated code out of the box, you'll still have to add forced type configurations for that, possibly embeddable type configurations:

• https://www.jooq.org/doc/latest/manual/code-generation/codegen-advanced/codegen-config-database/codegen-database-forced-types/
• https://www.jooq.org/doc/latest/manual/code-generation/codegen-embeddable-types/

Note that the JPADatabase offers a quick win by integrating with simple JPA defined schemas very quickly. It has its caveats. For best results, I recommend going DDL first (and generate both jOOQ code and JPA model from that), because it will be much easier to put your schema change management under version control, e.g. via Flyway or Liquibase.

So for anyone interested what the problem was:

Since we are using a custom logger (ServiceLoggingInvocationHandler) which try catched the exceptions of an invoke method, the catched exceptions were already wrapped with an invocation exception and were not the original exceptions. To solve the problem we needed to unwrap the exceptions again before forwarding them.

Since the logger was only used in debugging mode and only when specified the problem was only occurring for me.

As per documentation, SpringApplication converts any command line option arguments (that is, arguments starting with --, such as --server.port=9000) to a property and adds them to the Spring Environment.

-D works when running via maven. Try: java -jar application.jar --spring.config.location=file:///C://your//path//config.yml.

Via maven: mvn spring-boot:run -Dspring.config.location="file:///C://your//path//config.yml"

public WebDriver driver;

This declares a field, named driver. Not sure why you made it public.

WebDriver driver = new ChromeDriver();

This declares a local variable, also named driver, which is completely unrelated to the field you declared. As all local variables go, it ceases to exist when the method you declared it in ends. Because it has the same name, referencing variable driver in this method refers to the local variable and not the field.

All you really wanted was to make that second line:

Here I'm wondering about the line [in s_client]
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384

You're apparently using OpenSSL 1.0.2, where that's a basically useless relic. Back in the days when OpenSSL supported SSLv2 (mostly until 2010, although almost no one used it much after 2000), the ciphersuite values used for SSLv3 and up (including all TLS, but before 2014 OpenSSL didn't implement higher than TLS1.0) were structured differently than those used for SSLv2, so it was important to qualify the ciphersuite by the 'universe' it existed in. It has almost nothing to do with the protocol version actually used, which appears later in the session-param decode:

Instead of

You are violating the JPA spec by accessing the persistence context in a lifecycle listener.

See the JPA Specification 4.2 Section 3.5.2

In general, the lifecycle method of a portable application should not invoke EntityManager or query operations, access other entity instances, or modify relationships within the same persistence context. A lifecycle callback method may modify the non-relationship state of the entity on which it is invoked.

"a portable application should not" is the specification way of saying: Don't do that, anything might happen. Maybe the world ends.

The fix is not to do that. Maybe be preloading the currently logged in user and reference it so you may access it in your entity listener and do not set a reference to the user, but simple store its id or similar.

You need to put @Configuration on top of FeignConfig which should make it work I believe.

sendRedirect is sending a response code like 302 or 304 (I assume 302 Temporary Redirect) to the browser and a Location header telling the client where to go instead. This is then handled transparently by the browser, without it ever having to display anything.

To see the HTTP response for yourself use curl -v http://yourendpoint, or use Postman if you prefer a browser based tool. Or you can look at the request/response in your browser dev tools, under the network tab (you might have to find an option that doesn't clear the inpector history on page load).

Alternatively you would pass the redirect url to the page and do the redirect later with javascript.

You could respond with something like this, to display the page and redirect after 3 seconds: