[JBoss JIRA] (RF-13108) rich:calendar nested a4j:ajax event not firing
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-13108?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-13108:
------------------------------------
Are you saying that if the validators are not present, the event is correctly fired?
> rich:calendar nested a4j:ajax event not firing
> ----------------------------------------------
>
> Key: RF-13108
> URL: https://issues.jboss.org/browse/RF-13108
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-a4j-core, component-validators
> Affects Versions: 4.3.2
> Environment: jboss 7.1.3 richfaces 4.3.2.final, chrome
> Reporter: nathan dennis
> Labels: a4j:ajax, rich:calendar, rich:message, waiting_on_user
>
> nested a4j:ajax change event isn't functioning as expected. On "change" event, the expect result is that the value is moved into the target Date field of the backing bean. When using a4j:ajax, this does not happen.
> After speaking with ppitonak he believe that the order of the ajax with relation to the validators was import. however after closer inspection, the value wasn't making back to the bean even when the event was fired even with the order reversed.
> Logically the first date should be submitted to the backing bean on change even and made available for validation in the second dates validator. works with f:ajax.. doesnt work with a4j:ajax.
> {code}
> Request URL:http://oasis.monarchnc.org:10001/oasis/screening/edit.xhtml?cid=2
> Request Method:POST
> Status Code:200 OK
> Request Headersview source
> Accept:*/*
> Accept-Charset:ISO-8859-1,utf-8;q=0.7,*;q=0.3
> Accept-Encoding:gzip,deflate,sdch
> Accept-Language:en-US,en;q=0.8
> Connection:keep-alive
> Content-Length:870
> Content-type:application/x-www-form-urlencoded;charset=UTF-8
> Cookie:JSESSIONID="gOuCLop-DL7U6D3fbNhptHmw.slave:server-three"; csfcfc=11Xfn_12Xfn; __utma=69432588.533798156.1374674467.1374674467.1374674467.1; __utmz=69432588.1374674467.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); org.monarchnc.commandcenter.location=1; org.monarchnc.commandcenter.security=NDNlZGQ3ZDU3NjIxYzI4YjM4YzZlOTM0YzQ3ZjAxYWQ_
> Faces-Request:partial/ajax
> Host:oasis.monarchnc.org:10001
> Origin:http://oasis.monarchnc.org:10001
> Referer:http://oasis.monarchnc.org:10001/oasis/screening/edit.xhtml?cid=2&id=143&dsRid=197&windowId=-9720
> User-Agent:Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.172 Safari/537.22
> Query String Parametersview sourceview URL encoded
> cid:2
> Form Dataview sourceview URL encoded
> create:create
> create:medrecordnumber:
> create:patientName:Ritchard Trickle
> create:patientPhone:
> create:patientEmail:
> create:startTimeOverrideInputDate:30/7/13 04:24 PM
> create:startTimeOverrideInputCurrentDate:07/2013
> create:endTimeOverrideInputDate:01/8/13 05:58 PM
> create:endTimeOverrideInputCurrentDate:08/2013
> create:screeningBeanScreeningProviderValue:
> create:screeningBeanScreeningProviderInput:dennis, nathan
> javax.faces.ViewState:-4869776129569305131:8783263118910249789
> javax.faces.source:create:startTimeOverride
> javax.faces.partial.event:change
> javax.faces.partial.execute:create:startTimeOverride @component
> javax.faces.partial.render:@component
> javax.faces.behavior.event:change
> org.richfaces.ajax.component:create:startTimeOverride
> rfExt:null
> AJAX:EVENTS_COUNT:1
> javax.faces.partial.ajax:true
> Response Headersview source
> Cache-Control:no-cache
> Connection:close
> Content-Type:text/xml;charset=UTF-8
> Date:Thu, 01 Aug 2013 15:59:07 GMT
> Server:Apache-Coyote/1.1
> Transfer-Encoding:chunked
> X-Powered-By:JSF/2.0
> {code}
> {code:xml}
> <?xml version='1.0' encoding='UTF-8' ?>
> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
> <ui:composition xmlns="http://www.w3.org/1999/xhtml"
> xmlns:h="http://java.sun.com/jsf/html"
> xmlns:f="http://java.sun.com/jsf/core"
> xmlns:ui="http://java.sun.com/jsf/facelets"
> xmlns:c="http://java.sun.com/jsp/jstl/core"
> xmlns:a4j="http://richfaces.org/a4j"
> xmlns:rich="http://richfaces.org/rich"
> template="/resources/scaffold/pageTemplate.xhtml">
> <f:metadata>
> <f:viewParam name="id" value="#{screeningBean.id}"/>
> </f:metadata>
> <ui:define name="main">
> <h:form id="create">
>
> <h:panelGrid columnClasses="label,component,required" columns="3">
> <h:outputLabel for="startTimeOverride" value="Start Time Override:"/>
> <rich:calendar value="#{screeningBean.screening.beginTime}" id="startTimeOverride"
> popup="true" datePattern="dd/M/yy hh:mm a" required="true"
> showApplyButton="true" >
> <f:validateRequired />
> <a4j:ajax event="change" bypassUpdates="#{true}"/>
> </rich:calendar>
> <rich:message for="startTimeOverride" ajaxRendered="true" />
> <h:outputLabel for="endTimeOverride" value="End Time Override:" />
> <rich:calendar value="#{screeningBean.screening.endTime}" id="endTimeOverride"
> popup="true" datePattern="dd/M/yy hh:mm a"
> showApplyButton="true" >
> <f:validateRequired />
> <f:validator validatorId="dateRangeValidator" />
> <rich:validator />
> <a4j:ajax event="change" bypassUpdates="#{true}"/>
> </rich:calendar>
> <rich:message for="endTimeOverride" ajaxRendered="true" />
> </h:panelGrid>
> <div class="buttons">
> <a4j:commandButton value="Complete"
> action="#{screeningBean.updateScreening(2)}"
> execute="@form"
> onclick="this.disabled=true; var that = this; setTimeout(function() that.disabled=false;},500);"
> styleClass="btn btn-primary btn-primary-a4j" />
> </div>
> </h:form>
> </ui:define>
> </ui:composition>
> {code}
> {code:title=DateRangeValidator.java}
> /**************************************************************
> * Copyright (c) 2012 - 2013, Monarch, All rights reserved.
> *
> * @author Nathan Dennis
> *
> */
> package org.monarchnc.view.validators;
> import java.text.DateFormat;
> import java.text.SimpleDateFormat;
> import java.util.Date;
> import javax.faces.application.FacesMessage;
> import javax.faces.component.UIComponent;
> import javax.faces.component.UIInput;
> import javax.faces.context.FacesContext;
> import javax.faces.validator.FacesValidator;
> import javax.faces.validator.Validator;
> import javax.faces.validator.ValidatorException;
> import javax.persistence.EntityManager;
> import org.apache.deltaspike.core.api.provider.BeanProvider;
> import org.monarchnc.view.ScreeningBean;
> // TODO: Auto-generated Javadoc
> /**
> * The Class DateRangeValidator.
> */
> @FacesValidator("dateRangeValidator")
> public class DateRangeValidator implements Validator {
>
>
> /* (non-Javadoc)
> * @see javax.faces.validator.Validator#validate(javax.faces.context.FacesContext, javax.faces.component.UIComponent, java.lang.Object)f
> */
> public void validate(final FacesContext ctx, final UIComponent component, final Object value) throws ValidatorException {
>
> ScreeningBean screeningBean = BeanProvider.getContextualReference(screeningBean.class, false);
>
> Date date =(Date) value;
> if(screeningBean.getScreening().getBeginTime() != null && date != null)
> if(!date.after(screeningBean.getScreening().getBeginTime())){
> throw new ValidatorException(new FacesMessage(FacesMessage.SEVERITY_ERROR,"End Date must be after Start Date!!.\n","End Date must be after Start Date!!\n"));
>
> }
>
>
> }
> }
> {code}
> {code:title=ScreeningBean.java}
> @Named
> @Transactional
> @ConversationScoped
> public class ScreeningBean implements Serializable{
> Screening screening = new Screening();
> public Class<? extends ViewConfig> claim(){
> if (this.conversation.isTransient())
> {
> this.conversation.begin();
> }...
> }
> public Screening getScreening() {
> return screening;
> }
> public void setScreening(Screening screening) {
> this.screening = screening;
> }
> }
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-13094) Wrong extendedDataTable header widths when narrowing columns
by a a (JIRA)
[ https://issues.jboss.org/browse/RF-13094?page=com.atlassian.jira.plugin.s... ]
a a updated RF-13094:
---------------------
Attachment: Layout.jpg
in the screenshot i just attached it is more obvious what the problem ist
> Wrong extendedDataTable header widths when narrowing columns
> ------------------------------------------------------------
>
> Key: RF-13094
> URL: https://issues.jboss.org/browse/RF-13094
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-tables
> Affects Versions: 4.3.2
> Environment: GlassFish 3.1.2.2 with Mojarra 2.1.23, tested on Firefox 22 and Chrome 28.
> Reporter: Salvo Isaja
> Fix For: 4.3.4
>
> Attachments: Layout.jpg
>
>
> When reducing column widths on an extendedDataTable narrower than the viewport, columns of the table body are resized correctly, but the columns in the table header stay larger, until the viewport is narrowed too.
> This is reproducible in the online RichFaces 4.3.2 showcase with no modifications.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-13116) Using filters with paging / default filter value in extendeddatatable
by John Strandmyr (JIRA)
John Strandmyr created RF-13116:
-----------------------------------
Summary: Using filters with paging / default filter value in extendeddatatable
Key: RF-13116
URL: https://issues.jboss.org/browse/RF-13116
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Reporter: John Strandmyr
Priority: Critical
Fix For: 3.3.4.Final
I've got an extededdatatable from richfaces and if i add a default value to the filter, so that some rows are excluded on first rendering, and then change the filter to show the rows that were hidden, I don't get any calls to the actionlisteners on the rows that were hidden at first.
It works fine on those rows that was shown in the first page load, but not on those hidden.
The same issue appears when i use paging, and some rows are on page two. if i use the filter to show some rows from another page, the actionlistener isnt triggered. I can still click on those rows that was apparent on the first page, but not on the other pages.
If I don't have a default filter, or a pager, i can add and remove filtering and everything is fine.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-13090) <rich:jQuery> named functions not working as documented
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13090?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13090:
----------------------------
Fix Version/s: 4.5.0.Alpha1
> <rich:jQuery> named functions not working as documented
> -------------------------------------------------------
>
> Key: RF-13090
> URL: https://issues.jboss.org/browse/RF-13090
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-misc
> Affects Versions: 4.3.2
> Reporter: Vincent Wülcknitz
> Priority: Minor
> Labels: richfaces
> Fix For: 4.5.0.Alpha1
>
> Original Estimate: 1 hour
> Remaining Estimate: 1 hour
>
> I have found some strange behaviour with the <rich:jQuery> component when you implement named functions like described in the component reference:
> http://docs.jboss.org/richfaces/latest_4_3_X/Component_Reference/en-US/ht...
> If I implement the given code from the reference:
> {code}
> <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this)" />
> <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this)" />
> ...
> <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" />
> <rich:jQuery name="releasePic" query="animate({width:'50px'})"/>
> {code}
> only the onmouseover calls will work. The prictures will get bigger but not smaller onmouseout.
> I found out that if I do some small changes to the onmouseout call it works fine:
> {code}
> <h:graphicImage width="50" value="/images/price.png" onmouseover="enlargePic(this, {pwidth:'60px'})" onmouseout="releasePic(this,{})" />
> <h:graphicImage width="50" value="/images/discount.png" onmouseover="enlargePic(this, {pwidth:'100px'})" onmouseout="releasePic(this,{})" />
> ...
> <rich:jQuery name="enlargePic" query="animate({width:options.pwidth})" />
> <rich:jQuery name="releasePic" query="animate({width:'50px'})"/>
> {code}
> It only works when adding a second parameter to the call even if its empty.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-11402) Metamer: rich:inplaceSelect: scroller disappear when move by mouse
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-11402?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-11402:
----------------------------
Fix Version/s: 4.5.0.Alpha1
(was: 5-Future)
> Metamer: rich:inplaceSelect: scroller disappear when move by mouse
> ------------------------------------------------------------------
>
> Key: RF-11402
> URL: https://issues.jboss.org/browse/RF-11402
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-selects
> Affects Versions: 4.1.0.Milestone2, 4.2.2.Final, 4.3.0.M3, 4.3.0.CR1
> Environment: RichFaces 4.1.0.20110910-M2 r.
> Metamer 4.1.0.20110910-M2 r.22701
> Mojarra 2.0.4-b09-jbossorg-4
> JBoss Web 7.0.1.Final
> Java(TM) SE Runtime Environment 1.6.0_26-b03 @ Linux
> IE8 & IE9 & Chrome
> Reporter: Ján Jamrich
> Labels: IE10, IE8, IE9, chrome
> Fix For: 4.5.0.Alpha1
>
>
> When click into inplaceSelect input, an list of items appear. But if try move scroller to see more items, scroller disappear, and whole suggestion list disappear as well.
> This happens only in IE9, and chrome, not in Firefox.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-13107) rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13107:
----------------------------
Workaround Description:
Workaround is using limitRender:
{code:xml}
<a4j:commandButton value="Submit" execute="content" render="content"
limitRender="true" />
{code}
Another workaround is using mode="ajax" for tabPanel:
{code:xml}
<rich:tabPanel switchType="ajax">
{code}
Another workaround is to set {{ajaxRendered="false"}} to the rich:message(s) that might not get rendered.
was:Workaround for this bug is to set ajaxRendered="false" to the rich:message(s) that might not get rendered.
> rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: bug_reproducer.zip
>
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
> Snipper:
> {code:xml}
> <h:form>
> <rich:tabPanel switchType="server">
> <rich:tab>
> <h:inputText id="surname" value="#{richBean.surname}">
> <f:validateLength minimum="10"/>
> </h:inputText>
> <rich:message for="surname"/>
> </rich:tab>
> <rich:tab>
> <h:panelGroup id="content">
> <h:inputText id="name" value="#{richBean.name}">
> <f:validateLength minimum="6"/>
> </h:inputText>
> <rich:message for="name"/>
> </h:panelGroup>
> <a4j:commandButton value="Submit" execute="content" render="content" />
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-13107) rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13107:
----------------------------
Description:
We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
Note that:
1) switchType must be set to server to ensure the A's rich:message is really not on the page.
2) button in B must re-render only content of B
This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
Please find the enclosed reproducer.
Snipper:
{code:xml}
<h:form>
<rich:tabPanel switchType="server">
<rich:tab>
<h:inputText id="surname" value="#{richBean.surname}">
<f:validateLength minimum="10"/>
</h:inputText>
<rich:message for="surname"/>
</rich:tab>
<rich:tab>
<h:panelGroup id="content">
<h:inputText id="name" value="#{richBean.name}">
<f:validateLength minimum="6"/>
</h:inputText>
<rich:message for="name"/>
</h:panelGroup>
<a4j:commandButton value="Submit" execute="content" render="content" />
</rich:tab>
</rich:tabPanel>
</h:form>
{code}
was:
We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
Note that:
1) switchType must be set to server to ensure the A's rich:message is really not on the page.
2) button in B must re-render only content of B
This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
Please find the enclosed reproducer.
> rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: bug_reproducer.zip
>
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
> Snipper:
> {code:xml}
> <h:form>
> <rich:tabPanel switchType="server">
> <rich:tab>
> <h:inputText id="surname" value="#{richBean.surname}">
> <f:validateLength minimum="10"/>
> </h:inputText>
> <rich:message for="surname"/>
> </rich:tab>
> <rich:tab>
> <h:panelGroup id="content">
> <h:inputText id="name" value="#{richBean.name}">
> <f:validateLength minimum="6"/>
> </h:inputText>
> <rich:message for="name"/>
> </h:panelGroup>
> <a4j:commandButton value="Submit" execute="content" render="content" />
> </rich:tab>
> </rich:tabPanel>
> </h:form>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-13107) rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated RF-13107:
----------------------------
Summary: rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error (was: rich:message in tabPanel is not shown if other message is not rendered)
> rich:message is renderer even though it is in non-active switchable panel, causing JSF to fail with mallformedXML error
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: bug_reproducer.zip
>
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-13107) rich:message in tabPanel is not shown if other message is not rendered
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč edited comment on RF-13107 at 8/2/13 3:49 AM:
---------------------------------------------------------
The {{j_idt8:j_idt11}} stands for the {{<rich:message for="surname"/>}}.
----
Workaround is using {{limitRender}}:
{code:xml}
<a4j:commandButton value="Submit" execute="content" render="content" limitRender="true" />
{code}
Another workaround is using {{mode="ajax"}} for {{tabPanel}}:
{code:xml}
<rich:tabPanel switchType="ajax">
{code}
was (Author: lfryc):
The {{j_idt8:j_idt11}} stands for the {{<rich:message for="surname"/>}}.
----
Workaround is using {{limitRender}}:
{code:xml}
<a4j:commandButton value="Submit" execute="content" render="content" limitRender="true" />
{code}
> rich:message in tabPanel is not shown if other message is not rendered
> ----------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: bug_reproducer.zip
>
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months
[JBoss JIRA] (RF-13107) rich:message in tabPanel is not shown if other message is not rendered
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/RF-13107?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč commented on RF-13107:
---------------------------------
The {{j_idt8:j_idt11}} stands for the {{<rich:message for="surname"/>}}.
----
Workaround is using {{limitRender}}:
{code:xml}
<a4j:commandButton value="Submit" execute="content" render="content" limitRender="true" />
{code}
> rich:message in tabPanel is not shown if other message is not rendered
> ----------------------------------------------------------------------
>
> Key: RF-13107
> URL: https://issues.jboss.org/browse/RF-13107
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-validators
> Affects Versions: 4.3.2
> Reporter: Jonáš Trantina
> Assignee: Brian Leathem
> Fix For: 4.3.4
>
> Attachments: bug_reproducer.zip
>
>
> We have a form with a tabPanel component with two tabs A and B. In A there is an input and its rich:message in B the same plus a button that submits and re-renders B. When B is opened (thus A is not rendered) and the form is submitted and validation fails, then no message is shown.
> Note that:
> 1) switchType must be set to server to ensure the A's rich:message is really not on the page.
> 2) button in B must re-render only content of B
> This is only a specific scenario, the issue might occur also in other situations (e.g. global messages tag outside of tabPanel is not rendered).
> Please find the enclosed reproducer.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 9 months