[JBoss JIRA] (RF-12830) viewId?faces-redirect=true& includeViewParams=true doesn't work anymore
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12830?page=com.atlassian.jira.plugin.s... ]
Brian Leathem resolved RF-12830.
--------------------------------
Labels: redirect redirect_url (was: redirect redirect_url waiting_on_user)
Resolution: Out of Date
Great, thanks for reporting the issue and verifying the fix!
> viewId?faces-redirect=true&includeViewParams=true doesn't work anymore
> --------------------------------------------------------------------------
>
> Key: RF-12830
> URL: https://issues.jboss.org/browse/RF-12830
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.1
> Reporter: Dmitry Shultz
> Labels: redirect, redirect_url
>
> Updated RF from 4.2.2.Final to the recent 4.3.1.CR1 and lost the redirect functionality.
> This code worked before:
> String viewId = FacesContext.getCurrentInstance().getViewRoot().getViewId();
> return viewId + "?faces-redirect=true&includeViewParams=true";
> But now there is no redirect happens.
--
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
11 years, 11 months
[JBoss JIRA] (RF-12836) Component control doesn't work when a button is disabled
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12836?page=com.atlassian.jira.plugin.s... ]
Brian Leathem commented on RF-12836:
------------------------------------
Replied via the linked forum.
> Component control doesn't work when a button is disabled
> --------------------------------------------------------
>
> Key: RF-12836
> URL: https://issues.jboss.org/browse/RF-12836
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.3.0.Final
> Reporter: Migore S
>
> I'm trying to add a rich:componentControl to show a popup when a butotn is clicked, but when the button is disabled it doesn't work.
> {code}
> <h:commandButton id="delete-all-button" value="#{msgs.geral_excluir_selecionados}"
> rendered="#{bean.dataModel.rowCount != 0}"
> type="button" disabled="true">
> <rich:componentControl event="click" target="confirm-popup" operation="show">
> <a4j:param noEscape="true" value="event" />
> <rich:hashParam>
> <f:param name="width" value="500" />
> <f:param name="height" value="300" />
> <f:param name="minWidth" value="300" />
> <f:param name="minHeight" value="150" />
> <a4j:param noEscape="true" name="left" value="(jQuery(window).width()/2)-250" />
> <a4j:param noEscape="true" name="top" value="(jQuery(window).height()/2)-150" />
> </rich:hashParam>
> </rich:componentControl>
> </h:commandButton>
> {code}
> If I remove the disabled attribute it works.
> Issue on the forum: https://community.jboss.org/thread/222320
--
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
11 years, 11 months
[JBoss JIRA] (RF-12836) Component control doesn't work when a button is disabled
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12836?page=com.atlassian.jira.plugin.s... ]
Brian Leathem updated RF-12836:
-------------------------------
Labels: waiting_on_user (was: )
> Component control doesn't work when a button is disabled
> --------------------------------------------------------
>
> Key: RF-12836
> URL: https://issues.jboss.org/browse/RF-12836
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: component-panels-layout-themes
> Affects Versions: 4.3.0.Final
> Reporter: Migore S
> Labels: waiting_on_user
>
> I'm trying to add a rich:componentControl to show a popup when a butotn is clicked, but when the button is disabled it doesn't work.
> {code}
> <h:commandButton id="delete-all-button" value="#{msgs.geral_excluir_selecionados}"
> rendered="#{bean.dataModel.rowCount != 0}"
> type="button" disabled="true">
> <rich:componentControl event="click" target="confirm-popup" operation="show">
> <a4j:param noEscape="true" value="event" />
> <rich:hashParam>
> <f:param name="width" value="500" />
> <f:param name="height" value="300" />
> <f:param name="minWidth" value="300" />
> <f:param name="minHeight" value="150" />
> <a4j:param noEscape="true" name="left" value="(jQuery(window).width()/2)-250" />
> <a4j:param noEscape="true" name="top" value="(jQuery(window).height()/2)-150" />
> </rich:hashParam>
> </rich:componentControl>
> </h:commandButton>
> {code}
> If I remove the disabled attribute it works.
> Issue on the forum: https://community.jboss.org/thread/222320
--
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
11 years, 11 months
[JBoss JIRA] (RF-12830) viewId?faces-redirect=true& includeViewParams=true doesn't work anymore
by Dmitry Shultz (JIRA)
[ https://issues.jboss.org/browse/RF-12830?page=com.atlassian.jira.plugin.s... ]
Dmitry Shultz commented on RF-12830:
------------------------------------
tried it with 4.3.1.Final (on jboss-eap-6 alpha) redirects as expected, not a problem anymore, Thanks!
> viewId?faces-redirect=true&includeViewParams=true doesn't work anymore
> --------------------------------------------------------------------------
>
> Key: RF-12830
> URL: https://issues.jboss.org/browse/RF-12830
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.1
> Reporter: Dmitry Shultz
> Labels: redirect, redirect_url, waiting_on_user
>
> Updated RF from 4.2.2.Final to the recent 4.3.1.CR1 and lost the redirect functionality.
> This code worked before:
> String viewId = FacesContext.getCurrentInstance().getViewRoot().getViewId();
> return viewId + "?faces-redirect=true&includeViewParams=true";
> But now there is no redirect happens.
--
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
11 years, 11 months
[JBoss JIRA] (RF-12831) <rich:validator/> performs ajax validation without updating underlying model field
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/RF-12831?page=com.atlassian.jira.plugin.s... ]
Brian Leathem reassigned RF-12831:
----------------------------------
Assignee: Pavol Pitonak
Would you please verify this with a framework test?
> <rich:validator/> performs ajax validation without updating underlying model field
> ----------------------------------------------------------------------------------
>
> Key: RF-12831
> URL: https://issues.jboss.org/browse/RF-12831
> Project: RichFaces
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 4.3.0.Final
> Environment: JBoss eap 6.0.0, Win 7
> Reporter: Kamil Roman
> Assignee: Pavol Pitonak
> Priority: Minor
>
> Not sure if it's a bug or a feature, but field annotated with {code}<rich:validator/>{code} with a validation method set with {code}validator{code} attribute gets validated without updating the underlying model field. My code is something like this:
> {code:title=Model.java}
> public class Model {
> //...
> public Date getValidFrom() {/*...*/}
> public Date getValidTo() {/*...*/}
> }
> {code}
> {code:title=ModelValidator.java}
> public class ModelValidator{
> private Model model;
> public boolean isValidToAfterValidFrom() {
> return model.getValidTo().after(model.getValidFrom());
> }
> }
> {code}
> {code:title=model_form.xml}
> <c:set var="model" value="#{ModelBean.model}"/>
> <h:outputLabel value="#{labels.getLabel('valid_from')}" for="validFrom" />
> <rich:calendar value="#{model.validFrom}" id="validFrom" >
> <rich:validator/>
> </rich:calendar>
> <rich:message for="validFrom"/>
>
> <h:outputLabel value="#{labels.getLabel('valid_to')}" for="validTo" />
> <rich:calendar value="#{model.validTo}" id="validTo" validator="#{modelBean.validateValidTo}">
> <rich:validator event="inputblur"/>
> </rich:calendar>
> <rich:message for="validTo"/>
> {code}
> {code:title=ModelBean.java}
> public class ModelBean {
> public Model getModel() {/*..*/}
> private ModelValidator validator;
> //...
> public validateValidTo(FacesContext context, UIComponent toValidate, Object value) {
> if(!validator.isValidToAfterValidFrom()) {
> FacesMessage message = new FacesMessage(FacesMessage.SEVERITY_ERROR, labelBean.getLabel("valid.to.not.after.valid.from.error"), null);
> throw new ValidatorException(message);
> }
> }
> {code}
> The getModel() method returns the same Model instance as is used by the ModelValidator in ModelBean.
> Now, the testcase is:
> 1. User selects validTo earlier than ValidFrom (on a valid Model instance)
> 2. Validation passes as the underlying model value is not updated (validator refers to the same Model instance as ModelBean)
> 3. User submits the form.
> 4. System displays error message as server-side validation on submit is performed after applying request values.
> 5. User corrects the value in validTo field.
> 6. System still displays error message as validation fails, because the new value is not applied to the model (model holds the invalid value applied during failed submit).
> If this is not a bug, but a feature, it would be great if you included this behaviour in the docs!
--
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
11 years, 11 months