Roel Meeuws

This is still an issue. And a very frustrating one at that. Is there no one capable of fixing this? It should be relatively simple for someone familiar with the...

This is also blocking us here. I cannot understand why it is marked as an enhancement. II cannot explain this to my colleagues and supervisors here. This is clearly a...

Well, I would suggest to use the vendor extension mechanism for that. For example, assume we have annotated a resource or a resource method with the documented annotation `@GreatOperation(yell="WOW!")` and...

Anyone thinking about this issue?

I know. This is the exact "problem" or in fact feature we have dealt with all along. We always explicitly set the bean discovery mode to annotated in our projects....

Actually all annotations that have a @stereotype annotation will also be bean defining. That will not automatically imply they will be @normalscope. For @routescoped and @uiscoped a @stereotype annotation would...

> > All files in the META-INF/frontend or otherwise META-INF/resources/frontend directories should be copied to generated/jar-resources on running vaadin:prepare-frontend goal in maven > > Note: This might not be true...

This is really something I would consider priority 1 above all else. Everyone has been on Jakarta EE for some time now, BIRT is simply not runnable on wildfly above...

Why not do this in a @WebListener somewhere? ```java Field objectMapperFld = JsonUtils.class.getDeclaredField( "objectMapper" ); objectMapperFld.setAccessible( true ); ObjectMapper objectMapper = (ObjectMapper) objectMapperFld.get( null ); ```

I understand that it's all free time work. It's just that it will make companies like ours to move away from BIRT. That's not a criticism it's just reality. Sorry....