Closed lamemind-ud closed 2 years ago
Hi @lamemind-ud !
Do you have some data source set up in the project? Based on the error I'd guess that might be the problem.
Hello @mstahv and thanks for you response, but it's not a datasource related problem.
I'm not extending Panache, I'm using base entities
@Entity
@Table(name = "Brand")
public class Brand {
@Id
@GeneratedValue(strategy = GenerationType.IDENTITY)
@Column(name = "id", nullable = false)
private Integer id;
[..]
@Entity
, say org.demo.Brand
org.demo.BrandRepository
quarkus.hibernate-orm.packages=org.demo
quarkus.datasource.db-kind=h2
quarkus.datasource.username=sa
quarkus.datasource.password=password
quarkus.datasource.jdbc.url=jdbc:h2:mem:quarkus_test;DB_CLOSE_DELAY=-1
quarkus.hibernate-orm.database.generation=create
quarkus.hibernate-orm.log.sql=true
mwnv
Expected result: the unit test should work Result: the unit test fails with the stack trace reported in my previous comment
Idk if it's useful, but if you remove vaadin-core-jandex
dependency, the test works. And of course the app crashes as soon as you load localhost:8080
and this is expected to crash.
Thanks again
Sounds weird. Maybe there is something extra in the vaadin-core-jandex that should not be there 🤔
Could you share that project somehow? zip it and attach it to this issue, or share it in GitHub. That would really help our core team to look into it (and this way increase the chances that they would look into it sooner).
Sounds weird. Maybe there is something extra in the vaadin-core-jandex that should not be there 🤔
Could you share that project somehow? zip it and attach it to this issue, or share it in GitHub. That would really help our core team to look into it (and this way increase the chances that they would look into it sooner).
@mstahv I'll share the full project tomorrow
PS: in the uploaded project, I have already commented out the vaadin-core-jandex
dependency. You have to remove the comment in order to reproduce the bug. Sorry for the confusion
Thanks that helps a lot! Our core team promised to investigate this in their next sprint.
Seems like that adding quarkus-spring-data-jpa
causes bean discovery of fusion configuration classes, but fusion-endpoint
has provided scope
for some spring dependency, including spring-boot-autoconfigure
that contains org.springframework.boot.autoconfigure.web.servlet.WebMvcRegistrations
.
@lamemind-ud if you don't need fusion endpoint in your project, can you try adding the following configuration to application.properties
?
quarkus.arc.exclude-types=com.vaadin.fusion.*
Hello @mcollovati , your workaround is working! The unit test succeeded and the web app has started!
Actually I don't know what fusion-endpoint
is... I'm very new to vaadin.
And what if I need fusion-endpoint
in the future?
You don't need that. It will also not be included on the classpath by default in the future.
Vaadin 23 and Vaadin 22.0.7 (and later) will exclude fusion stuff from jandex index, so there will be no need for additional settings in application.properties
Description of the Bug
Hello, I cloned this repository and tried to integrate some functions, but I'm stuck with database access.
What i want to do
I'd like to use Spring repositories (
org.springframework.data.repository.*
) just like I already do in other Quarkus projects, throught thequarkus-spring-data-jpa
extension.Stack trace
java.lang.IllegalArgumentException: Producer method return type not found in index: org.springframework.boot.autoconfigure.web.servlet.WebMvcRegistrations
How to reproduce
In order to reproduce just add the
quarkus-spring-data-jpa
dependency.quarkus version 2.5.4.Final vaadin version 22.0.2
Thanks