When using the IceFaces ice:selectInputDate a date selection always triggers the form validation.
So when a user selects a date all validation errors are shown.
That's especially tedious when the date input is at the beginning of the form and all fields are empty. Then the user will get presented with all the "Value missing" error messages.
It's so frustating and really is a shame for such a widely-used framework like IceFaces.
Anybody got any hints how to handle this bug?
http://jira.icefaces.org/browse/ICE-4535
(immediate="true" does not help)
Thanks.
I found out that the real problem is not the getting rid of the validation but that the validation for required="true" is missing completely after a partial submit is sent.
I resolved this here: http://jsfbrickyard.wordpress.com/2010/03/10/how-to-fix-the-requiredtrue-and-partial-submit-problem-in-icefaces/
another and maybe better solution (or workaround) is described in this blog entry:
http://jsfbrickyard.wordpress.com/2010/03/11/a-better-alternative-for-the-icefaces-inputselectinputdate-control/
it describes how to use jquery UI datepicker instead of the ice:selectInputdate control.
comments welcome.
Related
I have a standard newsletter form from the shopware6 CMS.
Now people can register and get a success message but is there also an easy way to clear the input fields after the submit? Can I just give the form an ID and reset the form or is this not recommended? Anyone has an idea how to achieve this or is this just a bad idea at all?
The Shopware standard behavior is indeed a bit confusing here. Especially due to the success message being shown below the form, it might get unnoticed.
But instead of clearing the form, I would suggest to hide the form and just show the success message in it's place.
This might be also a good take for an improvement as a pull request to the Shopware platform / core.
I have looked everywhere for the following issue, but unfortunately not able to find the solution. I an using JSF 2.2, richfaces, Netbeans 7.3.1 and GlassFish Server. I am trying to build a GUI for selecting multiple items in the rich:picklist, adding them to the right and clicking a submit button which would execute methods (having JDBC calls) associated with each of the selected items on the right and hence populating the tables in Database. Any working example would be greatly appreciated. Thanks!
You can see a live demo of all richfaces components here http://livedemo.exadel.com/richfaces-demo/
Here all the components usage and its tag information every thing is clearly given. Still if you feel any problem with understanding then you can post another question with a specific problem. The question you have asked is a very general one. no offense.
Hope above link helps you.
In a production application that I have developed sometimes I get an error saying .getDocument() is null. I have added checks in my code that traps an error if this happens. And the strange thing is that the XSPDocument seams to be OK.
Any other ideas how to debug the cause of this?
========================================================
Edit
The lower parts of the application is a simple database, create an assignment it gets status new
change the status to ongoing thru a button. Add information in text, date and numberfields, no Richtext, no attachments.
The user can switch to another xpage to send this document is an pdf attachment in an email.
The user can save the document as a draft
When they are done the click on an approve button and this button will set the status to approved. Save the document and send it as an pdf to an email adress
The problem ocurrs both on the Save button and on the approve button.
.getDocument from the xsp document is null the xspdocument.getNoteID return an ID
I can do replaceitemvalue on the xsp document.
It never happens on new documents only existing what I have seen
It feels like the comment from David that the backend doc is dropped/recycled
we experienced the same getDocument() problem recently. Finally we found a root cause: two different XPages were loaded simultaneously via iFrames. One of those XPages produced run-time error randomly, in 25% of cases. A sort of conflict in JSF model in context of single session.
solution: viewState="nostate"
not sure if it helps in your case, but this option resolved a lot of problems in our applications. It was introduced in 8.5.3. And it should be especially useful for so called XAgents.
Hard to give a hint without knowing more about everything else, but I remember having seen this as well. Just a few ideas:
Is XSPDocument.getNoteID() pointing to a valid Document if this happens?
Is it maybe pointing to a different doc than what you expected?
Could there be some kind of dynamic change of datasources going on?
Maybe some kind of timeout so that the server all of a sudden forgot who you are (in rare cases this happens to me)?
Lothar/edcom
It would be helpful to have a few more details. I assume that the document has previously been saved and it's not a new note?
You're not trying to put the actual document object inside a scoped variable are you? That would be bad as that would be pretty toxic. Without knowing more I would think this could be the case. The backend document has been garbage collected.
I don't often have need for tomahawk components anymore since jsf 2.0 provides great selectOneMenu support and most of other functionality I used to use them for, but when it comes to a selectOneRadio component I don't know of another provider with a layout="spread" option. This is essential from time to time to achieve a certain layout I'm asked for.
I'm using Tomahawk for exactly this purpose but recently discovered some serialization issues caused by this component during failover. I was wondering if anyone has discovered another provider with similar "spread" functionality or if anyone has written/published an alternative based on h:selectOneRadio?
We also wanted to use the "spread" option - in our case for DDA compatibility (no using tables for layout) but for political reasons were unable to use Tomahawk. We ended up writing our own custom renderer for radio buttons and checkboxes.
It wasn't too hard, took me a few hours to get it working the way we wanted. I'm at home for a couple of days without access to the code base so I can't give you the exact code but it's a pretty simple matter of overriding the encodeBegin() and decodeBegin() (or encodeEnd() and decodeEnd() depending on your usecase) methods and writing the html appropriate for your application.
I need to enable/disable post comments regarding the value of a new field in Post list. I don't see how to do this... Any ideas?
Why is there an error when converts to XSLT? Is possible to get the querystring to do this?
I don't think you'll be able to get that level of control with the standard blog component. Should be reasonably easy to implement using CKSEBE though.
Easiest method I can think of within the standard blog is to use jQuery to hide the comment form - that way you only need to get the value of the field appearing somewhere on the page.