Replies: 4 comments 11 replies
-
|
I agree there's something odd there. Could you share what's in: org.somecompany.domain.api.accounting.WsAccountingDataSubResourceController[org.somecompany.domain.api.entity.WsThirdPartyEntitySubresourceController getThirdPartyEntitySubresource()]) ? And also the potential field that this method returns? I don't need the content of the method, just the annotations, return type and parameters. And for the field, the annotation. Also the annotation of the class would be useful. |
Beta Was this translation helpful? Give feedback.
-
|
Could you provide the information I asked about above? Basically, we are registering things for reflection that probably shouldn't be. We have some ignore rules in place and they might need some tweaking. Also I would be interested in you providing feedback about the other issues you had. |
Beta Was this translation helpful? Give feedback.
-
|
Sure. Nothing confidential in there, so here are the almost full sources: WsAccountingDataSubResourceController is an interface: Implementation: |
Beta Was this translation helpful? Give feedback.
-
|
Which other issues do you mean? For the Hibernate issue, I'm waiting for the hibernate, then Quarkus release with the fix. |
Beta Was this translation helpful? Give feedback.
-
|
Could you also share |
Beta Was this translation helpful? Give feedback.
-
Implementation: |
Beta Was this translation helpful? Give feedback.
-
|
We got the same warning when we migrated a jee application to quarkus 3.6. After upgrading to 3.9.4, the warnings simply disapeared |
Beta Was this translation helpful? Give feedback.
-
|
Yes, there was an issue related to that and we fixed it. So that's probably what you experienced with the upgrade. Now, there might be a different issue. |
Beta Was this translation helpful? Give feedback.
-
|
What was the issue? We are encountering this issue with quarkus 3.6, which we have to stay on until we have migrated past java 11. |
Beta Was this translation helpful? Give feedback.
-
|
There are two different issues AFAICS, one with JAX-RS and the other with JAXB. Let's keep the above thread for the JAX-RS issue and let's use this one for the JAXB one. For JAXB, I see Is this something you have in an entity serialized by JAXB? Either that or |
Beta Was this translation helpful? Give feedback.
-
|
We don't have any explicit reference to any of that in our code. I guess it comes from Quarkus itself? Just wildly guessing, could it come with the Keycloak admin client (which we use in a dependent module)? |
Beta Was this translation helpful? Give feedback.
-
|
I don't know really. If you can come up with a reproducer for both issues, I could have a closer look. There's definitely something we need to improve here but it's hard to know what without a small reproducer. |
Beta Was this translation helpful? Give feedback.
-
|
In the meantime, we are at latest Quarkus version and I heard some improvements have been made. I think we can give the reactive extensions another try and see if anything is better. Worst case, we'll have a reproducer then. |
Beta Was this translation helpful? Give feedback.
-
Hello,
I recently migrated our main application to Quarkus. It does work quite well, but I'm wondering why I have a bunch of indexing problems (at build time & at runtime), for classes I don't really use and should in any case be handled by the extensions themselves.
From the output, it seems that the problems come from JaxbProcessor/JaxrsClientReactiveProcessor.
I didn't configure anything specific for indexing external libraries.
Here is my dependency tree if it helps:
Am I doing something wrong?
Beta Was this translation helpful? Give feedback.
All reactions