[
https://issues.apache.org/jira/browse/WICKET-6901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380783#comment-17380783
]
Sven Meier edited comment on WICKET-6901 at 7/14/21, 6:19 PM:
--------------------------------------------------------------
You can easily change the configuration to not alter the markup:
{code:java}
beanValidationConfiguration.register(Size.class, (component, tag, annotation)
-> {});
{code}
Maybe I misunderstood you, but is this what you are looking for?
was (Author: svenmeier):
You can easily change the configuration to not alter the markup:
beanValidationConfiguration.reguster(Size.class, (component, tag,
annotation) -> {});
Maybe I misunderstood you, but is this what you are looking for?
> PropertyValidator and JSR303 problem
> ------------------------------------
>
> Key: WICKET-6901
> URL: https://issues.apache.org/jira/browse/WICKET-6901
> Project: Wicket
> Issue Type: Bug
> Components: wicket-bean-validation
> Reporter: Sergei
> Priority: Major
> Attachments: Screenshot_20210714_165724.png, bugreportproject.zip
>
>
> When using JSR 303 annotations, PropertyValidator does not display a message
> in the feedback panel due to the automatic addition of the maxlength
> attribute to the markup. To do this, you need to manually increase the value
> of the maxlength attribute in the markup or do it during rendering using
> AttributeModifier.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
