[ORCHESTRA] Running on RAD 7 with WAS 6.1
So, I managed to get Orchestra 1.3 to run on RAD 7.0 with WAS 6.1. I had to make an interesting change -- I had to manually add the OrchestraFacesContext to the JSF config file: factory faces-context-factoryorg.apache.myfaces.orchestra.lib.jsf.OrchestraFacesContextFactory/faces-context-factory /factory even though it's already in the faces-config.xml file included in the Orchestra JAR file. Strangely, RequestParameterFacesContextFactory was loading just fine, but OrchestraFacesContextFactory wasn't loading at all. I'm guessing this might be a weird quirk of the IBM JSF implementation (which is technically a heavily modified version of the 1.0 version of the RI). Now that I've gotten it to run, let's see what happens when we try to really use its features... --- Kito D. Mann -- Author, JavaServer Faces in Action http://twitter.com/kito99 http://www.virtua.com - JSF/Java EE consulting, training, and mentoring http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info +1 203-404-4848 x3
Re: t:selectManyCheckbox reverse label and input order
Chad Skinner wrote: I am using a t:selectManyCheckbox and would like to be able to reverse the order of the label and checkbox input field so that the checkbox is displayed before the label. Does anyone know what i need to do in order to achieve this. Basically I am printing a three column listing of check boxes, but since the labels are of varying lengths the checkboxes are printing all over the place and I would like them to line up neatly by placing them before the label. Have you found a solution? I'm also interested in that. It looks quite ugly with the checkboxes on the right. -- View this message in context: http://www.nabble.com/t%3AselectManyCheckbox-reverse-label-and-input-order-tp19537349p21494633.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
Date Pickers not working by using jsffaclets1.1.14
Hello Everyone, I'm upgrading from jsf-faclets1.1.11 to 1.1.14 I see a strange problem with the date picker When I choose a date for e.g. jan 16, the date text box reflects the correct date and when I try to change the same date I see that the previous date i.e jan 15 highlighted in the date picker component Any idea as to what is causing this? I'm using trinidad1.0.10 version Date picker component was working fine in Trinidad 1.0.10 and jsf-facelets 1.1.11 Thanks, Sabitha
Re: Input components with disabled=true
On Thu, 2009-01-15 at 20:28 +0100, Luca Graf wrote:
Hello together,
I got an problem with input components like h:selectBooleanCheckbox when i
use the attribute disabled=true. My scenario is that i have two checkboxes.
The second is initially set to disabled=true. Now the user should only get
access to the second if he changed the value of the first before.
My approach was, if the user changed the value of checkbox1 then i set the
attribute of checkbox2 via javascript to disabled=false.
Example:
h:selectBooleanCheckbox id=checkbox1 onchange=var
element=document.getElementById('checkbox2'); if(element.disabled)
element.disabled = false; else element.disabled = true;
h:selectBooleanCheckbox id=checkbox2 disabled=false/
On the first it looks good, after the user has changed the value of the first
checkbox, the second is now accessible via html.
But it looks that the value is doesn't send in the request to the server,
like the normal behavior for an input element with disabled=true.
It is not enough to set disabled=false in HTML to get the value of checkbox2
to the server?
Use readonly instead of disabled. They appear the same to the user, but
browsers send the state of readonly HTML elements back to the server on
submit. Browsers ignore disabled HTML elements on submit, which is causing
the problem.
Regards,
Simon
