Validation annotation in @CheckedTemplate
#28406
-
Snippet of our code:
cause deployment failure during Qute processing
Add empty Best regards |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 6 replies
-
Hi Luca, so first of all the validation annotations such as In any case, the error message is clear that I'd recommend to use a separate class for @RequestScoped
@Slf4j
public class FTPReleaseUploadEventManagerBean {
@CheckedTemplate(basePath = "")
static class Templates {
static native TemplateInstance notifyAbandonedRelease(Release release);
static native TemplateInstance notifyCompletedRelease(Release release);
}
} @FroMage it seems that |
Beta Was this translation helpful? Give feedback.
Hi Luca, so first of all the validation annotations such as
@NotNull
are not supported in Qute type-safe templates. Do you use any library that would handle those annotations during the compile time, i.e. modify the resulting bytecode?In any case, the error message is clear that
@Valid com.zucchetti.mercurio.entity.Release
class is not available and this is due to the fact that Qute build step is usingorg.jboss.jandex.Type.toString()
here, andtoString()
includes type annotations - hence the@Valid
.I'd recommend to use a separate class for
@CheckedTemplate
, i.e. something like: