Hi ,I am getting below error
Description:
The ApplicationContext could not start as 'org.springframework.aot.StaticSpringFactories' that is generated by the Spring AOT plugin could not be found.
Action:
Review your local configuration and make sure that the Spring AOT plugin is configured properly.
If you're trying to run your application with 'mvn spring-boot:run', please use 'mvn package spring-boot:run' instead.
See https://docs.spring.io/spring-native/docs/current/reference/htmlsingle/#spring-aot for more details.
4 replies
COPY ${JAR_FILE} application.jar which is what I'm taking issue with. I want to build that jar inside a builder stage (not layer) and output the expanded jar. But if I understand the documentation correctly the jar must be built first for it to be expanded, which means all build-time benefits (caching of previous layers) are nullified since the jar always has to be rebuilt.
18 replies
Hi, I was just experimenting with Spring MVC and especially with updating (simple) entities via controller endpoints:
public class Controller {
@Autowired
FooRepository fooRepository;
@PostMapping(path = "foos/create")
public RedirectView createFoo(@ModelAttribute Foo foo) {
fooRepository.save(foo);
return new RedirectView("/foos")
}
@PostMapping(path = "foos/{id}/update")
public ModelAndView updateFoo(@PathVariable("id") Long id, @ModelAttribute Foo foo) {
fooRepository.save(foo);
return new RedirectView("/foos");
}
// ...
}What I was wondering: In the updateFoo method, in this case there only the code of the snippet above and no implemented logic of merging entities/copying attributes (e. g. find -> edit -> save), but - somehow magic - when calling the endpoint, previous created entities get updated:
curl -X POST -H "Content-Type: application/x-www-form-urlencoded" "http://localhost:8080/foos/create?name=bar"
Hibernate: call next value for hibernate_sequence
Hibernate: insert into foos (name, id) values (?, ?)
curl -X POST -H "Content-Type: application/x-www-form-urlencoded" "http://localhost:8080/foos/1/update?name=foo"
Hibernate: select foo0_.id as id1_4_0_, foo0_.name as name2_4_0_ from foos foo0_ where foo0_.id=?
Hibernate: update foos set name=? where id=?Is this by design? Thank you!
2 replies
Hello everyone, I'm working through a Spring upgrade from 4.3 to 5.3.5. Our application made use of the path extension content negotiation strategy in a few places. I see this is deprecated but still included, I enabled it in WebMvcConfigurer::configureContentNegotiation. With favorPathExtension set to true it does look like path based negotiation is working again but it looks like the path extensions are included in any @PathVariable I have defined in a controller. This leads to a MethodArgumentTypeMismatch exception being thrown for controller methods that accept a non-string path variable.
e.g:
@RequestMapping(value = "/{id}", method = RequestMethod.GET, produces = CUSTOM_CONTENT)
public Content getContent(@PathVariable Long id)This will result inMethodArgumentTypeMismatch "Unable to parse id=1.content. For input string: "1.content""
I'm not sure if I'm missing a config setting here or of this is expected
2 replies
I am looking for the best and cleanest solution to handle the spring-boot JMS listener with throttling the consumption of messages like 1 message per 10 seconds.
Tried with Thread.sleep(10000) after message read but looking for any other better solution.
1 reply
org.springframework.boot:spring-boot-starter-amqp starter support Spring Native? I tried generating a new project using the initializer, and got the following error on boot.Caused by: java.io.FileNotFoundException: class path resource [org/springframework/amqp/rabbit/annotation/MultiRabbitBootstrapConfiguration.class] cannot be opened because it does not exist
at org.springframework.core.io.ClassPathResource.getInputStream(ClassPathResource.java:187) ~[na:na]
at org.springframework.core.type.classreading.SimpleMetadataReader.getClassReader(SimpleMetadataReader.java:55) ~[na:na]
at org.springframework.core.type.classreading.SimpleMetadataReader.<init>(SimpleMetadataReader.java:49) ~[na:na]
at org.springframework.core.type.classreading.SimpleMetadataReaderFactory.getMetadataReader(SimpleMetadataReaderFactory.java:103) ~[na:na]
at org.springframework.boot.type.classreading.ConcurrentReferenceCachingMetadataReaderFactory.createMetadataReader(ConcurrentReferenceCachingMetadataReaderFactory.java:86) ~[na:na]
at org.springframework.boot.type.classreading.ConcurrentReferenceCachingMetadataReaderFactory.getMetadataReader(ConcurrentReferenceCachingMetadataReaderFactory.java:73) ~[na:na]
at org.springframework.core.type.classreading.SimpleMetadataReaderFactory.getMetadataReader(SimpleMetadataReaderFactory.java:81) ~[na:na]
at org.springframework.context.annotation.ConfigurationClassParser.asSourceClass(ConfigurationClassParser.java:696) ~[na:na]
at org.springframework.context.annotation.ConfigurationClassParser$DeferredImportSelectorGroupingHandler.lambda$processGroupImports$1(ConfigurationClassParser.java:813) ~[na:na]
6 replies
I have a follow up question if you don't mind. The Datadog buildpack has a hard-coded version of the java-agent in it and it would be much better if I could pass that version in as an argument to the buildpack, so I wouldn't have to rely on updates from DD instead. Do you know if there are any plans for the spring-boot-maven-plugin to accept arguments for buildpacks? Many thanks
4 replies
1 reply
Hi all,
I have a question about the ordering of bean definitions and auto configuration.
The camel JMS component is using this line to find a connectionFactory.ConnectionFactory cf = applicationContext.getBeansOfType(ConnectionFactory.class).values().iterator().next();
But now i have to create a second connection to a different activeMQ and this bean definition is added before my jmsConnectionFactory. From what i can see this only happens because the configuration is loaded in order of the name.
But i am wondering if there is something like the AutoConfigurationSorter which might help me here? basically i am trying to sort bean definitions instead of beans.
I know i can create a new jmsComponent endpoint and give it the connectionFactory but i'd like for the automatically created 'activemq:' (extending the jmsComponent) endpoint to remain the same.
Good morning all. I posted a question in the spring-data channel but was told that it's more of a Spring Boot question, so here goes.
I need some help with the health check of Elasticsearch. I'm using Spring Boot 2.5.0-M3 and spring-data-elasticsearch 4.2.0-M5 and I'm using the ReactiveElasticsearchClient.
When checking /actuator/health locally it works fine, however after I've deployed to Kubernetes the heath check keeps reporting
elasticsearch: {
status: "DOWN",
details: {
statusCode: 401,
reasonPhrase: "Unauthorized"
}I have set the following properties but without any luck.
spring:
data:
elasticsearch:
client:
reactive:
use-ssl: true
endpoints: ${ELASTICSEARCH_HOST}
socket-timeout: 10s
username: ${ELASTICSEARCH_USER}
password: ${ELASTICSEARCH_PWD}I can use those credentials and successfully call the /_cluster/health endpoint through Postman, so why does it give me a 401 when Spring Boot tries to call?
The documentation https://docs.spring.io/spring-boot/docs/2.5.0-M3/reference/html/production-ready-features.html#auto-configured-reactivehealthindicators says that the ElasticsearchReactiveHealthIndicator is auto-configured, so I'm not sure what else to do.
FWIW, my ReactiveElasticsearchClient is only set up with SSL, as that's all that's required when querying ES but I'd expect the ElasticsearchReactiveHealthIndicator to use the properties set above.
Am I missing something? Thank you
2 replies
2 replies
1 reply
