September 2013 - richfaces-issues

[JBoss JIRA] (RF-13199) Framework tests does not include all needed classes to the deployment when deploying on WildFly

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13199?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13199: ------------------------------- Labels: jsf22 (was: ) > Framework tests does not include all needed classes to the deployment when deploying on WildFly > ----------------------------------------------------------------------------------------------- > > Key: RF-13199 > URL: https://issues.jboss.org/browse/RF-13199 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: tests - functional > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.0.Alpha4 > Reporter: Juraj Húska > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > When running framework tests with WildFly 8.0.0.Alpha4, some of the tests fail with: _DeploymentException: Cannot deploy_ exception. > The created wars miss classes like: {{FrameworkDeployment}} and other linkage errors. See for example [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view...] or [this|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/RichFaces/view...] tests results. > The reason is IMHO different *Weld* implementation in WildFly than in JBoss AS 7.1.1.Final, where the same tests are passing. > I am also wondering why we are creating wars which contains Arquillian related stuff for client tests ? Should not we create more granular deployment, which will distinguish among client, server and warp tests ? -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-11454) Migrate Push CDI tests based on Arquillian to framework

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11454?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11454: ------------------------------- Component/s: component-push/poll (was: core) > Migrate Push CDI tests based on Arquillian to framework > ------------------------------------------------------- > > Key: RF-11454 > URL: https://issues.jboss.org/browse/RF-11454 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-push/poll, tests - unit > Affects Versions: 4.1.0.Milestone3 > Reporter: Lukáš Fryč > Fix For: 5-Tracking > > > In scope of RF-11110, Push CDI has been developed and tested using Arquillian in separated Maven project: > https://github.com/lfryc/richfaces-cdi-push-prototype > It was decided [1] to not to migrate these tests in scope of 4.1 and postpone them to 4.2. > [1] http://transcripts.jboss.org/meeting/irc.freenode.org/richfaces/2011/rich... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-11153) Text exceeds edges of consumer window in CDI sample for aj4:push in showcase

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11153?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11153: ------------------------------- Component/s: component-push/poll > Text exceeds edges of consumer window in CDI sample for aj4:push in showcase > ---------------------------------------------------------------------------- > > Key: RF-11153 > URL: https://issues.jboss.org/browse/RF-11153 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, examples, showcase > Affects Versions: 4.1.0.Milestone1 > Environment: richfaces-showcase-4.1.0-SNAPSHOT > Reporter: Juraj Húska > Assignee: Lukáš Fryč > Priority: Optional > Fix For: 5-Future > > Attachments: firstWrong.png, secondWrong.png > > > When the message which is pushed to consumers is too long, like 50 characters and more, than the output on consumers window looks quite ugly, since the message exceeds the white part of the page. The solution would be either to enlarge the white part, or to make a restriction about size of message to for example 40 chars. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-11462) showcase - demo a4j:push - sample CDI Push - incorrect behavior of replacing consumers windows when the limit(5) is reached

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11462?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11462: ------------------------------- Component/s: component-push/poll > showcase - demo a4j:push - sample CDI Push - incorrect behavior of replacing consumers windows when the limit(5) is reached > --------------------------------------------------------------------------------------------------------------------------- > > Key: RF-11462 > URL: https://issues.jboss.org/browse/RF-11462 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll, showcase > Affects Versions: 4.1.0.Milestone2 > Environment: app: richfaces-showcase-4.1.0-SNAPSHOT > browsers: Chrome, Firefox, IE > containers: JBoss AS 6.x, 7.x, > Reporter: Juraj Húska > Priority: Optional > Fix For: 5-Future > > > When the limit of number of consumers windows is reached(5), then when another consumer is invoked, it causes that the window which was invoked as first is replaced with another consumer. > When I close any of the consumer window then the new invoked consumer does not replace that one closed, but in order that window which is currently supposed to be replaced. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-9156) Push: Unit tests development

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-9156?page=com.atlassian.jira.plugin.sy... ] Brian Leathem updated RF-9156: ------------------------------ Component/s: component-push/poll > Push: Unit tests development > ---------------------------- > > Key: RF-9156 > URL: https://issues.jboss.org/browse/RF-9156 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: component-push/poll, tests - unit > Affects Versions: 4.0.0.Milestone2 > Reporter: Ilya Shaikovsky > Assignee: Nick Belaevski > Fix For: 5-Future > > -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-11455) Full-featured Push CDI integration based on CDI 1.1

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-11455?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-11455: ------------------------------- Component/s: component-push/poll (was: core) > Full-featured Push CDI integration based on CDI 1.1 > --------------------------------------------------- > > Key: RF-11455 > URL: https://issues.jboss.org/browse/RF-11455 > Project: RichFaces > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.1.0.Milestone3 > Reporter: Lukáš Fryč > Fix For: 5-Future > > > When designing Push CDI integration in 4.1.0.M3, it wasn't possible to use classic CDI event observers. > As result, CDI extension was designed instead with limitations bellow. > Once CDI-36 will be solved, it will be possible to read InjectionPoint and its @Push annotation with classic event observer. > * @Push annotation's parameters will be switched to @Nonbinding (there will be no reason to have them bound and user will be able to observe all @Push events). > * It will also make possible to use runtime selection of topics/subtopics (not currently possible, observers are specifically resolved in deploy time) -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12573) a4j:push results endless spinner in addressbar on safari

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12573?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12573: ------------------------------- Component/s: component-push/poll (was: core) > a4j:push results endless spinner in addressbar on safari > -------------------------------------------------------- > > Key: RF-12573 > URL: https://issues.jboss.org/browse/RF-12573 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.3.Final > Reporter: nimo stephan > Fix For: 5-Tracking > > > When using aj4:push then the loading-indicator of safari which is visible in the url-addressbar is working and visible forever and does not stop! While the loading indicator is running, the user cannot press any button and cannot type into any input field sporadically. When I make a full page refresh, then input on the html-page works, however the loading indicator does not stop from loading. Hence the user thinks he cannot make any work on that site as long as the working indicator is shown. That is not user-friendly. Maybe the bug is within the athmosphere lib rf is using. The loading indicator problem is related to these problems: > http://stackoverflow.com/questions/9932462/how-to-remove-safaris-loading-... > http://stackoverflow.com/questions/1064782/stop-the-browser-throbber-of-d... > http://www.shanison.com/2010/05/10/stop-the-browser-%E2%80%9Cthrobber-of-... -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12543) a4j:push after ajax-rendered does not have its javascript included

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12543?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12543: ------------------------------- Component/s: component-push/poll > a4j:push after ajax-rendered does not have its javascript included > ------------------------------------------------------------------ > > Key: RF-12543 > URL: https://issues.jboss.org/browse/RF-12543 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Environment: RichFaces 4.2.2 FINAL > Reporter: nimo stephan > Fix For: 5-Tracking > > > I have a4j:push within my page which should be rendered only if the property "pushIsActivated" is true. When changing the property by a button to true, then I want to make a ajax-rendering which renders the a4j:push. However, the javascript portion is not created within the aj4:push, hence the component does not work! I have to make a full page refresh, then the javascript portion is inserted and a4j:push works as expected. However, I have to do a full page refresh. I guess, it is a bug, because the a4j:push has a rendered-property which can be changed by ajax, hence it has to work after ajax-update. > {code} > <h:form id="my-form" prependId="false" style="display:none;"> > <a4j:push rendered="#{mybean.pushIsActivated}" address=".." onerror=".." ondataavailable=".."> > <a4j:ajax event="dataavailable" render="my-section"/> > </a4j:push> > </h:form> > {code} > If I only render my-form after changing the property, a4j:push does not work: > {code} > <h:form> > <h:commandButton value="Activate Push " action="#{myBean.setActivatePushToTrue}"> > <f:ajax render=":my-form"/> > </h:commandButton> > </h:form> > {code} > I have to do a full page refresh, only then aj4:push works: > {code} > <h:form> > <h:commandButton value="Activate Push " action="#{myBean.setPushActivateToTrue}" onclick="submit();" /> > </h:form> > {code} > Richfaces does insert the needed javascript only after a full page request: > {code} > <script type="text/javascript">RichFaces.Push.setPushResourceUrl.....;</script> > {code} > If I make a ajax-rendering, Richfaces does NOT (!) insert the needed javascript. Hence a4j:push does not work. -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-12544) Mime type problem with aj4:push and safari

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-12544?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12544: ------------------------------- Component/s: component-push/poll > Mime type problem with aj4:push and safari > ------------------------------------------ > > Key: RF-12544 > URL: https://issues.jboss.org/browse/RF-12544 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-push/poll > Affects Versions: 4.2.3.Final > Reporter: nimo stephan > Fix For: 5-Tracking > > > When using a4j:push with (actual version of) Safari, then I get this within my javascript-console: > "Resource interpreted as image but transferred with MIME type text/html." -- 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, 9 months

1
0
0 / 0

[JBoss JIRA] (RF-13197) Input with name javax.faces.ViewState is not rendered after submit

by Brian Leathem (JIRA)

[ https://issues.jboss.org/browse/RF-13197?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-13197: ------------------------------- Fix Version/s: 5.0.0.Alpha3 > Input with name javax.faces.ViewState is not rendered after submit > ------------------------------------------------------------------ > > Key: RF-13197 > URL: https://issues.jboss.org/browse/RF-13197 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: core > Affects Versions: 5.0.0.Alpha1 > Environment: WildFly 8.0.Alpha4 also GlassFish 4 > Mojarra 2.2 > Chrome, Firefox > Reporter: Juraj Húska > Labels: jsf22 > Fix For: 5.0.0.Alpha3 > > > The issue is reproducible with framework test {{ITMultipleFormUpdate.when_form_is_explicitly_listed_in_render_then_its_ViewState_should_be_updated_after_response}}. > Expected: > After submitting the form, the {{ViewState}} should be updated. > Actual: > Elements with the name {{javax.faces.ViewState}} are not rendered for both of the inputs. > Please see steps to reproduce. -- 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, 9 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 September 2013