August 2008 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Assigned: (RF-4072) inplaceInput: long string displays in different ways in the View and Changed states

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-4072?page=com.atlassian.jira.plugin... ] Nick Belaevski reassigned RF-4072: ---------------------------------- Assignee: Nick Belaevski (was: Vladimir Molotkov) > inplaceInput: long string displays in different ways in the View and Changed states > ----------------------------------------------------------------------------------- > > Key: RF-4072 > URL: https://jira.jboss.org/jira/browse/RF-4072 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Environment: RF-3.2.2.BETA3 > jsp, facelets > test application > Tomcat 6.0 > all browsers > Reporter: Tatyana Romanovich > Assignee: Nick Belaevski > Priority: Minor > Fix For: 3.2.2 > > Attachments: inplaceInputViewChanged.gif > > > 1. Go to the test application > 2. Select inplaceInput component > 3. Enter very long string with words and spaces > 4. Left inplaceInput component, remember displaying text > 5. Click reRender button > 6. Verify displaying text: > FAILURE: long string displays in different ways in the View and Changed states -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Work started: (RF-4072) inplaceInput: long string displays in different ways in the View and Changed states

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-4072?page=com.atlassian.jira.plugin... ] Work on RF-4072 started by Nick Belaevski. > inplaceInput: long string displays in different ways in the View and Changed states > ----------------------------------------------------------------------------------- > > Key: RF-4072 > URL: https://jira.jboss.org/jira/browse/RF-4072 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.2 > Environment: RF-3.2.2.BETA3 > jsp, facelets > test application > Tomcat 6.0 > all browsers > Reporter: Tatyana Romanovich > Assignee: Nick Belaevski > Priority: Minor > Fix For: 3.2.2 > > Attachments: inplaceInputViewChanged.gif > > > 1. Go to the test application > 2. Select inplaceInput component > 3. Enter very long string with words and spaces > 4. Left inplaceInput component, remember displaying text > 5. Click reRender button > 6. Verify displaying text: > FAILURE: long string displays in different ways in the View and Changed states -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Commented: (RF-4075) Regression!!! Create "compatibility" flag to restore previous Iterable save state functionality broken with RF-2076

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-4075?page=com.atlassian.jira.plugin... ] Nick Belaevski commented on RF-4075: ------------------------------------ UIDataAdaptor#keepSaved(FacesContext) modifier changed to protected > Regression!!! Create "compatibility" flag to restore previous Iterable save state functionality broken with RF-2076 > ------------------------------------------------------------------------------------------------------------------- > > Key: RF-4075 > URL: https://jira.jboss.org/jira/browse/RF-4075 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.1 > Reporter: Michael Youngstrom > Assignee: Nick Belaevski > Fix For: Future > > > RF-2076 created a major Regression in RichFaces. This has been a long standing spec bug that a4j iterables were able to avoid for a long time. > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=153 > The problem is that now all my code depends upon the behavior of not discarding saved values. Would it be possible to add a "compatibility" flag to the iterable components that will allow them to behave the way they used to in not discarding saved state but allow those who want to match h:dataTable broken functionality can set it to true? > This issue is also related to RF-2076 which was rejected. This issue is different from RF-2076 because it is specifically requesting both functionalities. > Mike -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (RF-4075) Regression!!! Create "compatibility" flag to restore previous Iterable save state functionality broken with RF-2076

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-4075?page=com.atlassian.jira.plugin... ] Nick Belaevski updated RF-4075: ------------------------------- Fix Version/s: Future (was: 3.2.2) Consider implementing special attribute for this feature in the future > Regression!!! Create "compatibility" flag to restore previous Iterable save state functionality broken with RF-2076 > ------------------------------------------------------------------------------------------------------------------- > > Key: RF-4075 > URL: https://jira.jboss.org/jira/browse/RF-4075 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.1 > Reporter: Michael Youngstrom > Assignee: Nick Belaevski > Fix For: Future > > > RF-2076 created a major Regression in RichFaces. This has been a long standing spec bug that a4j iterables were able to avoid for a long time. > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=153 > The problem is that now all my code depends upon the behavior of not discarding saved values. Would it be possible to add a "compatibility" flag to the iterable components that will allow them to behave the way they used to in not discarding saved state but allow those who want to match h:dataTable broken functionality can set it to true? > This issue is also related to RF-2076 which was rejected. This issue is different from RF-2076 because it is specifically requesting both functionalities. > Mike -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Assigned: (RF-4075) Regression!!! Create "compatibility" flag to restore previous Iterable save state functionality broken with RF-2076

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-4075?page=com.atlassian.jira.plugin... ] Nick Belaevski reassigned RF-4075: ---------------------------------- Assignee: Nick Belaevski (was: Alexander Smirnov) > Regression!!! Create "compatibility" flag to restore previous Iterable save state functionality broken with RF-2076 > ------------------------------------------------------------------------------------------------------------------- > > Key: RF-4075 > URL: https://jira.jboss.org/jira/browse/RF-4075 > Project: RichFaces > Issue Type: Bug > Affects Versions: 3.2.1 > Reporter: Michael Youngstrom > Assignee: Nick Belaevski > Fix For: 3.2.2 > > > RF-2076 created a major Regression in RichFaces. This has been a long standing spec bug that a4j iterables were able to avoid for a long time. > https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=153 > The problem is that now all my code depends upon the behavior of not discarding saved values. Would it be possible to add a "compatibility" flag to the iterable components that will allow them to behave the way they used to in not discarding saved state but allow those who want to match h:dataTable broken functionality can set it to true? > This issue is also related to RF-2076 which was rejected. This issue is different from RF-2076 because it is specifically requesting both functionalities. > Mike -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-2287) autosized ModalPanel and Calendar: Calendar rendered broken.

by Ilya Shaikovsky (JIRA)

autosized ModalPanel and Calendar: Calendar rendered broken. ------------------------------------------------------------ Key: RF-2287 URL: http://jira.jboss.com/jira/browse/RF-2287 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.0 Reporter: Ilya Shaikovsky Assigned To: Nick Belaevski Fix For: 3.2.0 screens attached code: <rich:modalPanel id="_panel" minHeight="100" minWidth="200" moveable="true" autosized="true"> <f:facet name="header"> <h:outputText value="Events..." /> </f:facet> <f:facet name="controls"> <h:graphicImage value="/pages/montana.gif" onclick="Richfaces.hideModalPanel('_panel');" /> </f:facet> <h:outputText value="Eventsaaaaaaaaaaaaaaaa ..." /> <rich:calendar popup="true"/> </rich:modalPanel> B.t.w. JS error rised -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
11
0 / 0

[JBoss JIRA] Created: (RF-4125) rich:columns in rich:dataGrid description

by Svetlana mukhina (JIRA)

rich:columns in rich:dataGrid description ------------------------------------------ Key: RF-4125 URL: https://jira.jboss.org/jira/browse/RF-4125 Project: RichFaces Issue Type: Task Components: doc Affects Versions: 3.2.1 Reporter: Svetlana mukhina Assignee: Alex Tserbo Fix For: 3.2.2 Correct the guide according to the following post and reply of http://jboss.com/index.html?module=bb&op=viewtopic&t=140249 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-3920) graphValidator: java.lang.IllegalArgumentException in case using rich:graphValidator for h:panelGrid.

by Mikhail Vitenkov (JIRA)

graphValidator: java.lang.IllegalArgumentException in case using rich:graphValidator for h:panelGrid. ----------------------------------------------------------------------------------------------------- Key: RF-3920 URL: https://jira.jboss.org/jira/browse/RF-3920 Project: RichFaces Issue Type: Bug Affects Versions: 3.2.2 Environment: IE6, IE7, FF 3.0, Safari 3.1, Opera 9.5(3.2.2.BETA1) Reporter: Mikhail Vitenkov Assignee: Nick Belaevski Priority: Critical Step 1. Add panelGrid with validated inputs, surround it with rich:graphValidator: <rich:graphValidator value="#{graphValidator}"> <h:panelGrid columns="2" border="2" id="panelGridID"> <h:outputLabel for="mailValue" value="Mail validation:" /> <h:panelGroup> <h:inputText value="#{validator.mailValue}" id="mailValue"> <rich:ajaxValidator event="onchange"></rich:ajaxValidator> </h:inputText> <rich:message for="mailValue" showDetail="true" showSummary="true" /> </h:panelGroup> <h:outputLabel for="creditValue" value="CreditCard validation:" /> <h:panelGroup> <h:inputText value="#{validator.creditValue}" id="creditValue"> <rich:ajaxValidator event="onchange"></rich:ajaxValidator> </h:inputText> <rich:message for="creditValue" showDetail="true" showSummary="true" /> </h:panelGroup> <h:outputText value="total length should be less than 25" /> <a4j:commandButton value="validate all fields" reRender="panelGridID"></a4j:commandButton> </h:panelGrid> //Graph validator validates total length of all(2) inputs placed in panelGrid. Step 2. Add bean "validator": public class ValidatorBean implements TestValidable{ @Email(message="Mail validation failed!") private String mailValue; @CreditCardNumber(message="CreditCard validation failed!") private String creditValue; public ValidatorBean(){ this.mailValue = ""; this.creditValue = ""; } Getters & setters for 'mailValue' & 'creditValue' Step 3. Add "graphValidator" bean: public class GraphValidatorBean { private final List beans; @Valid public List getBeans() { return beans; } public GraphValidatorBean() { beans = new ArrayList(1); beans.add(new ValidatorBean()); } @Max(value=25,message="total length > 25") @Min(value=10,message="total length < 10") public int getTotal(){ int total = 0; for (Object bean : beans) { ValidatorBean vBean = (ValidatorBean) bean; total += vBean.getMailValue().toString.length() + vBean.getCreditValue().toString().length(); } return total; } } Step 4. Navigate on the page, contained tested validators. Step 5. Input values, valid for ajaxValidator & press "validate all fields" button. Actual behavior: Error occurs: java.lang.IllegalArgumentException: XClass not coming from this ReflectionManager implementation at org.hibernate.annotations.common.reflection.java.JavaReflectionManager.toClass(JavaReflectionManager.java:66) at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:142) at org.hibernate.validator.ClassValidator.createChildValidator(ClassValidator.java:296) at org.hibernate.validator.ClassValidator.initValidator(ClassValidator.java:218) at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:133) at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:104) at org.hibernate.validator.ClassValidator.<init>(ClassValidator.java:96) at org.richfaces.validator.BeanValidator.createValidator(BeanValidator.java:272) at org.richfaces.validator.BeanValidator.getValidator(BeanValidator.java:238) at org.richfaces.validator.BeanValidator.validateGraph(BeanValidator.java:177) at org.richfaces.component.UIGraphValidator.processUpdates(UIGraphValidator.java:87) at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:678) at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:678) at javax.faces.component.UIComponentBase.processUpdates(UIComponentBase.java:678) at javax.faces.component.UIForm.processUpdates(UIForm.java:91) at org.ajax4jsf.component.AjaxViewRoot$2.invokeContextCallback(AjaxViewRoot.java:412) at org.ajax4jsf.component.ContextCallbackWrapper.invokeContextCallback(ContextCallbackWrapper.java:24) at org.ajax4jsf.component.AjaxViewRoot.processPhase(AjaxViewRoot.java:235) at org.ajax4jsf.component.AjaxViewRoot.processUpdates(AjaxViewRoot.java:428) at org.apache.myfaces.lifecycle.UpdateModelValuesExecutor.execute(UpdateModelValuesExecutor.java:33) at org.apache.myfaces.lifecycle.LifecycleImpl.executePhase(LifecycleImpl.java:103) at org.apache.myfaces.lifecycle.LifecycleImpl.execute(LifecycleImpl.java:76) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:148) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.ajax4jsf.webapp.BaseXMLFilter.doXmlFilter(BaseXMLFilter.java:154) at org.ajax4jsf.webapp.BaseFilter.handleRequest(BaseFilter.java:265) at org.ajax4jsf.webapp.BaseFilter.processUploadsAndHandleRequest(BaseFilter.java:376) at org.ajax4jsf.webapp.BaseFilter.doFilter(BaseFilter.java:503) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) at java.lang.Thread.run(Unknown Source) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

3
3
0 / 0

[JBoss JIRA] Created: (RF-4097) bean validator demo

by Ilya Shaikovsky (JIRA)

bean validator demo ------------------- Key: RF-4097 URL: https://jira.jboss.org/jira/browse/RF-4097 Project: RichFaces Issue Type: Sub-task Affects Versions: 3.2.1 Reporter: Ilya Shaikovsky Assignee: Ilya Shaikovsky Fix For: 3.2.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (RF-4065) Annotate docs nightlies with "nightly" banners

by Nick Belaevski (JIRA)

Annotate docs nightlies with "nightly" banners ---------------------------------------------- Key: RF-4065 URL: https://jira.jboss.org/jira/browse/RF-4065 Project: RichFaces Issue Type: Task Affects Versions: 3.2.2 Reporter: Nick Belaevski Assignee: Svetlana mukhina Fix For: 3.2.2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 8 months

4
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues August 2008