springlets | Springlets provides a series of heterogeneus | Object-Relational Mapping library

By default, the Select2DataWithConversion data type only returns the identifier that will be set as value attribute of the option element and the representation of the object (in your case the product name) as the text attribute of the option element.

That is the minimum info that the select2 component needs to be constructed.

https://select2.org/data-sources/formats

However, as you described in your answer, it's really common to need more info in your Select2 component. For that reason, we overloaded the constructor of Select2DataWithConversion including a boolean parameter to return the entire information of the object.

Check this overloaded constructor here:

https://github.com/DISID/springlets/blob/master/springlets-data/springlets-data-commons/src/main/java/io/springlets/data/web/select2/Select2DataWithConversion.java#L76

So, you just need to change your ProductsCollectionThymeleafController.java to use it like:

The conversion to String when the JSON data is sent to the select2 component is performed by the EntityExpression utilities which are registered in the ConversionService.

Those utilities use the SpEl support to parse the expression and convert the entity to a String. It seems the SpEl expression isn't using or doesn't have access to the ConversionService itself to convert to String the object properties included in the expression.

I've created an issue in the Springlets project to take a look at the problem.

Some weeks ago, I detected a problem in Spring Security and I created the following issue in their repository:

https://github.com/spring-projects/spring-security/issues/4202

Seems like if a @Configuration class extends the WebSecurityConfigurerAdapter abstract class (like in the code generated by Spring Roo), some component is trying to @Autowired a ConversionService instance before the formatters have been registered in the Spring context, so the addFormatters method doesn't include any formatters on it.

A simple work-around that will solve your problem and you'll be able to use Spring Security in your project is to @Override the setContentNegotiationStrategy method in the generated SecurityConfiguration class without include the @Autowired annotation.

The following example looks how to override this method correctly. (In this sample the code is commented)

https://github.com/jcagarcia/proofs/blob/master/spring-security-and-formatters/src/main/java/org/springframework/roo/petclinic/config/security/SecurityConfiguration.java#L54

If this solves your problem, will be great that you comment on the issue saying that you have the same problem.

Hope it helps,

These are the main differences between this two providers:

• DEFAULT: Is the default Spring Security auto-configuration provided by Spring Boot when you include the spring-boot-starter-security in your project classpath. This is the default option because Spring Roo always tries to generate applications that use the auto-configuration provided by Spring Boot.

  • Selecting this provided the following changes will be applied to your project:
    • spring-boot-starter-security dependency will be included to your pom.xml file
  • If you want to know more information about this configuration you should check the spring boot reference guide

• SPRINGLETS_JPA: If you select this provider, the default Spring Security auto-configuration provided by Spring Boot will be used. In addition, this provider will include the Springlets library to your classpath that provides you some extra starters to auto-configure advanced Spring Security properties. Also, configures the security authentication to use and user from the database instead of the default in-memory authentication provided by Spring Boot auto-configuration. You will be able to manage these configuration using the application.properties file and including the properties springlets.security.auth.in-memory.enabled and springlets.security.auth.in-memory.erase-credentials.

  • Selecting this provided the following changes will be applied to your project:
    • springlets-boot-starter-authentication dependency will be included to your pom.xml file
    • security.enable-csrf=true property will be included to enable CSRF. Know more about CSRF and Spring Security here
  • To know more about the Springlets Security project check the Springlets project page

Hope it helps,