April 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12801) org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere

by Sebastian Cramer (JIRA)

[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ] Sebastian Cramer edited comment on RF-12801 at 4/24/13 6:25 AM: ---------------------------------------------------------------- Hey Lukáš. AFAIK the resolver is always affected for WAS8.0.0.x (didnt check 8.0.0.6 - which will supposedly contain a newer myfaces version but is not released yet) as soon as you enable resource optimization (for me it is on Windows7 and HP-UX - it seems to be platform independend). There are no log entries or anything. Just all injected bean references turn out to be null (well that results in a bunch of log entries - but these wont help). As soon as I use Michael's workaround the injection is working but the infamous "packed.js is included multiple times" bug strikes. I know it's not really helpful - but if I can be of any further assistance I will gladly help. was (Author: sebcramer): Hey Lukáš. AFAIK the resolver is always affected for WAS8.0.x (didnt check 8.0.6 - is that available already?) as soon as you enable resource optimization (for me it is on Windows7 and HP-UX - it seems to be platform independend). There are no log entries or anything. Just all injected bean references turn out to be null (well that results in a bunch of log entries - but these wont help). As soon as I use Michael's workaround the injection is working but the infamous "packed.js is included multiple times" bug strikes. I know it's not really helpful - but if I can be of any further assistance I will gladly help. > org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere > ------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12801 > URL: https://issues.jboss.org/browse/RF-12801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.3.0.Final > Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final > Reporter: Erdem YILMAZ > Assignee: Lukáš Fryč > Labels: ELResolver, optimization, resource, waiting_on_user, websphere > > when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere. > resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour. > we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12801) org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere

by Sebastian Cramer (JIRA)

[ https://issues.jboss.org/browse/RF-12801?page=com.atlassian.jira.plugin.s... ] Sebastian Cramer commented on RF-12801: --------------------------------------- Hey Lukáš. AFAIK the resolver is always affected for WAS8.0.x (didnt check 8.0.6 - is that available already?) as soon as you enable resource optimization (for me it is on Windows7 and HP-UX - it seems to be platform independend). There are no log entries or anything. Just all injected bean references turn out to be null (well that results in a bunch of log entries - but these wont help). As soon as I use Michael's workaround the injection is working but the infamous "packed.js is included multiple times" bug strikes. I know it's not really helpful - but if I can be of any further assistance I will gladly help. > org.richfaces.resourceOptimization.enabled parameter with true value disables WebBeansELResolver to register in Websphere > ------------------------------------------------------------------------------------------------------------------------- > > Key: RF-12801 > URL: https://issues.jboss.org/browse/RF-12801 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: resource handling > Affects Versions: 4.3.0.Final > Environment: Websphere 8.0.0.3 and Websphere 8.0.0.5, Windows 7, Richfaces 4.3.0.Final > Reporter: Erdem YILMAZ > Assignee: Lukáš Fryč > Labels: ELResolver, optimization, resource, waiting_on_user, websphere > > when we use context param org.richfaces.resourceOptimization.enabled in web.xml, the CDI listener is not registered in Websphere. > resourcesOptimization parameter disables org.apache.webbeans.el.WebBeansELResolver in Websphere. In richfaces 4.2.3.Final version, resourceOptimization parameter do not affect the CDI behaviour. > we have disabled the resource optimization in order to work with richfaces but for the production environment, we prefer to enable 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12008) Add RichFaces AS7 module to distribution

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12008?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12008 at 4/24/13 4:44 AM: ---------------------------------------------------------- Hey Manuel, this is likely the issue of uninitialized services for leaked RichFaces service factory (similarly to RF-12896). Note that we would need to fix the modular class loading for RichFaces and test it properly in order to fully support RichFaces as AS module. was (Author: lfryc): Hey Manuel, this is likely the issue of uninitializated services for leader RichFaces service factory (similarly to RF-12896). Note that we would need to fix the modular class loading for RichFaces and test it properly in order to fully support RichFaces as AS module. > Add RichFaces AS7 module to distribution > ---------------------------------------- > > Key: RF-12008 > URL: https://issues.jboss.org/browse/RF-12008 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Lukáš Fryč > Fix For: 5-Future > > > It would be nice to have RichFaces packed as JBoss AS7 module, so it could be just grabbed and inserted to {{modules}} directory (similary to SnowDrop distribution [1]). > It would allow to reuse RichFaces between projects and make the WARs really skinny for those who are deploying several RichFaces-based applications to the AS7. > [1] https://docs.jboss.org/author/display/SNOWDROP/The+Spring+Deployer -- 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-12008) Add RichFaces AS7 module to distribution

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12008?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12008: --------------------------------- Hey Manuel, this is likely the issue of uninitializated services for leader RichFaces service factory (similarly to RF-12896). Note that we would need to fix the modular class loading for RichFaces and test it properly in order to fully support RichFaces as AS module. > Add RichFaces AS7 module to distribution > ---------------------------------------- > > Key: RF-12008 > URL: https://issues.jboss.org/browse/RF-12008 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Lukáš Fryč > Fix For: 5-Future > > > It would be nice to have RichFaces packed as JBoss AS7 module, so it could be just grabbed and inserted to {{modules}} directory (similary to SnowDrop distribution [1]). > It would allow to reuse RichFaces between projects and make the WARs really skinny for those who are deploying several RichFaces-based applications to the AS7. > [1] https://docs.jboss.org/author/display/SNOWDROP/The+Spring+Deployer -- 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-12896) Richfaces TopicsContext.lookup() returns null after redeployment when Richfaces is deployed as a module in JBoss EAP 6

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12896?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12896: --------------------------------- The problem is the RichFaces' ServiceFactory which holds reference to PushContextFactory leaks from first deployment to next deployments in case of RichFaces JAR as a module - thus [during initialization|https://github.com/richfaces/core/blob/master/impl/src/mai...] across several deployments, we [get the same instance of PushContext|https://github.com/richfaces/core/blob/master/impl/src/main/j...] which doesn't have a TopicsContext instance set (might be due to serialization). That's why we need to initialize it using {{PushContext#init(FacesContext)}} method before we want to use it. The better workaround might be initializating the PushContext once JSF is loaded (similarly to {{InitializationListener}}, on [{{PostConstructApplication}}|https://github.com/richfaces/core/blob/master/impl/src/main/resources/META-INF/faces-config.xml#L14]). ---- Note that when RichFaces is used a module, its services likely leaks from one deployment to another. In order to fix this issue properly, we would need to either isolate deployments (load RichFaces for each deployment separately) or remove binding of deployments' services to TCCL. > Richfaces TopicsContext.lookup() returns null after redeployment when Richfaces is deployed as a module in JBoss EAP 6 > ---------------------------------------------------------------------------------------------------------------------- > > Key: RF-12896 > URL: https://issues.jboss.org/browse/RF-12896 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.2.3.Final > Reporter: Ilia Vassilev > Assignee: Brian Leathem > Fix For: 4.3.2 > > Attachments: jboss-as-helloworld-rf.war, modules.zip, RichBean.java > > > Our application uses Richfaces push functionality and makes a call to lookup the TopicsContext in the constructor of one of a backing bean. The code looks like this below. This works fine when Richfaces is packaged in the war, however when we extract the richfaces jars into a module and have our applications declare a module dependency, there is an issue when we redeploy the application. It works fine when JBoss is first started, but if we redeploy the application while JBoss is running, we are getting a NullPointerException in our application because TopicsContext.lookup() is returning null. > {code} > @PostConstruct > public void postContruct() { > TopicsContext topicsContext = TopicsContext.lookup(); > if(topicsContext == null) > log(" - topicsContext is NULL"); > pushTK = new TopicKey(PUSH_TOPIC); > // this will fail if topicsContext is null (NPE) > topicsContext.getOrCreateTopic(pushTK); > } > {code} -- 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-12940) Showcase: fix path to outputPanel - compositeMessages sample source

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12940?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-12940. ----------------------------- Resolution: Done > Showcase: fix path to outputPanel - compositeMessages sample source > ------------------------------------------------------------------- > > Key: RF-12940 > URL: https://issues.jboss.org/browse/RF-12940 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.1 > Reporter: Michal Petrov > Assignee: Michal Petrov > Priority: Trivial > Fix For: 4.3.2 > > -- 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-12941) Showcase: ProgressBar demo - remove obsolete attribute and make the progress smoother

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12941?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč resolved RF-12941. ----------------------------- Resolution: Done > Showcase: ProgressBar demo - remove obsolete attribute and make the progress smoother > ------------------------------------------------------------------------------------- > > Key: RF-12941 > URL: https://issues.jboss.org/browse/RF-12941 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.1 > Reporter: Michal Petrov > Assignee: Michal Petrov > Priority: Minor > Fix For: 4.3.2 > > > The current solution is not a nice one (discovered after someone at stackOverflow wanted to create a simple progressbar). > I changed it so it would increment itself via a4j:ajax, and also made the interval shorter as it seemed to have been taking a long time to finish. > And I also removed an obsolete (and unimplemented) 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12941) Showcase: ProgressBar demo - remove obsolete attribute and make the progress smoother

by Lukáš Fryč (JIRA)

Lukáš Fryč created RF-12941: ------------------------------- Summary: Showcase: ProgressBar demo - remove obsolete attribute and make the progress smoother Key: RF-12941 URL: https://issues.jboss.org/browse/RF-12941 Project: RichFaces Issue Type: Feature Request Security Level: Public (Everyone can see) Components: showcase Affects Versions: 4.3.1 Reporter: Michal Petrov Assignee: Michal Petrov Fix For: 4.3.2 The current solution is not a nice one (discovered after someone at stackOverflow wanted to create a simple progressbar). I changed it so it would increment itself via a4j:ajax, and also made the interval shorter as it seemed to have been taking a long time to finish. And I also removed an obsolete (and unimplemented) 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12941) Showcase: ProgressBar demo - remove obsolete attribute and make the progress smoother

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12941?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12941: ---------------------------- Priority: Minor (was: Major) > Showcase: ProgressBar demo - remove obsolete attribute and make the progress smoother > ------------------------------------------------------------------------------------- > > Key: RF-12941 > URL: https://issues.jboss.org/browse/RF-12941 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.1 > Reporter: Michal Petrov > Assignee: Michal Petrov > Priority: Minor > Fix For: 4.3.2 > > > The current solution is not a nice one (discovered after someone at stackOverflow wanted to create a simple progressbar). > I changed it so it would increment itself via a4j:ajax, and also made the interval shorter as it seemed to have been taking a long time to finish. > And I also removed an obsolete (and unimplemented) 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

12 years, 5 months

1
0
0 / 0

[JBoss JIRA] (RF-12940) Showcase: fix path to outputPanel - compositeMessages sample source

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12940?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12940: ---------------------------- Priority: Trivial (was: Major) > Showcase: fix path to outputPanel - compositeMessages sample source > ------------------------------------------------------------------- > > Key: RF-12940 > URL: https://issues.jboss.org/browse/RF-12940 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: showcase > Affects Versions: 4.3.1 > Reporter: Michal Petrov > Assignee: Michal Petrov > Priority: Trivial > Fix For: 4.3.2 > > -- 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

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

richfaces-issues April 2013