November 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13280) RF 5 packed resources cause conflict in RF 4.5

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13280?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13280. ------------------------------ Verified > RF 5 packed resources cause conflict in RF 4.5 > ---------------------------------------------- > > Key: RF-13280 > URL: https://issues.jboss.org/browse/RF-13280 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.5.0.Alpha1 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > > Showcase uses resource from RF 5 core instead of using the proper ones from RF 4.5 components. (e.g. packed.js) > The solution is to split core and ui resources in RF 5. RF 4.5 will only generate ui resources and use core resources from RF 5. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13229) Inspect RF 4.5 Java classes for occurences of 'import org.richfaces.ui'

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13229?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13229. ------------------------------ Verified > Inspect RF 4.5 Java classes for occurences of 'import org.richfaces.ui' > ----------------------------------------------------------------------- > > Key: RF-13229 > URL: https://issues.jboss.org/browse/RF-13229 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.5.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1 > > -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13224) RF 4.5 build fails to render optimized resources

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13224?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13224. ------------------------------ Verified > RF 4.5 build fails to render optimized resources > ------------------------------------------------ > > Key: RF-13224 > URL: https://issues.jboss.org/browse/RF-13224 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.5.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Michal Petrov > Fix For: 4.5.0.Alpha1 > > > -I believe it's caused by:- > https://github.com/richfaces/richfaces/commit/46b03d226ae420bcbc8abd7f79e... > This is no longer an issue. > Current issues: > * packed.js is not generated, .js files do not seem to be handled by the plugin at all > * some images are not rendered, e.g. gradientA.png (used in several components for background), it is not defined in resource-mappings.properties -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13225) RF5 build fails to render optimized resources

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13225?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13225. ------------------------------ Verified > RF5 build fails to render optimized resources > --------------------------------------------- > > Key: RF-13225 > URL: https://issues.jboss.org/browse/RF-13225 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 5.0.0.Alpha2 > Reporter: Michal Petrov > Assignee: Michal Petrov > Fix For: 5.0.0.Alpha2 > > Original Estimate: 2 days > Remaining Estimate: 2 days > > The improvements for 4.5.x along with resource handling improvements introduced several issues: > * framework/pom.xml resource optimization > {code} > <execution> > <id>static-resources</id> > <phase>process-classes</phase> > <goals> > <goal>java</goal> > </goals> > <configuration> > <arguments> > <argument>--classpathDir</argument> > <argument>${project.build.outputDirectory}</argument> > <argument>--output</argument> > <argument>${optimized.resources.directory}/Static/</argument> > <argument>--prefix</argument> > <argument>${optimized.resources.prefix}/Static/</argument> > <argument>--mapping</argument > <argument>${optimized.resources.mapping}/Static.properties</argument> > <argument>--skins</argument> > <argument>${optimized.resources.skins}</argument> > <argument>--excludeFile</argument> > <argument>^javax.faces</argument> > <argument>excludeFile</argument> > <argument>^org.richfaces.ui.images.*</argument> > {code} > {panel} > the exclusion exists for classes like {{org/richfaces/ui/images/BaseGradient.java}} which end up being rendered as images, with the change to image resources in RF5 this exclusion causes the resource handling to fail > {panel} > * CSS rendering from *.ecss > {code} > #{richSkin.imageUrl('inputBackgroundImage.png')} > {code} > {panel} > the imageUrl method doesn't return the proper path, e.g. > {{../org.richfaces.ui.images/gradientA.png}} (proper) > instead of > {{%skin%/org.richfaces.ui.images/gradientA.png}} (current) > {panel} -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13392) TreeSelectionChangeEvent always triggered during Apply Request Phase

by Andreas Hahne (JIRA)

Andreas Hahne created RF-13392: ---------------------------------- Summary: TreeSelectionChangeEvent always triggered during Apply Request Phase Key: RF-13392 URL: https://issues.jboss.org/browse/RF-13392 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-tree Affects Versions: 4.3.3 Reporter: Andreas Hahne When selecting a {{rich:treeNode}}, the corresponding {{selectionChangeListener}} is triggered during Apply Request Phase, no matter if the immediate attribute is set to true or false. This leads to a weird behaviour in our application where an output panel is filled with the data selected in the tree. Both components are located in the same {{h:form}} element (in contrast to the showcase on the RF homepage). While the value of the {{h:outputText}} component is updated correctly, the one in the {{h:inputText}} is not because it is overwritten by the old value during Update Model Phase. If the change was processed during Invoke Application Phase this would not occur most likely. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13186) Showcase 4.5.x fails

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13186?page=com.atlassian.jira.plugin.s... ] Matej Novotny commented on RF-13186: ------------------------------------ Thanks for quick response and link. I resumed verifying and came across one more thing. It only occurs when _resource optimization_ is set to _False_ and I was also using a different _project stage_ to avoid the above mentioned JSF bug. {code} <context-param> <param-name>javax.faces.PROJECT_STAGE</param-name> <param-value>Production</param-value> </context-param> {code} Using these settings go to [inputs->inputNumberSlider|http://localhost:8080/showcase/richfaces/component-sample.jsf?demo=inputNumberSlider&skin=blueSky] and try to interact with the component. There is no response and in a web console is a JS type error (with a //TODO note attached to that line of code). {code} Uncaught TypeError: Object [object Object] has no method 'setPosition' inputNumberSlider.js;jsessionid=YuqiPJsXtBxYRSB91vgCso2m.undefined:145 {code} The error refers to [this|https://github.com/richfaces4/components/blob/4.5.x/rich/src/main/re...] line on GitHub. Otherwise I found no problems/errors/warnings. > Showcase 4.5.x fails > -------------------- > > Key: RF-13186 > URL: https://issues.jboss.org/browse/RF-13186 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Michal Petrov > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1 > > > [https://github.com/michpetrov/richfaces/tree/showcase-4.5.x/examples/show...] - showcase 4.5 > [https://github.com/richfaces4/components/tree/4.5.x] - 4.5.x components > [https://github.com/richfaces4/dev-examples/tree/4.5.x] - 4.5 dev-examples > Builds and deploys fine. > Examples that do not work: > * -several examples (e.g. actionListener) produce "The form component needs to have a UIForm in its ancestry. Suggestion: enclose the necessary components within <h:form>"- > * validation - fails because rf.rf4.ui.Message is not defined, the resource is not being included due to resource optimization > * trees/rich:tree - missing …/javax.faces.resource/node_icon.gif.jsf?ln=org.richfaces > * menus/rich:contextMenu and rich:dropDownMenu - not working, probably for the same reason as validators (missing proper javascript resource) > * inputs/rich:inplaceInput - ditto > * selects/rich:inplaceSelect - ditto > * output/rich:tooltip - ditto > When resource optimization some components (dataTables) are missing background image causing a badly generated CSS. {{background-image: url()}} > h5. resource optimization turned off > h6. Issue with Validator > - org.richfaces.validator.FacesObjectDescriptor.getMessage() > - collision between RF4.5 and RF5 > the interface is the same in both versions but the Message class is in different packages in the two > h6. Issue with menus > - org.richfaces.renderkit.html.MenuItemRendererBase.getUtils() > - probably the same problem -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13389) Showcase for RF 5, pick list rendering in firefox

by Matej Novotny (JIRA)

[ https://issues.jboss.org/browse/RF-13389?page=com.atlassian.jira.plugin.s... ] Matej Novotny closed RF-13389. ------------------------------ Resolution: Cannot Reproduce Bug Ok, I double checked everything before I reported this but I forgot to clear the cache. It did the trick. Closing as unreproducible and sorry for the bother.. > Showcase for RF 5, pick list rendering in firefox > ------------------------------------------------- > > Key: RF-13389 > URL: https://issues.jboss.org/browse/RF-13389 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-selects > Affects Versions: 5.0.0.Alpha2 > Environment: JBoss AS 7.1 > Firefox version 25.0 > Chrome version 31 > Reporter: Matej Novotny > Assignee: Matej Novotny > Fix For: 5.0.0.Alpha2 > > Attachments: Chrome_screenshot.png, Firefox_screenshot.png > > > When using Firefox (in my case version 25) and accessing a pick list page in showcase(selects->r:pickList), the simple pick list does not render correctly (see attached screenshot). However pick list with columns cause no problems. > I tested it with Chrome where everything works correctly. > Also to make sure I rebuilded whole repository with dependencies not to have any outdated artifacts. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13251: ---------------------------- Labels: waiting_on_user (was: ) > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Lukáš Fryč > Priority: Minor > Labels: waiting_on_user > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13251: --------------------------------- Immo, could you please clarify in what aspects is your usage different or provide some sample of usage? I know you use FocusManager and you would probably do something like {{focusManager.focus("autocomplete")}} but that should at the end work very similar to my sample above. > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Lukáš Fryč > Priority: Minor > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13251) FocusManager to support complex components like rich:autocomplete

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13251?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13251: --------------------------------- Focus (and FocusManager) works with any [tabbable|http://api.jqueryui.com/tabbable-selector/] input including autocomplete. I have checked on a modified sample in richfaces-showcase using focus-preserving approach: {code} <h:form> <rich:focus preserve="true" /> <rich:autocomplete id="autocomplete" mode="cachedAjax" minChars="2" autocompleteMethod="#{autocompleteBean.autocomplete}" /> <a4j:commandButton render="autocomplete" /> </h:form> {code} When you hit commandButton, the autocomplete is re-rendered and rich:focus then brings focus back to the component thas was focused before the request (autocomplete). > FocusManager to support complex components like rich:autocomplete > ----------------------------------------------------------------- > > Key: RF-13251 > URL: https://issues.jboss.org/browse/RF-13251 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.4 > Reporter: Immo Benjes > Assignee: Lukáš Fryč > Priority: Minor > > Currently the FocusManager in Richfaces only works on 'simple' UI components like h:inputText or h:selectOneMenu but not on more complex components like rich:autocomplete. > It would be good if FocusManager could support complex components or 'real' Ids as generated for that page. > The use case for the support on autocomplete is like this: > User has to enter multiple 'entities'. A rich:autocomplete is used to select the entity and add it to a list. After each ajax submit the focus gets lost and the user has to manually set the focus back to the autocomplete input field. -- 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, 5 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues November 2013