This content has been marked as final.
Show 2 replies
-
1. Re: various components not working
ilya_shaikovsky Jul 7, 2008 8:13 AM (in response to janson12)every case should be carefully explained to became a bug.
-
2. Re: various components not working
janson12 Jul 10, 2008 5:35 AM (in response to janson12)Sorry for the delay. i heavily doubt that it is a bug. Anyway, here's an example scenario: the user can reRender a panel via drop down menu . The rerendered area in this case has a suggestionbox and two calendars to define a time range. The whole thing looks (a bit simplified) like this:
<h:form id="selectionForm"> <t:saveState value="#{myBean}" id="myBean"/> <rich:panel header="Analysis" > <h:panelGrid > <h:selectOneMenu value="#{myBean.targetView}" > <f:selectItems value="#{myBean.analysisCriteriaList}" /> <a4j:support event="onchange" action="#{myBean.loadView}" reRender="ajaxArea"/> </h:selectOneMenu> <rich:panel > <h:panelGrid columns="2" > <h:outputText value="#{analyze_msg.personalNumber}"/> <h:panelGroup> <h:inputText id="persNumber" value="#{myBean.employeeNumber}"/> <a4j:region> <rich:suggestionbox id="suggestionBoxCC" for="persNumber" fetchValue="#{result.number}" suggestionAction="#{OrgaEditPerson.autocomplete}" var="result" height="150" width="250" nothingLabel="#{analyze_msg.no_item_found}" eventsQueue="personQueue" > <h:column> <h:outputText value="#{result.number}" /> </h:column> <h:column> <h:outputText value="#{result.name}" /> </h:column> </rich:suggestionbox> </a4j:region> </h:panelGroup> <h:panelGroup/> <rich:spacer height="12" /> <h:outputText value="#{analyze_msg.date_from}:" /> <rich:calendar value="#{myBean.fromDate}" datePattern="#{myBean.datePatternDefault}"/> <h:outputText value="#{analyze_msg.date_to}:" /> <rich:calendar value="#{myBean.toDate}" datePattern="#{myBean.datePatternDefault}"/> </h:panelGrid> </rich:panel> <a4j:commandButton value="#{analyze_msg.button_analyze}" action="#{myBean.analyze}" reRender="ajaxArea"/> </h:panelGrid> </rich:panel> </h:form>
As i said it works properly in 9 out of 10 times but sometimes the pop up components seem to be locked. This occurs only once at the beginning -after a of the respective page all components (even those on other pages) work as expected.