October 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13301) Favor use of Page Fragments in Framework Tests

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13301: ------------------------------- Summary: Favor use of Page Fragments in Framework Tests Key: RF-13301 URL: https://issues.jboss.org/browse/RF-13301 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: tests - functional Affects Versions: 5.0.0.Alpha2 Reporter: Lukáš Fryč Since we have introduced Page Fragments in Alpha2, we could favor their usage in fragment tests. We could start to refactor tests for components rewritten in Alpha2 and continue as we rewrite other components. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13300) Page Fragments: refine module dependencies

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13300: ------------------------------- Summary: Page Fragments: refine module dependencies Key: RF-13300 URL: https://issues.jboss.org/browse/RF-13300 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: page-fragments Affects Versions: 5.0.0.Alpha2 Reporter: Lukáš Fryč During the review, I have found out we may need to fine module dependencies: https://github.com/richfaces/richfaces/pull/55#issuecomment-27339441 ---- {code} joda-time:2.3 - DateTime commons-lang:2.6 - Validate.isTrue - StringEscapeUtils.unescapeJava json-simple:1.1.1 - JSONParser org.jodah:typetools:0.3.0 - TypeResolver.resolveRawArguments {code} I'm fine with {{DateTime}}, since it's going to be standardized - even though we may consider making it optional dependency and provide alternative in form of {{java.util.Date}}. I didn't found reason to leave {{Validate.isTrue}} - this should be replaced by more verbose but dependency free code. I did some googling for alternatives to {{StringEscapeUtils.unescapeJava}} and found out few suggestions for dependency free Java-unescaping. {{JSONParser}} seems to be necessary (even though we don;t use it extensively yet), but I would favor standard APIs in form of JSR-353. I believe {{TypeResolver}} can be re-written from scratch, but since it's one-class ASL dependency, we might consider shading it. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13299) Page Fragments: added license headers to all sources

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13299: ------------------------------- Summary: Page Fragments: added license headers to all sources Key: RF-13299 URL: https://issues.jboss.org/browse/RF-13299 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Affects Versions: 5.0.0.Alpha2 Reporter: Lukáš Fryč Issue mentioned during impl review: https://github.com/richfaces/richfaces/pull/55 -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13298) Richfaces BOM manages a non Maven Central dependency

by Rafael Benevides (JIRA)

Rafael Benevides created RF-13298: ------------------------------------- Summary: Richfaces BOM manages a non Maven Central dependency Key: RF-13298 URL: https://issues.jboss.org/browse/RF-13298 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: build/distribution Affects Versions: 4.3.4, 4.3.3, 4.3.2 Reporter: Rafael Benevides Richfaces BOMs http://repo1.maven.org/maven2/org/richfaces/richfaces-bom/4.3.4.Final/ric... manages the following GAV: org.richfaces.ui.common:richfaces-ui-common-api:${version.richfaces} which is not present on Maven Central ( http://search.maven.org/#search%7Cga%7C1%7Crichfaces-ui-common-api ) BOM should have this scope changed or declare a https://repository.jboss.org/nexus repository -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13297) Autocomplete - demo with cachedAjax does not update options after first request

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13297?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13297: ---------------------------- Fix Version/s: 5.0.0.Alpha2 > Autocomplete - demo with cachedAjax does not update options after first request > ------------------------------------------------------------------------------- > > Key: RF-13297 > URL: https://issues.jboss.org/browse/RF-13297 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > > Once the suggestion list is opened for first search request, it's not updated anymore. It's related to caching functionality. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13296) Autocomplete - clientFilterFunction doesn't work in showcase

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13296?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13296: ---------------------------- Fix Version/s: 5.0.0.Alpha2 > Autocomplete - clientFilterFunction doesn't work in showcase > ------------------------------------------------------------ > > Key: RF-13296 > URL: https://issues.jboss.org/browse/RF-13296 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > > The demo does not work at all, I guess the clientFilterfunction functionality is broken. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13285) The new autocomplete component's CSS does not play nicely with the RichFaces showcase

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13285?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-13285. ----------------------------- Resolution: Done > The new autocomplete component's CSS does not play nicely with the RichFaces showcase > ------------------------------------------------------------------------------------- > > Key: RF-13285 > URL: https://issues.jboss.org/browse/RF-13285 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-input > Reporter: Brian Leathem > Assignee: Lukáš Fryč > Fix For: 5.0.0.Alpha2 > > Original Estimate: 20 minutes > Remaining Estimate: 20 minutes > > There are some sizing and visibility issues that need to be addressed, likely by changing the showcase applications's custom CSS (this was done for the picklist component for example). -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13297) Autocomplete - demo with cachedAjax does not update options after first request

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13297: ------------------------------- Summary: Autocomplete - demo with cachedAjax does not update options after first request Key: RF-13297 URL: https://issues.jboss.org/browse/RF-13297 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-input, showcase Affects Versions: 5.0.0.Alpha2 Reporter: Lukáš Fryč Once the suggestion list is opened for first search request, it's not updated anymore. It's related to caching functionality. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13296) Autocomplete - clientFilterFunction doesn't work in showcase

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13296: ------------------------------- Summary: Autocomplete - clientFilterFunction doesn't work in showcase Key: RF-13296 URL: https://issues.jboss.org/browse/RF-13296 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: component-input, showcase Affects Versions: 5.0.0.Alpha2 Reporter: Lukáš Fryč The demo does not work at all, I guess the clientFilterfunction functionality is broken. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (RF-13296) Autocomplete - clientFilterFunction doesn't work in showcase

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13296?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13296: ---------------------------- Issue Type: Bug (was: Feature Request) > Autocomplete - clientFilterFunction doesn't work in showcase > ------------------------------------------------------------ > > Key: RF-13296 > URL: https://issues.jboss.org/browse/RF-13296 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-input, showcase > Affects Versions: 5.0.0.Alpha2 > Reporter: Lukáš Fryč > > The demo does not work at all, I guess the clientFilterfunction functionality is broken. -- 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, 6 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 October 2013