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
org.jboss.weld.exceptions.DeploymentException: WELD-001503: Bean class which has interceptors cannot be declared final: class be.fgov.kszbcss.tad.admin.rest.model.PartnersRest$PartnersRestBuilderImpl
After #18724 (which attempted to fix the issue by making the builder class non-final):
org.jboss.weld.exceptions.DeploymentException: WELD-001436: Type be.fgov.kszbcss.tad.admin.rest.model.PartnersRest$PartnersRestBuilderImpl is not proxyable because it has a private constructor [EnhancedAnnotatedConstructorImpl] private be.fgov.kszbcss.tad.admin.rest.model.PartnersRest$PartnersRestBuilderImpl() - class be.fgov.kszbcss.tad.admin.rest.model.PartnersRest$PartnersRestBuilderImpl.""
openapi-generator version
OK in 7.1.0, broken from 7.2.0 onward.
The text was updated successfully, but these errors were encountered:
What is the purpose of these bean validation annotations on the builder class? I don't think they are needed.
The builder is instantiated with a static method call to the .builder() method, so there's no way for the bean validation runtime to enforce these constraints anyway?
I could try to make a PR to remove them, and revert #18724 as that didn't fix the issue.
Description
Similar to #17875. The applied fix does not entirely solve the issue.
Related to #17874, the
@Valid
bean validation annotation also gets added on TYPE_USE in the builder.PartnersRest.java
This somehow causes an issue on JBoss EAP 7.4.
I guess the presence of the
@Valid
annotation causes the container to treat the builder as a CDI bean?Before #18724:
After #18724 (which attempted to fix the issue by making the builder class non-final):
openapi-generator version
OK in 7.1.0, broken from 7.2.0 onward.
The text was updated successfully, but these errors were encountered: