July 2009 - richfaces-issues - Jboss List Archives

[JBoss JIRA] Updated: (RF-7606) SelectUtils.getConvertedUISelectManyValue more restrictive than it needs to be

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-7606?page=com.atlassian.jira.plugin... ] Nick Belaevski updated RF-7606: ------------------------------- Component/s: component Fix Version/s: Future Affects Version/s: 3.3.2.CR1 Assignee: Nick Belaevski > SelectUtils.getConvertedUISelectManyValue more restrictive than it needs to be > ------------------------------------------------------------------------------ > > Key: RF-7606 > URL: https://jira.jboss.org/jira/browse/RF-7606 > Project: RichFaces > Issue Type: Feature Request > Components: component > Affects Versions: 3.3.2.CR1 > Environment: JBoss 4.2.2.GA, RichFaces 3.2.1.GA, windows xp sp2 x86 > Reporter: Andr? Fernandes > Assignee: Nick Belaevski > Priority: Minor > Fix For: Future > > > on line 189 of the org.ajax4jsf.util.SelectUtils we see > if (List.class.isAssignableFrom(valueType)) > .... > But I think it don't need to be List. > It should be Collection because it is less restrictive and works just fine. :) > I found this when I was using an Entity with a Collection<AClass> and a > <rich:pickList ...> > <s:selectItems ...></s:selectItems> > </rich:pickList> > on the view. > When I was posting back to the server, it was throwing an exception (think it is IllegalArgumentException). > Then I get the source for RichFaces and find out that the SelectUtils.getConvertedUISelectManyValue was not expecting a Collection, but instead it was expecting a List. > Then I change my entity to have a List<AClass> and it works just fine. > If the line 189 just change to if (Collection.class.isAssignableFrom(valueType)) it should work. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-7551) Unable to view forecolor and backcolor features of TinyMCE under <rich:editor> correctly. in MSIE8

by Akash Singla (JIRA)

Unable to view forecolor and backcolor features of TinyMCE under <rich:editor> correctly. in MSIE8 -------------------------------------------------------------------------------------------------- Key: RF-7551 URL: https://jira.jboss.org/jira/browse/RF-7551 Project: RichFaces Issue Type: Bug Components: browser compatibility Affects Versions: 3.3.1 Reporter: Akash Singla Priority: Minor Attachments: screenshot-1.jpg I am using richFaces 3.3.1 version. I used rich:editor tag with forecolor and backcolor properties. There are 2 issues: --- These 2 properties are visible properly in every browser except MSIE 8. --- These 2 properties appear as readonly in Chrome and Safari. --- The preview property requires content_css property to be defined to run properly. I have tried original TinyMCE version. It works fine. Thanks. -- 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

16 years, 8 months

3
4
0 / 0

[JBoss JIRA] Assigned: (RF-7604) a4j:actionparam doesn't support comma in value

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-7604?page=com.atlassian.jira.plugin... ] Nick Belaevski reassigned RF-7604: ---------------------------------- Assignee: Alex Kolonitsky (was: Nick Belaevski) > a4j:actionparam doesn't support comma in value > ---------------------------------------------- > > Key: RF-7604 > URL: https://jira.jboss.org/jira/browse/RF-7604 > Project: RichFaces > Issue Type: Bug > Components: component-a4j-core > Affects Versions: 3.3.2.CR1 > Environment: richfaces-ui-3.2.1.GA > Tomcat 6.0.16 > Facelets 1.1.14 > Reporter: Stephen Kinser > Assignee: Alex Kolonitsky > Priority: Minor > Fix For: 3.3.2.CR1 > > > I attempt to define a value that contains a comma, as follows: > <a4j:actionparam name="metricName" value="Host:type=Processors,name=CPU.UserMode" assignTo="#{GraphPageBean.metricName}"/> > Here's the method that I expect to be passed Host:type=Processors,name=CPU.UserMode: > public void setMetricName(String metricName) { > this.metricName = metricName; > } > setMetricName is called with a metricName value of "Host:type=Processors". I modified the value to use a '|' instead of a ',' and I got the full value of Host:type=Processors|name=CPU.UserMode. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (RF-7607) web.xml context-param org.ajax4jsf.VIEW_HANDLERS should allow newlines

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-7607?page=com.atlassian.jira.plugin... ] Nick Belaevski updated RF-7607: ------------------------------- Component/s: core Fix Version/s: Future Affects Version/s: 3.3.2.CR1 Assignee: Nick Belaevski > web.xml context-param org.ajax4jsf.VIEW_HANDLERS should allow newlines > ---------------------------------------------------------------------- > > Key: RF-7607 > URL: https://jira.jboss.org/jira/browse/RF-7607 > Project: RichFaces > Issue Type: Feature Request > Components: core > Affects Versions: 3.3.2.CR1 > Environment: java 1.5 > myfaces 1.2.3 > rf 3.2.1.CR8 > facelets 1.1.14 > Reporter: Andreas Höhmann > Assignee: Nick Belaevski > Fix For: Future > > > if i need multiple viewhandlers (faclets) the context-param org.ajax4jsf.VIEW_HANDLERS is the right place ... but ... there is limitation ... all defined viewhandlers must places in ONE line (no linebreaks). > current version: > <context-param> > <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name> > <param-value> > com.sun.facelets.FaceletViewHandler,de.ahoehma.jsf.ReverseProxyViewHandler > </param-value> > </context-param> > preferred version: > <context-param> > <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name> > <param-value> > com.sun.facelets.FaceletViewHandler, > de.ahoehma.jsf.ReverseProxyViewHandler > </param-value> > </context-param> -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (RF-7604) a4j:actionparam doesn't support comma in value

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-7604?page=com.atlassian.jira.plugin... ] Nick Belaevski updated RF-7604: ------------------------------- Fix Version/s: 3.3.2.CR1 Affects Version/s: 3.3.2.CR1 > a4j:actionparam doesn't support comma in value > ---------------------------------------------- > > Key: RF-7604 > URL: https://jira.jboss.org/jira/browse/RF-7604 > Project: RichFaces > Issue Type: Bug > Components: component-a4j-core > Affects Versions: 3.3.2.CR1 > Environment: richfaces-ui-3.2.1.GA > Tomcat 6.0.16 > Facelets 1.1.14 > Reporter: Stephen Kinser > Assignee: Nick Belaevski > Priority: Minor > Fix For: 3.3.2.CR1 > > > I attempt to define a value that contains a comma, as follows: > <a4j:actionparam name="metricName" value="Host:type=Processors,name=CPU.UserMode" assignTo="#{GraphPageBean.metricName}"/> > Here's the method that I expect to be passed Host:type=Processors,name=CPU.UserMode: > public void setMetricName(String metricName) { > this.metricName = metricName; > } > setMetricName is called with a metricName value of "Host:type=Processors". I modified the value to use a '|' instead of a ',' and I got the full value of Host:type=Processors|name=CPU.UserMode. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Created: (RF-7543) inputNumberSlider: "label" attribute doesn't work

by Inna Shchibrya (JIRA)

inputNumberSlider: "label" attribute doesn't work ------------------------------------------------- Key: RF-7543 URL: https://jira.jboss.org/jira/browse/RF-7543 Project: RichFaces Issue Type: Bug Components: component-input Affects Versions: 3.3.2.CR1 Environment: All browsers jsp Reporter: Inna Shchibrya Assignee: Nick Belaevski Priority: Minor For rich: inputNumberSlider "label" attribute doesn't work and absent in page 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

16 years, 8 months

2
1
0 / 0

[JBoss JIRA] Updated: (RF-7605) Not working ajax request with installed ad muncher

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-7605?page=com.atlassian.jira.plugin... ] Nick Belaevski updated RF-7605: ------------------------------- Component/s: component-a4j-core Fix Version/s: Future Assignee: Nick Belaevski > Not working ajax request with installed ad muncher > -------------------------------------------------- > > Key: RF-7605 > URL: https://jira.jboss.org/jira/browse/RF-7605 > Project: RichFaces > Issue Type: Bug > Components: component-a4j-core > Affects Versions: 3.3.2.CR1 > Environment: windows xp, ie8 b2, ie7 > Reporter: Marcin Jaskulski > Assignee: Nick Belaevski > Fix For: Future > > > If I have ad muncher ad blocker installed and no ajax request works when I use internet explorer (it seems that on Firefox works fine). > This is log from a4j:log component: > debug[16:54:31,393]: Have Event [object Object] with properties: target: [object HTMLInputElement], srcElement: undefined, type: click > debug[16:54:31,394]: NEW AJAX REQUEST !!! with form :navigationPanelForm debug[16:54:31,396]: Form have onsubmit function, call it > debug[16:54:31,410]: Append hidden control navigationPanelForm with value [navigationPanelForm] and value attribute [navigationPanelForm] > debug[16:54:31,411]: Append hidden control javax.faces.ViewState with value [j_id5] and value attribute [j_id5] > debug[16:54:31,412]: parameter conversationId with value 15192 > debug[16:54:31,413]: parameter conversationPropagation with value join > debug[16:54:31,414]: parameter navigationPanelForm:showAnswerFocused with value navigationPanelForm:showAnswerFocused > Next step shoud be "Start XmlHttpRequest". It seems like ajax request doesn't even start. > You can check this issue on richfaces demo page. -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Updated: (RF-7603) a4j:form data="#{}" does not populate javascript data variable (data is undefined)

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-7603?page=com.atlassian.jira.plugin... ] Nick Belaevski updated RF-7603: ------------------------------- Component/s: component-a4j-core Fix Version/s: Future Assignee: Nick Belaevski > a4j:form data="#{}" does not populate javascript data variable (data is undefined) > ---------------------------------------------------------------------------------- > > Key: RF-7603 > URL: https://jira.jboss.org/jira/browse/RF-7603 > Project: RichFaces > Issue Type: Patch > Components: component-a4j-core > Affects Versions: 3.3.2.CR1 > Environment: Gentoo Linux 2.6.24 > Sun Java 1.6.0.0.7 > RichFaces 3.2.1_GA > Facelets 1.1.14 > Apache Tomcat 6.0 AppServer > JSF 1.2 RI > Reporter: Lincoln Baxter III > Assignee: Nick Belaevski > Fix For: Future > > Attachments: UIAjaxForm.java > > Time Spent: 3 hours > Remaining Estimate: 0 minutes > > When using the a4j:form component, the data="#{managedBean.property}" attribute is not correctly causing the javascript data variable to be populated. > See example below. data is always undefined, even if the managed bean property is set to a valid value, the alert box shows undefined. > I verified that when using a4j:commandButton, the data variable is correctly populated, and the alert box displays the value. > <a4j:form id="themouth" data="#{indexBean.ajaxInputOk}" > reRender="whispers,earInput,earErrors" > oncomplete="alert(data)" ajaxSubmit="true"> > <div class="centered paddingLarge"><h:outputText > id="whispers" styleClass="smallText" value="#{indexBean.whispers}" /></div> > <div class="centered" id="earWhisper"><a4j:outputPanel id="earErrors"> > <h:message showSummary="true" showDetail="false" for="earInput" > style="color: red;" /> > </a4j:outputPanel><br /> > <h:inputText id="earInput" autocomplete="off" > value="#{indexBean.input}" > validator="#{indexBean.validateWhisper}" required="true"> > </h:inputText> <h:commandButton id="whisperButton" > action="#{indexBean.doWhisper}" value="whisper" /></div> > </a4j:form> -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Moved: (RF-7607) web.xml context-param org.ajax4jsf.VIEW_HANDLERS should allow newlines

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-7607?page=com.atlassian.jira.plugin... ] Nick Belaevski moved AJSF-146 to RF-7607: ----------------------------------------- Project: RichFaces (was: Ajax4jsf) Key: RF-7607 (was: AJSF-146) > web.xml context-param org.ajax4jsf.VIEW_HANDLERS should allow newlines > ---------------------------------------------------------------------- > > Key: RF-7607 > URL: https://jira.jboss.org/jira/browse/RF-7607 > Project: RichFaces > Issue Type: Feature Request > Environment: java 1.5 > myfaces 1.2.3 > rf 3.2.1.CR8 > facelets 1.1.14 > Reporter: Andreas Höhmann > > if i need multiple viewhandlers (faclets) the context-param org.ajax4jsf.VIEW_HANDLERS is the right place ... but ... there is limitation ... all defined viewhandlers must places in ONE line (no linebreaks). > current version: > <context-param> > <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name> > <param-value> > com.sun.facelets.FaceletViewHandler,de.ahoehma.jsf.ReverseProxyViewHandler > </param-value> > </context-param> > preferred version: > <context-param> > <param-name>org.ajax4jsf.VIEW_HANDLERS</param-name> > <param-value> > com.sun.facelets.FaceletViewHandler, > de.ahoehma.jsf.ReverseProxyViewHandler > </param-value> > </context-param> -- 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

16 years, 8 months

1
0
0 / 0

[JBoss JIRA] Moved: (RF-7606) SelectUtils.getConvertedUISelectManyValue more restrictive than it needs to be

by Nick Belaevski (JIRA)

[ https://jira.jboss.org/jira/browse/RF-7606?page=com.atlassian.jira.plugin... ] Nick Belaevski moved AJSF-143 to RF-7606: ----------------------------------------- Project: RichFaces (was: Ajax4jsf) Key: RF-7606 (was: AJSF-143) Issue Type: Feature Request (was: Quality Risk) > SelectUtils.getConvertedUISelectManyValue more restrictive than it needs to be > ------------------------------------------------------------------------------ > > Key: RF-7606 > URL: https://jira.jboss.org/jira/browse/RF-7606 > Project: RichFaces > Issue Type: Feature Request > Environment: JBoss 4.2.2.GA, RichFaces 3.2.1.GA, windows xp sp2 x86 > Reporter: Andr? Fernandes > Priority: Minor > > on line 189 of the org.ajax4jsf.util.SelectUtils we see > if (List.class.isAssignableFrom(valueType)) > .... > But I think it don't need to be List. > It should be Collection because it is less restrictive and works just fine. :) > I found this when I was using an Entity with a Collection<AClass> and a > <rich:pickList ...> > <s:selectItems ...></s:selectItems> > </rich:pickList> > on the view. > When I was posting back to the server, it was throwing an exception (think it is IllegalArgumentException). > Then I get the source for RichFaces and find out that the SelectUtils.getConvertedUISelectManyValue was not expecting a Collection, but instead it was expecting a List. > Then I change my entity to have a List<AClass> and it works just fine. > If the line 189 just change to if (Collection.class.isAssignableFrom(valueType)) it should work. -- 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

16 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues July 2009