You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After adding validation of the message retrieved by the Websocket the native image isn't working anymore.
The problem is that the logging is not displayed (see com-pas/compas-architecture#173) so it's very hard to determine what is missing. It may be something simple.
The validation is done in the decode method from the websocket-commons module in CoMPAS Core.
The suspicion is that the validator implementation is being removed by GraalVM.
Steps to reproduce
Build the container image using maven and "-Pnative-image".
Use this image for instance in the Docker Compose file of CoMPAS Deployment.
Open a file from the local file system.
Make sure Websocket is used in the CoMPAS Settings
Try saving the file to CoMPAS using the name invalid/*name.
There should be a error message showing the name is invalid.
Expected behaviour
There is a error shown that marshalling is went wrong (in Log Dialog).
Actual behaviour
There should be a message shown that the name is invalid and can't be used (in Log Dialog).
The text was updated successfully, but these errors were encountered:
Subject of the issue
After adding validation of the message retrieved by the Websocket the native image isn't working anymore.
The problem is that the logging is not displayed (see com-pas/compas-architecture#173) so it's very hard to determine what is missing. It may be something simple.
The validation is done in the decode method from the websocket-commons module in CoMPAS Core.
The suspicion is that the validator implementation is being removed by GraalVM.
Steps to reproduce
invalid/*name
.Expected behaviour
There is a error shown that marshalling is went wrong (in Log Dialog).
Actual behaviour
There should be a message shown that the name is invalid and can't be used (in Log Dialog).
The text was updated successfully, but these errors were encountered: