| Author |
Message |
|
|
|
+1 and be able to 'remember' the chosen values somewhere (e.g. in the user profile) so that will be used next time
|
 |
|
|
|
build your own converter
|
 |
|
|
The example mentioned in the original post is an interesting one. Comparing two dates. One date should be before the other. Questions that arise then are:
- do you want to visualy validate both? when? e.g. what if one is empy... is the other valid? The empty one get'sfilled, do one or both get validated?
- ...
It would be nice if this could be declared on the model (hibernate validator?) and used in the frontend.
Ronald
|
 |
|
|
|
Try adding a timezone. I had this problem and adding a timezone solved it
|
 |
|
|
First, thanks for the fast response and now.....AHHHHH stupid me... I did not mean browser tabs, but the icefaces tabbedpaneset. I was not clear on that part I have to admit. So this not multiple browser tabs working on one (or more) conversations, but icefacestabs within when switching between conversations.
Does this impact your answer?
Ronald
|
 |
|
|
I tried using icefaces (1.5.1) in Seam 1.1.0.GA and 1.1.1(cvs) and ran into problems with the conversation scope
- Switching back to previous conversations did not work
- Opening a new conversation works, but opens pages with tabs on the last tab opened by the *previous* converation
- SelectDate was real slow (probably not related to icefaces/seam, just the implenentation of the selectDate (try going back 25 years ;-) )
The first two could be related to the item in the releasenotes of 1.5.2: Refactored ICEfaces to better align with Seam's expected JSF lifecycle behaviors.
But I just removed icefaces completely and currently have no time to re-try it if the outcome is not guaranteed to be positive with regard to the issues mentioned above. I do not expect anyone to give it a try, just a statement like "Yes, could very well be related because this issues solves ..... " is enough to give it an additional try this weekend
Kind regards,
Ronald
|
 |
|
|