Yeah, right verbatim creates UIOutput for the nested stuff.
Introduced due some troubles in jsf-jsp-integration ([1]). -Matthias [1] - http://www.onjava.com/pub/a/onjava/2004/06/09/jsf.html On 2/20/06, Volker Weber <[EMAIL PROTECTED]> wrote: > Hi Philippe, > > you have jsf tags inside of f:verbatim? AFAIK this will not work, you > should close the verbatim before the jsf tags, and reopen after. > > > Regards, > Volker > > Philippe Lamote wrote: > > Hi List, > > > > Another problem I've run into today: > > > > -- I have in my page a div like this: (inside a form) > > ... > > <!-- For the Use Case Submit New Calendar: --> > > <t:div rendered="#{portalbean.useCase eq 'submitNew'}" > > > <f:verbatim> > > > > <tr > > > <td width="5%">  </td> > > <td align="left" rowspan="4" class="rightCellLine"> > > <h:outputLabel value="#{labels.regCal_when} > >  " /> > > <t:inputCalendar id="kalender" > > renderAsPopup="true" > > > > popupButtonString="Click here to show Calendar" > > > > renderPopupButtonAsImage="true" > > > > popupDateFormat="dd/MM/yyyy" > > > > popupTodayString="#{labels.regCal_today} " > > > > popupWeekString="#{labels.regCal_week}" > > required="true" > > > > value="#{regcalbean.currentEvent.dateChosen}"> > > > > </t:inputCalendar>     > > > > ... > > <h:message for="kalender" styleClass="error" /> > > </f:verbatim> > > </t:div> > > > > > > > > All is rendered well when the Use Case chosen equals "submitNew", so > > far no problem. > > > > The "currentEvent" for its value, is of Type CalendarEvent where the > > relevant part of that class states: > > ... /** > > * The chosen Date: > > */ > > private Date dateChosen; > > > > /** > > * @return Returns the dateChosen. > > */ > > public Date getDateChosen() { > > return dateChosen; > > } > > /** > > * @param dateChosen The dateChosen to set. > > */ > > public void setDateChosen(Date dateChosen) { > > this.dateChosen = dateChosen; > > } > > (in the constructor dateChosen is not instantiated to avoid a default > > date of today in the inputCalendar field - this makes no difference as > > to the issue however) > > > > The problem: > > The weird stuff is twofold: > > 1/ The inputCalendar is a "required" element. > > Yet, when I don't fill anything in, I get no complaints. > > 2/ It turns out that despite the fact all data inside the div is > > rendered, NONE of this data is actually saved. In fact whatever I type > > into it, the "value" stays "null". > > All data of currentEvent outside the div is saved correctly. > > > > Any ideas as to the "why"? > > I don't think this is how div is supposed to work, is it? > > > > Philippe > > > > > > > > > > > > > > > > -- > Don't answer to From: address! > Mail to this account are droped if not recieved via mailinglist. > To contact me direct create the mail address by > concatenating my forename to my senders domain. > -- Matthias Wessendorf Zülpicher Wall 12, 239 50674 Köln http://www.wessendorf.net mwessendorf-at-gmail-dot-com
