Troubleshooting

The new Spring version depends on the Jakarta EE 10 specification. As a result, you must upgrade your servlet container to a version that supports Jakarta EE 10, like Tomcat 10.1 or Jetty 12 (packaged with LuciadFusion).

Moreover, this Spring version has changed the root package name of its Java classes from javax to jakarta. If you use any:

you must change your imports from the javax to the jakarta package.

In Spring Security 5.8 and earlier, requests without an authorization rule were permitted by default. However, denying requests without authorization rules by default puts your application in a stronger security position. In that case, your application requires that authorization rules are clearly defined for every endpoint. Consequently, since Spring Security 6.0, Spring Security denies any request that’s missing an authorization rule by default.

Authorization rules for LuciadFusion Platform Services are applied automatically based on the information returned by the getEndPointPatterns() method in ILfnServiceTypeConfiguration. You may need to override this method if the default implementation doesn’t give a valid pattern for your custom service types. You can configure the applied authorization rules for all services using the fusion.security.serviceAuthenticationRequired. When you set it to true, authentication will be required for all services. If you set it to false, anonymous access to services is allowed. For more fine-grained configuration of access to services, read the How to configure access to services in LuciadFusion article.

If you configured custom endpoints, you must make sure to add a SecurityFilterChain with an authorization rule covering that endpoint. Otherwise, you’ll get 403 Forbidden errors when trying to access those endpoints.

Spring Boot 3 significantly changed the trailing slash matching configuration option. This option determines whether to treat a URL with a trailing slash the same as a URL without one. Previous versions of Spring Boot set this option to true by default. As a result, a controller with a GetMapping("/some/greeting") annotation for example, would match both GET /some/greeting and GET /some/greeting/” by default in previous Spring Boot versions.

In current versions, accessing a URL with a trailing slash, such as GET /some/greeting/, results in a 404 error, unless the controller is specifically set up to handle URLs with a trailing slash.

If you run into any other Spring issue, check in the Spring migration guides if a Spring Framework change may be causing your issue.

These are the links to the Spring migration guides and release notes:

Spring Boot 2.4 has changed the way that YAML files are processed. Because of this, you can no longer use spring.profiles.include in profile-specific YAML files. If you only want to import other YAML files and aren’t interested in activating a profile, you can use spring.config.import as an alternative. If you do want other profiles activated, you can use the new Profile Groups feature.

For more information, see the Spring Boot Config Data Migration Guide.

Please note that the YAML files provided with LuciadFusion have already been migrated. This means that it isn’t possible to use the spring.config.use-legacy-processing property to revert to the legacy way of processing YAML files.

Circular reference detection has become stricter. This means that, for example, self-injection is no longer possible. If your application fails to start due to a BeanCurrentlyInCreationException, we strongly recommend that you update your configuration to break the dependency cycle.

For more information, see the Spring Boot 2.6 release notes.

The server.use-forward-headers property has been deprecated in favor of server.forward-headers-strategy. If you were using server.use-forward-headers: true, then you need to update it to server.forward-headers-strategy: native. For more information, see the Spring Boot 2.2 release notes.

If you run into any other Spring issue, check in the release notes for the various Spring versions if a Spring Framework change may be causing your issue.

These are the links to the Spring Boot and Spring Framework release notes:

A correct indentation in YAML files is really important. Tabs should never be used. A good format is to use 2 spaces for an indentation level. The following example shows 2 server properties server.servlet.context-path and server.port:

Property keys or parts of property keys cannot be used more than once in the same YAML file.

Wrong:

The key fusion.security is encountered twice. The correct use is:

When a property is defined two times in two separate profiles, the value of the property of the rightmost active profile is taken. For example, when you have -Dspring.profiles.active=fusion.single,custom.profile, the properties re-defined in custom.profile will overwrite the ones defined in fusion.single profile.

If a property occurs in a profile as well as in its imported configuration file, the property values in the imported configuration file takes precedence.

For example, file fusion.common.yml configuration file specifies:

File application-fusion.testing.yml specifies:

The resulting value of fusion.security.enabled is true. From the Spring Javadoc for spring.config.import: Imports are processed as they are discovered, and are treated as additional documents inserted immediately below the one that declares the import.