May 2013 - richfaces-issues - Jboss List Archives

[JBoss JIRA] (RF-12903) Review the usage of dist/assembly as the richfaces.jar assembler and depchain

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12903?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12903: --------------------------------- I did everything except separation to dedicated JAR. Currently, {{resource-optimizer}} is part of {{richfaces.jar}} under {{org.richfaces.resource.optimizer}} package, coming from {{src/main/resource-optimizer}} folder. > Review the usage of dist/assembly as the richfaces.jar assembler and depchain > ----------------------------------------------------------------------------- > > Key: RF-12903 > URL: https://issues.jboss.org/browse/RF-12903 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 5.0.0.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-12903) Review the usage of dist/assembly as the richfaces.jar assembler and depchain

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12903?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12903 at 5/3/13 11:32 AM: ---------------------------------------------------------- I did everything except separation to dedicated JAR. Currently, {{resource-optimizer}} is part of {{richfaces.jar}} under {{org.richfaces.resource.optimizer}} package, coming from {{src/main/resource-optimizer}} folder. I would open an issue for separating this functionality to separated JAR. was (Author: lfryc): I did everything except separation to dedicated JAR. Currently, {{resource-optimizer}} is part of {{richfaces.jar}} under {{org.richfaces.resource.optimizer}} package, coming from {{src/main/resource-optimizer}} folder. > Review the usage of dist/assembly as the richfaces.jar assembler and depchain > ----------------------------------------------------------------------------- > > Key: RF-12903 > URL: https://issues.jboss.org/browse/RF-12903 > Project: RichFaces > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build/distribution > Reporter: Lukáš Fryč > Assignee: Lukáš Fryč > Priority: Critical > Fix For: 5.0.0.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 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, 8 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: --------------------------------------- I just installed WAS 8.0.0.6 (released on April 29th) on my dev-machine. Even though it fixed some JSF-bugs it didnt help with this particular problem. Sorry. > 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, 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-12962) No tag defined for name actionListener

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/RF-12962?page=com.atlassian.jira.plugin.s... ] Pavol Pitonak updated RF-12962: ------------------------------- Affects Version/s: 5.0.0.Alpha1 > No tag defined for name actionListener > -------------------------------------- > > Key: RF-12962 > URL: https://issues.jboss.org/browse/RF-12962 > Project: RichFaces > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: component-a4j-core > Affects Versions: 5.0.0.Alpha1 > Environment: RichFaces 5.0.0-SNAPSHOT > Reporter: Pavol Pitonak > Priority: Blocker > > After packages refactoring, component actionListener is no longer available. > {quote} > <r:actionListener> Tag Library supports namespace: http://richfaces.org/rich, but no tag was defined for name: actionListener > {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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-12962) No tag defined for name actionListener

by Pavol Pitonak (JIRA)

Pavol Pitonak created RF-12962: ---------------------------------- Summary: No tag defined for name actionListener Key: RF-12962 URL: https://issues.jboss.org/browse/RF-12962 Project: RichFaces Issue Type: Bug Security Level: Public (Everyone can see) Components: component-a4j-core Environment: RichFaces 5.0.0-SNAPSHOT Reporter: Pavol Pitonak Priority: Blocker After packages refactoring, component actionListener is no longer available. {quote} <r:actionListener> Tag Library supports namespace: http://richfaces.org/rich, but no tag was defined for name: actionListener {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, 8 months

1
0
0 / 0

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

by Jan Papousek (JIRA)

[ https://issues.jboss.org/browse/RF-12960?page=com.atlassian.jira.plugin.s... ] Jan Papousek commented on RF-12960: ----------------------------------- Brian: I am not sure I understand to your question. Usually the archetypes are available from JBoss Public Maven Repository (releases and snapshots) and Maven Central (releases), but 5.0.0-SNAPSHOT is not available in JBoss Public. > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-12916) a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12916: --------------------------------- The recommended approach would be writing a simple demo application and configuring it to work in a cluster. We could probably start with a push demo: https://github.com/richfaces/richfaces5/tree/master/examples/push-demo > a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS) > ------------------------------------------------------------------------------------------------------ > > Key: RF-12916 > URL: https://issues.jboss.org/browse/RF-12916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Luan Cestari > Assignee: Lukáš Fryč > > The customer is using JBoss in cluster and he have a Richfaces 4. The web client is using websocket using Richfaces/Atmosphere. The problem is that the customer have heavy asynchronous process that need to notify all websockets from all users (using a JMS, 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-12916) a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč updated RF-12916: ---------------------------- Labels: waiting_on_user (was: ) > a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS) > ------------------------------------------------------------------------------------------------------ > > Key: RF-12916 > URL: https://issues.jboss.org/browse/RF-12916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Luan Cestari > Assignee: Lukáš Fryč > Labels: waiting_on_user > > The customer is using JBoss in cluster and he have a Richfaces 4. The web client is using websocket using Richfaces/Atmosphere. The problem is that the customer have heavy asynchronous process that need to notify all websockets from all users (using a JMS, 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-12916) a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč edited comment on RF-12916 at 5/3/13 2:44 AM: --------------------------------------------------------- We need to do a proof of concept that this works correctly using JMS clustering as I outlined. I wonder if you could do this proof of concept and share the results, we can discuss details if necessary. was (Author: lfryc): We need to do a proof of concept that this works correctly as I outlined through JMS clustering. I wonder if you could do this proof of concept and share the results, we can discuss details if necessary. > a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS) > ------------------------------------------------------------------------------------------------------ > > Key: RF-12916 > URL: https://issues.jboss.org/browse/RF-12916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Luan Cestari > Assignee: Lukáš Fryč > > The customer is using JBoss in cluster and he have a Richfaces 4. The web client is using websocket using Richfaces/Atmosphere. The problem is that the customer have heavy asynchronous process that need to notify all websockets from all users (using a JMS, 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

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (RF-12916) a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS)

by Lukáš Fryč (JIRA)

[ https://issues.jboss.org/browse/RF-12916?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on RF-12916: --------------------------------- We need to do a proof of concept that this works correctly as I outlined through JMS clustering. I wonder if you could do this proof of concept and share the results, we can discuss details if necessary. > a4j:push doesn't work in cluster and doesn't have an asynchronous way to notify all Topics (e.g. JMS) > ------------------------------------------------------------------------------------------------------ > > Key: RF-12916 > URL: https://issues.jboss.org/browse/RF-12916 > Project: RichFaces > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Affects Versions: 4.3.0.Final > Reporter: Luan Cestari > Assignee: Lukáš Fryč > > The customer is using JBoss in cluster and he have a Richfaces 4. The web client is using websocket using Richfaces/Atmosphere. The problem is that the customer have heavy asynchronous process that need to notify all websockets from all users (using a JMS, 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

11 years, 8 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 May 2013