May 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12961) Update the docs reflecting changes in RichFaces 5.0.0.Alpha1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12961?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12961: ------------------------------- Sprint: 5.0.0.Alpha1 Sprint 3 > Update the docs reflecting changes in RichFaces 5.0.0.Alpha1 > ------------------------------------------------------------ > > Key: RF-12961 > URL: https://issues.jboss.org/browse/RF-12961 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 5.0.0.Alpha1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha1 > > Original Estimate: 6 hours > Remaining Estimate: 6 hours > -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12918) Switch to using the asciidoctor plugin for asciidoc processing

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12918?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12918: ------------------------------------ The two issue mentioned in the description have been resolved, but two new issues are preventing us from using the released version of asciidoctor: # https://github.com/asciidoctor/asciidoctor/issues/172 # https://github.com/asciidoctor/asciidoctor/issues/173 We are currently using a fork of asciidoctor to generate the docbook xml, as described in: https://github.com/richfaces/docs/blob/master/contributing.asciidoc > Switch to using the asciidoctor plugin for asciidoc processing > -------------------------------------------------------------- > > Key: RF-12918 > URL: https://issues.jboss.org/browse/RF-12918 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: doc > Affects Versions: 5.0.0.Alpha1 > Reporter: Brian Leathem > Assignee: Brian Leathem > Fix For: 5-Tracking > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > It is currently not possible to generate the RichFaces docbook xml from the asciidoc source using asciidoctor. Two bugs hold us back from switching to asciidoctor: > # https://github.com/asciidoctor/asciidoctor/issues/116 > # https://github.com/asciidoctor/asciidoctor/issues/222 > When these asciidoctor issues have been resolved, we can switch the richfaces docs project to generate the xml using the asciidoctor maven plugin. > Until then, the asciidoc is processed using the asciidoc command line as described in: > https://github.com/richfaces/docs/blob/master/conversion/src/main/bash/as... -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12960) archetypes are not available for RichFaces 5

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12960?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12960: ------------------------------------ >From where are you expecting them to be available? > archetypes are not available for RichFaces 5 > -------------------------------------------- > > Key: RF-12960 > URL: https://issues.jboss.org/browse/RF-12960 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Reporter: Jan Papousek > Labels: archetype > -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12908) Distribution ZIP doesn't contain any examples

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12908?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12908: ---------------------------------- Assignee: Brian Leathem > Distribution ZIP doesn't contain any examples > --------------------------------------------- > > Key: RF-12908 > URL: https://issues.jboss.org/browse/RF-12908 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build/distribution > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Brian Leathem > Fix For: 5.0.0.Alpha1 > > Original Estimate: 30 minutes > Remaining Estimate: 30 minutes > > There is just empty {{examples}} folder in the distribution ZIP. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12951) XML validation errors for CDK renderer templates

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12951?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12951: ------------------------------- Fix Version/s: 5-Tracking > XML validation errors for CDK renderer templates > ------------------------------------------------ > > Key: RF-12951 > URL: https://issues.jboss.org/browse/RF-12951 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: cdk, clean-up > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Fix For: 5-Tracking > > > *.template.xml files has lot of validation errors, but most of them fit in the following categories. > With addressing the CDK XML schema changes for these errors, we could achieve less warnings in the IDE. > * cdk:scriptObject > * cdk:import > * div's content ( > * tabindex = -1 > * cdk:passThroughWithExclusions="id,value,styleClass,class" -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12950) Move Showcase tests to the examples/showcase module and mark some of them as smoke tests

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12950?page=com.atlassian.jira.plugin.s... ] Brian Leathem commented on RF-12950: ------------------------------------ Where are the tests now? ie. you say move them to the showcase module, where are they coming from? > Move Showcase tests to the examples/showcase module and mark some of them as smoke tests > ---------------------------------------------------------------------------------------- > > Key: RF-12950 > URL: https://issues.jboss.org/browse/RF-12950 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: tests - functional > Reporter: Lukáš Fryč > > Smoke tests should verify that basic showcase functionality works as expected. > Full showcase test suite can be moved into RF5 repository then. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12949) Create a set of Photoalbum smoke tests which will verify it starts and that the basic features works

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12949?page=com.atlassian.jira.plugin.s... ] Brian Leathem reassigned RF-12949: ---------------------------------- Assignee: Pavol Pitonak Can you allocate some time to create these tests? > Create a set of Photoalbum smoke tests which will verify it starts and that the basic features works > ---------------------------------------------------------------------------------------------------- > > Key: RF-12949 > URL: https://issues.jboss.org/browse/RF-12949 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Reporter: Lukáš Fryč > Assignee: Pavol Pitonak > > The Photoalbum example should have a test which will make sure it starts correctly and basic functionality works as expected. -- 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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12947) Tree: Could not serialize state: org.richfaces.model.SwingTreeNodeDataModelImpl with MyFaces

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12947?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12947: ------------------------------- Fix Version/s: 5-Tracking > Tree: Could not serialize state: org.richfaces.model.SwingTreeNodeDataModelImpl with MyFaces > -------------------------------------------------------------------------------------------- > > Key: RF-12947 > URL: https://issues.jboss.org/browse/RF-12947 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.3.1, 4.3.2 > Reporter: Pavol Pitonak > Labels: myfaces > Fix For: 5-Tracking > > > # git clone git://github.com/richfaces/qa.git > # git checkout 4.3.x > # mvn clean verify -P tomee-remote-1-5 -Dtest=TestRowKeyConverter -Dmethod=testToggle > result: > * one of three tests fail on TomEE (MyFaces) with this error: > {quote} > Apr 26, 2013 1:34:03 PM org.apache.myfaces.application.viewstate.ServerSideStateCacheImpl serializeView > SEVERE: Exiting serializeView - Could not serialize state: org.richfaces.model.SwingTreeNodeDataModelImpl > java.io.NotSerializableException: org.richfaces.model.SwingTreeNodeDataModelImpl > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1180) > at java.io.ObjectOutputStream.defaultWriteFields(ObjectOutputStream.java:1528) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1493) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) > at java.util.HashMap.writeObject(HashMap.java:1014) > at sun.reflect.GeneratedMethodAccessor173.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:975) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1480) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1362) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1170) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) > at java.util.HashMap.writeObject(HashMap.java:1014) > at sun.reflect.GeneratedMethodAccessor173.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:601) > at java.io.ObjectStreamClass.invokeWriteObject(ObjectStreamClass.java:975) > at java.io.ObjectOutputStream.writeSerialData(ObjectOutputStream.java:1480) > at java.io.ObjectOutputStream.writeOrdinaryObject(ObjectOutputStream.java:1416) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1174) > at java.io.ObjectOutputStream.writeArray(ObjectOutputStream.java:1362) > at java.io.ObjectOutputStream.writeObject0(ObjectOutputStream.java:1170) > at java.io.ObjectOutputStream.writeObject(ObjectOutputStream.java:346) > at org.apache.myfaces.application.viewstate.ServerSideStateCacheImpl.serializeView(ServerSideStateCacheImpl.java:411) > at org.apache.myfaces.application.viewstate.ServerSideStateCacheImpl.saveSerializedViewInServletSession(ServerSideStateCacheImpl.java:300) > at org.apache.myfaces.application.viewstate.ServerSideStateCacheImpl.saveSerializedView(ServerSideStateCacheImpl.java:578) > at org.apache.myfaces.renderkit.html.HtmlResponseStateManager.saveState(HtmlResponseStateManager.java:146) > at org.apache.myfaces.application.StateManagerImpl.saveView(StateManagerImpl.java:194) > at org.apache.myfaces.view.facelets.FaceletViewDeclarationLanguage.renderView(FaceletViewDeclarationLanguage.java:2052) > at org.apache.myfaces.application.ViewHandlerImpl.renderView(ViewHandlerImpl.java:285) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:59) > at javax.faces.application.ViewHandlerWrapper.renderView(ViewHandlerWrapper.java:59) > at org.apache.myfaces.lifecycle.RenderResponseExecutor.execute(RenderResponseExecutor.java:116) > at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:241) > at javax.faces.webapp.FacesServlet.service(FacesServlet.java:199) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.richfaces.tests.metamer.TestIdentityFilter.doFilter(TestIdentityFilter.java:93) > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243) > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:222) > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:123) > at org.apache.tomee.catalina.OpenEJBValve.invoke(OpenEJBValve.java:45) > at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:472) > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171) > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:99) > at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:936) > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:118) > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:407) > at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1004) > at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:589) > at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:312) > at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110) > at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603) > at java.lang.Thread.run(Thread.java:722) > {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

11 years

1
0
0 / 0

[JBoss JIRA] (RF-12939) Focus: attribute ajaxRendered does not work

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12939?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12939: ------------------------------- Fix Version/s: 5.0.0.Alpha1 > Focus: attribute ajaxRendered does not work > ------------------------------------------- > > Key: RF-12939 > URL: https://issues.jboss.org/browse/RF-12939 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-misc > Affects Versions: 4.3.1, 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Firefox 20, Chrome 26 > Reporter: Pavol Pitonak > Fix For: 5.0.0.Alpha1 > > > # Test ITFocusAjaxRendered.when_there_are_inputs_with_tabindex_then_the_lowest_tabindex_will_obtain_focus() fails. When focus's attribute ajaxRendered is set to false, no input should be focused after ajax request. > # rename the test because it doesn't use tabindex attribute -- 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

11 years

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: ------------------------------- Fix Version/s: 5.0.0.Alpha2 > 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č > Fix For: 5.0.0.Alpha2 > > > 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} > RichFaces.jQuery = RichFaces.jQuery || jQuery; > //encapsulation > (function($, RichFaces) { > // 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 -- 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

11 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues May 2013