October 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-13275) Replace #{toScriptArgs(options)} with #{options.toJson()}

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-13275: ------------------------------- Summary: Replace #{toScriptArgs(options)} with #{options.toJson()} Key: RF-13275 URL: https://issues.jboss.org/browse/RF-13275 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Components: cdk, core Affects Versions: 4.5.0.Alpha1, 5.0.0.Alpha2 Reporter: Lukáš Fryč We should rewrite <cdk:scriptObject> to generate Map which exposes {{#toJson()}} function, that works as {{ScriptUtils.toScript}}. This will overcome defficiencies of {{#{toScriptArgs(options)}}} mentioned in RF-12593. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13275) Replace #{toScriptArgs(options)} with #{options.toJson()}

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13275?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-13275: ---------------------------- Description: We should rewrite <cdk:scriptObject> to generate Map which exposes {{#toJson()}} function, that works as {{ScriptUtils.toScript}}. This will overcome defficiencies of {{#{toScriptArgs(options)}} mentioned in RF-12593. was: We should rewrite <cdk:scriptObject> to generate Map which exposes {{#toJson()}} function, that works as {{ScriptUtils.toScript}}. This will overcome defficiencies of {{#{toScriptArgs(options)}}} mentioned in RF-12593. > Replace #{toScriptArgs(options)} with #{options.toJson()} > ---------------------------------------------------------- > > Key: RF-13275 > URL: https://issues.jboss.org/browse/RF-13275 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: cdk, core > Affects Versions: 4.5.0.Alpha1, 5.0.0.Alpha2 > Reporter: Lukáš Fryč > > We should rewrite <cdk:scriptObject> to generate Map which exposes > {{#toJson()}} function, that works as {{ScriptUtils.toScript}}. > This will overcome defficiencies of {{#{toScriptArgs(options)}} mentioned in RF-12593. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13250) Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-13250?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak commented on RF-13250: ------------------------------------ Hi Milo, I appreciate your effort but I'm still not able to reproduce this issue. It would be helpful if you could provide me short, self contained, correct, example (see [1]) together with description of environment where to run it. Thanks. [1] https://community.jboss.org/wiki/SubmittingEffectiveIssueReports > Extreme memory usage in RF4.3.4.Final and not in RF4.3.3.Final > -------------------------------------------------------------- > > Key: RF-13250 > URL: https://issues.jboss.org/browse/RF-13250 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.4 > Environment: Gentoo Linux, Tomcat 7.0.39, MyFaces 2.1.12, Tomahawk 1.1.14, RichFaces 4.3.4, APR 1.4.5 > Reporter: Milo van der Zee > Assignee: Pavol Pitonak > Labels: memoryleak > > Hello, > I did an upgrade from RF 4.3.3.Final to 4.3.4.Final and the application started to crash with 'Out Off Memory' errors. I changed the POM back to 4.3.3.Final and the problem is gone. > I also started seeing this message lot's of times: > {{WARN org.atmosphere.cpr.AtmosphereResponse - Committed error code 400}} > I don't know if that has anything to do with the error. I set {{org.atmosphere.cpr.sessionSupport}} to {{true}} and I did not see the message again. But still the application went out-of-memory. > In the crashed system heap dump I see a lot of: > - AtomicBoolean (751.000, 15.0MB) > - ConcurrentLinkedQueue > - AtmospereRequest$Builder (60.042, 13.8MB) > To me it looks like it has something to do with Atmosphere. Any ideas? > Thanks, > Milo van der Zee -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13274) Use QSTools:archetypeSync to keep the kitchensink archetype synchronized with the kithensink-rf quickstart

by Brian Leathem (JIRA)

Brian Leathem created RF-13274: ---------------------------------- Summary: Use QSTools:archetypeSync to keep the kitchensink archetype synchronized with the kithensink-rf quickstart Key: RF-13274 URL: https://issues.jboss.org/browse/RF-13274 Project: RichFaces Issue Type: Enhancement Security Level: Public (Everyone can see) Reporter: Brian Leathem Fix For: 4.3.5 As per [~rafabene]'s description in IRC: {quote} use QSTools:archetypeSync to keep your Archetype Synchornized with the kithensink-rf Quickstart as we did for our Archetypes look at an example here: https://github.com/jboss-developer/jboss-eap-archetypes/blob/master/jboss... you tell where the quickstart is projectGitRepo projectPath tell what's your branch or commit or tag them what's your rootPackage you can configure expression that will be replaced by $\{artifactId} with archetypeExpressionReplaceValues so every fix that you make on Quickstarts will be available on your next Archetype build call me if you have any issues with QSTools:archetypeSync {quote} -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13148) RichFaces project from archetype can not be built without JBoss repositories

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13148?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13148: ------------------------------------ Another solution is to put jsf-test in maven central. Not ideal IMO as we are moving away from jsf-test. OTOH we are not moving away from it that quickly. > RichFaces project from archetype can not be built without JBoss repositories > ---------------------------------------------------------------------------- > > Key: RF-13148 > URL: https://issues.jboss.org/browse/RF-13148 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype, build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Priority: Blocker > Labels: regression > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Projects created from RichFaces archetypes can not be built without JBoss repositories (using just Maven Central). > The reason is that they depend on {{org.jboss.test-jsf:jsf-test:pom:1.1.6}} which is deployed only to JBoss repos. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13148) RichFaces project from archetype can not be built without JBoss repositories

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-13148?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-13148: --------------------------------- You are right, Juraj, in RF4, we use scope=test, but here we import the BOM. It seems for dependency management, it needs to be resolved even though it manages just test dependencies. The solution is removing BOM (which we introduced to allow managing dependencies properly) and use specific versions jsf-test instead. > RichFaces project from archetype can not be built without JBoss repositories > ---------------------------------------------------------------------------- > > Key: RF-13148 > URL: https://issues.jboss.org/browse/RF-13148 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype, build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Priority: Blocker > Labels: regression > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Projects created from RichFaces archetypes can not be built without JBoss repositories (using just Maven Central). > The reason is that they depend on {{org.jboss.test-jsf:jsf-test:pom:1.1.6}} which is deployed only to JBoss repos. -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12936) Use jQuery in non-conflicting way

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12936?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12936: ------------------------------- Description: The {{richfaces.js}} references both, {{jQuery}} from closure and global {{$}} - this issue is addressed in RF-12833. However jQuery should not be used directly, rather from closures - prefered way is to use {{$}} but its naming now conflicts with {{RichFaces.$}} for component references. I suggest to use following trick: {code:title=richfaces.js} window.RichFaces = window.RichFaces || {}; RichFaces.jQuery = RichFaces.jQuery || window.jQuery; //encapsulation (function($, rf) { // free to use $ here }(RichFaces.jQuery, RichFaces)); {code} It will allow: * provide own jQuery for RichFaces (using _jQuery.noConflict()_) * use libraries which make use of {{$}} (prototype, other jQuery versions) in no-conflicting way was: The {{richfaces.js}} references both, {{jQuery}} from closure and global {{$}} - this issue is addressed in RF-12833. However jQuery should not be used directly, rather from closures - prefered way is to use {{$}} but its naming now conflicts with {{RichFaces.$}} for component references. I suggest to use following trick: {code:title=richfaces.js} window.RichFaces = window.RichFaces || {}; RichFaces.jQuery = RichFaces.jQuery || window.jQuery; //encapsulation (function($, rf) { // free to use $ here }(RichFaces.jQuery, RichFaces)); {code} It will allow: * provide own jQuery for RichFaces * use libraries which make use of {{$}} (prototype, other jQuery versions) in no-conflicting way > Use jQuery in non-conflicting way > --------------------------------- > > Key: RF-12936 > URL: https://issues.jboss.org/browse/RF-12936 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 4.3.1 > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Fix For: 4.5.0.Alpha1, 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > The {{richfaces.js}} references both, {{jQuery}} from closure and global {{$}} - this issue is addressed in RF-12833. > However jQuery should not be used directly, rather from closures - prefered way is to use {{$}} but its naming now conflicts with {{RichFaces.$}} for component references. > I suggest to use following trick: > {code:title=richfaces.js} > window.RichFaces = window.RichFaces || {}; > RichFaces.jQuery = RichFaces.jQuery || window.jQuery; > //encapsulation > (function($, rf) { > // free to use $ here > }(RichFaces.jQuery, RichFaces)); > {code} > It will allow: > * provide own jQuery for RichFaces (using _jQuery.noConflict()_) > * use libraries which make use of {{$}} (prototype, other jQuery versions) in no-conflicting way -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13259) DataTable rowClasses with columnGroup is not rendered

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13259?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13259: ------------------------------- Fix Version/s: 5-Tracking > DataTable rowClasses with columnGroup is not rendered > ----------------------------------------------------- > > Key: RF-13259 > URL: https://issues.jboss.org/browse/RF-13259 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.3.0.Final, 5.0.0.Alpha1 > Environment: java 6, java 7, > all browsers > JBoss AS 7.1.1.Final > Reporter: Luca Stancapiano > Fix For: 5-Tracking > > > This is my page: > {code} > <rich:dataTable id="postsList" value="#{topic.threadsDataModel}" rowClasses="oddRow,noStyle"> > <rich:columnGroup> > <rich:column styleClass="forumpostleftcolumn">...</rich:column> > <rich:column>...</rich:column> > <rich:columnGroup> > <rich:columnGroup> > <rich:column styleClass="forumpostleftcolumn">...</rich:column> > <rich:column">...</rich:column> > <rich:columnGroup> > </rich:dataTable> > {code} > I expect that the styes oddRow and noStyle are rendered inside the rows but nothing happens. Seems that rowClasses attribute cannot be used with rich:columnGroup. > -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13259) DataTable rowClasses with columnGroup is not rendered

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13259?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13259: ------------------------------- Labels: testcase_provided (was: ) > DataTable rowClasses with columnGroup is not rendered > ----------------------------------------------------- > > Key: RF-13259 > URL: https://issues.jboss.org/browse/RF-13259 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component > Affects Versions: 4.3.0.Final, 5.0.0.Alpha1 > Environment: java 6, java 7, > all browsers > JBoss AS 7.1.1.Final > Reporter: Luca Stancapiano > Labels: testcase_provided > Fix For: 5-Tracking > > > This is my page: > {code} > <rich:dataTable id="postsList" value="#{topic.threadsDataModel}" rowClasses="oddRow,noStyle"> > <rich:columnGroup> > <rich:column styleClass="forumpostleftcolumn">...</rich:column> > <rich:column>...</rich:column> > <rich:columnGroup> > <rich:columnGroup> > <rich:column styleClass="forumpostleftcolumn">...</rich:column> > <rich:column">...</rich:column> > <rich:columnGroup> > </rich:dataTable> > {code} > I expect that the styes oddRow and noStyle are rendered inside the rows but nothing happens. Seems that rowClasses attribute cannot be used with rich:columnGroup. > -- 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-13148) RichFaces project from archetype can not be built without JBoss repositories

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13148?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-13148: ------------------------------------ Indeed, the jsf-test dependincies in RF 4 appear to have been: * jsf-test-stage * jsf-test-jetty * jsf-test-scriptunit https://github.com/richfaces4/build/blob/master/parent/pom.xml#L453 [~lfryc] what was the reson for introducing the _jsf-test _ dependency in RichFaces 5? Or am I just reading the poms wrong... > RichFaces project from archetype can not be built without JBoss repositories > ---------------------------------------------------------------------------- > > Key: RF-13148 > URL: https://issues.jboss.org/browse/RF-13148 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: archetype, build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Priority: Blocker > Labels: regression > Fix For: 5.0.0.Alpha2 > > Original Estimate: 1 hour > Remaining Estimate: 1 hour > > Projects created from RichFaces archetypes can not be built without JBoss repositories (using just Maven Central). > The reason is that they depend on {{org.jboss.test-jsf:jsf-test:pom:1.1.6}} which is deployed only to JBoss repos. -- 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

12 years, 5 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 October 2013