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
I created this maven library project in spring-boot for creating excel and csv reports.
The project uses the Byte Buddy library to generate runtime dynamic classes necessary for the purpose of the project.
I tested the correct functioning of this library as a dependency of spring-boot projects having datasource configurations and only with embedded tomcat servers provided by the Spring Tool Suite IDE (version: 3.9.12.RELEASE).
The problem, as shown in the screenshots, is if I try to start the Spring application from the command line (java -jar) or with different IDEs I get a VerifyError for corrupt bytecode:
In the error shown in the figure, the ViwSanVerextStatoFornReportRow class is the ReportRow class generated from the ViwSanVerextStatoForn JPA Entity component.
Are there any suggestions or reasons for this kind of problem?
It seems like a constructor is instrumented incorreclty. This is a user error. Constructors must not use this other than for setting fields before the super constructor is invoked.
I created this maven library project in spring-boot for creating excel and csv reports.
The project uses the Byte Buddy library to generate runtime dynamic classes necessary for the purpose of the project.
I tested the correct functioning of this library as a dependency of spring-boot projects having datasource configurations and only with embedded tomcat servers provided by the Spring Tool Suite IDE (version: 3.9.12.RELEASE).
The problem, as shown in the screenshots, is if I try to start the Spring application from the command line (java -jar) or with different IDEs I get a VerifyError for corrupt bytecode:
In the error shown in the figure, the ViwSanVerextStatoFornReportRow class is the ReportRow class generated from the ViwSanVerextStatoForn JPA Entity component.
Are there any suggestions or reasons for this kind of problem?
Issue already created here: issue
The text was updated successfully, but these errors were encountered: