As I did not get a (valid) answer here, I asked a couple of people from Microsoft and they confirmed that it was not currently possible. Brad Wilson: At this time, only property level validators can emit client-side validation (as that lines up much better with the idea of input validation in the form of … Read more
The solution I went with was to add a System aggregate root that could maintain a list of the current Facility names. When creating a new Facility, I use the System aggregate (only one System as a global object / singleton) as a factory for it. If the given facility name already exists, then it … Read more
If you are strictly using the HTTP authentication framework provided by RFC 7235 for your REST API, the correct HTTP code would actually be 401. From the RFC: The 401 (Unauthorized) status code indicates that the request has not been applied because it lacks valid authentication credentials for the target resource. The server generating a … Read more
If you want to disable client side validation for a form in HTML, add the novalidate attribute to the form element. Ex: <form method=”post” action=”/foo” novalidate>…</form> See https://www.w3.org/TR/html5/sec-forms.html#element-attrdef-form-novalidate
This is indeed specified/expected behavior. The attributes of taghandlers like <f:validateXxx> are evaluated during view build time. So they can’t refer a variable which is only available during view render time like the currently iterated variable of <ui:repeat>. It would indeed work when you use an iterator which runs during view build time like JSTL … Read more
If utilizing the JSF-builtin validation facility (i.e. just use validators which throw ValidatorException the usual way with therein the desired faces message) is really not an option for some reason (I’d really think twice, no, thrice about working around JSF validation facility), then you can always use FacesContext#validationFailed() to signal JSF that the validation has … Read more
The PrimeFaces ajax response puts an args object in the JS scope which has a validationFailed property. You could just check for that in the oncomplete. <p:commandButton … oncomplete=”if (args && !args.validationFailed) dialogaboutDEQ.show()” /> If you’re performing validation in action method instead of in a normal validator, and you can’t rework that, then you need … Read more
The minimum are slash (“https://stackoverflow.com/”) and NULL (‘\0’)
Either use the input component’s requiredMessage attribute: <x:inputXxx … required=”true” requiredMessage=”Value is required” /> Or create a properties file in the classpath which contains the custom message template: javax.faces.component.UIInput.REQUIRED = Value is required. and is been registered as message bundle in faces-config.xml: <application> <message-bundle>com.example.CustomMessages</message-bundle> </application> The above example assumes that the file name is CustomMessages.properties … Read more
In case you aren’t using ajax, or are still on JSF 1.x, and you really need to invoke a business action in cancel() method (i.e. just reloading the page is insufficient), then your best bet is to add immediate=”true” to the button. This way all input fields which don’t have immediate=”true” will be skipped in … Read more