facesContext.validationFailed is coming back null
For what reason facesContext.validationFailed could be null? (in a postBack where there are errors..)
I had to resort to an ugly if (#{fn:containsIgnoreCase(facesContext.maximumSeverity,'ERROR')}) showSecurePopup('confirm');
because facesContext.validationFailed is coming back null..
the test code is:
<h:form>
<h:messages />
<br></br>
<h:outputText value="Validation failed: #{facesContext.validationFailed}" />
<br></br>
<h:outputLabel for="field1" value="Test Field" />
<br></br>
<h:inputText required="true" />
<h:commandButton action="#{contactBacking.submitComment}" value="Submit"
<f:ajax render="@form" execute="@form" />
</h:commandButton>
</h:form>
EDIT: Edited as per @BalusC's answer.. and took screenshot of result:
jsf-2
add a comment |
For what reason facesContext.validationFailed could be null? (in a postBack where there are errors..)
I had to resort to an ugly if (#{fn:containsIgnoreCase(facesContext.maximumSeverity,'ERROR')}) showSecurePopup('confirm');
because facesContext.validationFailed is coming back null..
the test code is:
<h:form>
<h:messages />
<br></br>
<h:outputText value="Validation failed: #{facesContext.validationFailed}" />
<br></br>
<h:outputLabel for="field1" value="Test Field" />
<br></br>
<h:inputText required="true" />
<h:commandButton action="#{contactBacking.submitComment}" value="Submit"
<f:ajax render="@form" execute="@form" />
</h:commandButton>
</h:form>
EDIT: Edited as per @BalusC's answer.. and took screenshot of result:
jsf-2
add a comment |
For what reason facesContext.validationFailed could be null? (in a postBack where there are errors..)
I had to resort to an ugly if (#{fn:containsIgnoreCase(facesContext.maximumSeverity,'ERROR')}) showSecurePopup('confirm');
because facesContext.validationFailed is coming back null..
the test code is:
<h:form>
<h:messages />
<br></br>
<h:outputText value="Validation failed: #{facesContext.validationFailed}" />
<br></br>
<h:outputLabel for="field1" value="Test Field" />
<br></br>
<h:inputText required="true" />
<h:commandButton action="#{contactBacking.submitComment}" value="Submit"
<f:ajax render="@form" execute="@form" />
</h:commandButton>
</h:form>
EDIT: Edited as per @BalusC's answer.. and took screenshot of result:
jsf-2
For what reason facesContext.validationFailed could be null? (in a postBack where there are errors..)
I had to resort to an ugly if (#{fn:containsIgnoreCase(facesContext.maximumSeverity,'ERROR')}) showSecurePopup('confirm');
because facesContext.validationFailed is coming back null..
the test code is:
<h:form>
<h:messages />
<br></br>
<h:outputText value="Validation failed: #{facesContext.validationFailed}" />
<br></br>
<h:outputLabel for="field1" value="Test Field" />
<br></br>
<h:inputText required="true" />
<h:commandButton action="#{contactBacking.submitComment}" value="Submit"
<f:ajax render="@form" execute="@form" />
</h:commandButton>
</h:form>
EDIT: Edited as per @BalusC's answer.. and took screenshot of result:
jsf-2
jsf-2
edited Nov 13 '18 at 6:17
Cœur
17.7k9106145
17.7k9106145
asked Jul 24 '12 at 20:59
FMQFMQ
300212
300212
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The FacesContext#isValidationFailed()
returns a boolean
which is never null
. Just get rid of that nonsensicial nullcheck.
<h:outputText value="Validation failed: #{facesContext.validationFailed}" />
True as your comment might be.. the result is still the same.. I actually know this works for a fact, I have used this in other projects, I actually also know that validation errors are being raised since I´m using them in a custom component.. I can´t really figure out why this might be happening...
– FMQ
Jul 24 '12 at 22:57
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f11639208%2ffacescontext-validationfailed-is-coming-back-null%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The FacesContext#isValidationFailed()
returns a boolean
which is never null
. Just get rid of that nonsensicial nullcheck.
<h:outputText value="Validation failed: #{facesContext.validationFailed}" />
True as your comment might be.. the result is still the same.. I actually know this works for a fact, I have used this in other projects, I actually also know that validation errors are being raised since I´m using them in a custom component.. I can´t really figure out why this might be happening...
– FMQ
Jul 24 '12 at 22:57
add a comment |
The FacesContext#isValidationFailed()
returns a boolean
which is never null
. Just get rid of that nonsensicial nullcheck.
<h:outputText value="Validation failed: #{facesContext.validationFailed}" />
True as your comment might be.. the result is still the same.. I actually know this works for a fact, I have used this in other projects, I actually also know that validation errors are being raised since I´m using them in a custom component.. I can´t really figure out why this might be happening...
– FMQ
Jul 24 '12 at 22:57
add a comment |
The FacesContext#isValidationFailed()
returns a boolean
which is never null
. Just get rid of that nonsensicial nullcheck.
<h:outputText value="Validation failed: #{facesContext.validationFailed}" />
The FacesContext#isValidationFailed()
returns a boolean
which is never null
. Just get rid of that nonsensicial nullcheck.
<h:outputText value="Validation failed: #{facesContext.validationFailed}" />
answered Jul 24 '12 at 22:38
BalusCBalusC
846k29831393215
846k29831393215
True as your comment might be.. the result is still the same.. I actually know this works for a fact, I have used this in other projects, I actually also know that validation errors are being raised since I´m using them in a custom component.. I can´t really figure out why this might be happening...
– FMQ
Jul 24 '12 at 22:57
add a comment |
True as your comment might be.. the result is still the same.. I actually know this works for a fact, I have used this in other projects, I actually also know that validation errors are being raised since I´m using them in a custom component.. I can´t really figure out why this might be happening...
– FMQ
Jul 24 '12 at 22:57
True as your comment might be.. the result is still the same.. I actually know this works for a fact, I have used this in other projects, I actually also know that validation errors are being raised since I´m using them in a custom component.. I can´t really figure out why this might be happening...
– FMQ
Jul 24 '12 at 22:57
True as your comment might be.. the result is still the same.. I actually know this works for a fact, I have used this in other projects, I actually also know that validation errors are being raised since I´m using them in a custom component.. I can´t really figure out why this might be happening...
– FMQ
Jul 24 '12 at 22:57
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f11639208%2ffacescontext-validationfailed-is-coming-back-null%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown