spring-boot-web | Spring Boot脚手架工程 - 这是基于spring boot | Authorization library

You will need to cope with the possibility of null being returned by any of the calls in that chained method call as follows:

Fixed it.

I moved the css and js folder to src/main/resoucres/static/ and also I had to remove @EnableMVC from the Application.java and then it started working.

Also I had to add {pageContext.request.contextPath} to index.jsp otherwise it wouldn't work on the server since the URL would be http://localhost/myapp/.

By excluding spring-boot-starter-web you did exclude all its dependencies, which are necessary to run a Spring Boot project in a servlet environment. Most notably you did exclude spring-web, which contains most of the classes you find in the error messages.

As its name suggests spring-boot-starter-web isn't centered around Tomcat, only its dependency spring-boot-starter-tomcat is. So you should exclude the latter artifact and include spring-boot-starter-undertow to pull the necessary Undertow dependencies into the project:

Try to correct this:

As mentioned by Michael, you may need to implement the WebFilter interface. Since the AWSXRayServletFilter is a servlet filter, it won't work with WebFilter. Unfortunately there is no built-in support in X-Ray SDK for WebFlux yet. What you'll need to do is within your WebFilter chain, implement an interceptor of your own for tracing incoming requests by creating a segment and adding relevant data to it. You can reference how the AWSXRayServletFilter traces incoming requests here: https://github.com/aws/aws-xray-sdk-java/blob/master/aws-xray-recorder-sdk-core/src/main/java/com/amazonaws/xray/javax/servlet/AWSXRayServletFilter.java

Or, you can use the OpenTelemetry Java SDK to instrument your application and use AWS Collector to send trace data to X-Ray. The OTel SDK has support for WebFlux framework. You can find more info below.

OTel Java SDK instrumentation: https://github.com/open-telemetry/opentelemetry-java-instrumentation

AWS OTel Collector: https://aws-otel.github.io/docs/getting-started/collector

Your application shouldnt run either way because of this docker run -it -p 4000:80 kubernatesimage it should be docker run -it -p 4000:8080 kubernatesimage

Now concerning the issue : Your runtime version is 8 : because of your dockerfile is "FROM openjdk:8" so your application will be running in java 8 environment =>version 52 .. and you have compiled your application to jar file "spring-boot-web-0.0.1-SNAPSHOT.jar" by another version 55 which is java 11. So you have java version mismatch => The key is to make sure both the compile and runtime is using the same JDK.

One proposed fix is change your java version in pom.xml file

You are creating a docker_build.txt file with the content of
echo "building app..."| tee -a build_result.txt but then you are changing the directory to /app and then you create another docker_build.txt and finally you build your artifact.

But you see your first docker_build.txt not with your ls command because your starting directory is not / but the a dynamic path provided by the CI_PROJECT_DIR predefined variable

Further all artifact defintions are also relativ to this path, therefore after moving your docker_build.txt command this should work:

The link header in the Github API provides the URI in an escaped format. The String you pass to client.get().uri() should be unescaped - so it escapes the escaped string, and you end up with a URL that returns nothing.

Instead, you probably want to use something similar to:

I'm afraid not at this time. I also tried looking for implementations in Java but couldn't find any. It would actually be really nice if we had something like that.

I found an implementation for Android but I didn't get the chance to look at the complexity of porting it to Codename One.