[JBoss JIRA] (RF-11965) showcase - a4j:push - error thrown after creating topic for pushCdi
by Juraj Huska (JIRA)
Juraj Huska created RF-11965:
--------------------------------
Summary: showcase - a4j:push - error thrown after creating topic for pushCdi
Key: RF-11965
URL: https://issues.jboss.org/browse/RF-11965
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-push/poll, showcase
Affects Versions: 4.2.0.CR1
Environment: container: JBoss AS 7.1.0.CR1b
Reporter: Juraj Huska
Priority: Minor
When deploying showcase 4.2.0.CR1 then after pushCdi topic created an error is thrown:
{code}
18:13:42,211 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) initializing
18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) AS7MessagingProviderManagement initialized
18:13:42,219 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushJms
18:13:42,761 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushTopicsContext
18:13:42,802 INFO [org.richfaces.demo.push.JMSInitializer] (MSC service thread 1-2) creating topic pushCdi
18:13:42,972 SEVERE [org.richfaces.demo.push.MessageProducerRunnable] (MessageProducerThread) javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.$
at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:397) [guava-10.0.1.jar:]
at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl.createTopic(JMSTopicsContextImpl.java:281) [richfaces-core-impl-4.2.0.CR1.jar:]
at org.richfaces.application.push.TopicsContext.getOrCreateTopic(TopicsContext.java:48) [richfaces-core-api-4.2.0.CR1.jar:]
at org.richfaces.application.push.TopicsContext.publish(TopicsContext.java:69) [richfaces-core-api-4.2.0.CR1.jar:]
at org.richfaces.demo.push.TopicsContextMessageProducer.sendMessage(TopicsContextMessageProducer.java:46) [classes:]
at org.richfaces.demo.push.MessageProducerRunnable.run(MessageProducerRunnable.java:57) [classes:]
at java.lang.Thread.run(Thread.java:662) [:1.6.0_22]
Caused by: javax.faces.FacesException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext
at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:207) [richfaces-core-impl-4.2.0.CR1.jar:]
at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:195) [richfaces-core-impl-4.2.0.CR1.jar:]
at com.google.common.collect.ComputingConcurrentHashMap$ComputingValueReference.compute(ComputingConcurrentHashMap.java:355) [guava-10.0.1.jar:]
at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.compute(ComputingConcurrentHashMap.java:184) [guava-10.0.1.jar:]
at com.google.common.collect.ComputingConcurrentHashMap$ComputingSegment.getOrCompute(ComputingConcurrentHashMap.java:153) [guava-10.0.1.jar:]
at com.google.common.collect.ComputingConcurrentHashMap.getOrCompute(ComputingConcurrentHashMap.java:69) [guava-10.0.1.jar:]
at com.google.common.collect.ComputingConcurrentHashMap$ComputingMapAdapter.get(ComputingConcurrentHashMap.java:393) [guava-10.0.1.jar:]
... 6 more
Caused by: javax.naming.NameNotFoundException: topic/pushTopicsContext -- service jboss.naming.context.java.topic.pushTopicsContext
at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:92)
at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:177)
at org.jboss.as.naming.InitialContext.lookup(InitialContext.java:87)
at javax.naming.InitialContext.lookup(InitialContext.java:396) [:1.6.0_22]
at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.lookupTopic(JMSTopicsContextImpl.java:94) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:]
at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$JMSTopicContext.start(JMSTopicsContextImpl.java:125) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:]
at org.richfaces.application.push.impl.jms.JMSTopicsContextImpl$1.apply(JMSTopicsContextImpl.java:199) [richfaces-core-impl-4.2.0-20120130.140419-26.jar:]
... 12 more
{code}
The functionality of push demos is fine, just the tests are not passing on Hudson, which I have to investigate whether it is caused by this one.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (RF-12085) The richfaces version change script is missing version strings in the kitchensink archetype file
by Brian Leathem (JIRA)
Brian Leathem created RF-12085:
----------------------------------
Summary: The richfaces version change script is missing version strings in the kitchensink archetype file
Key: RF-12085
URL: https://issues.jboss.org/browse/RF-12085
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: archetype, build/distribution
Reporter: Brian Leathem
Assignee: Lukáš Fryč
Priority: Critical
Fix For: 4.2.1.CR1
{code}
[archetypes (release/4.2.1.CR1)]> ack 4.3.0
components/component/src/main/resources/META-INF/maven/archetype-metadata.xml
39: <defaultValue>4.3.0-SNAPSHOT</defaultValue>
components/components-aggregator/src/main/resources/META-INF/maven/archetype-metadata.xml
36: <defaultValue>4.3.0-SNAPSHOT</defaultValue>
components/component-short/src/main/resources/META-INF/maven/archetype-metadata.xml
39: <defaultValue>4.3.0-SNAPSHOT</defaultValue>
kitchensink/src/main/resources/META-INF/maven/archetype-metadata.xml
10: <defaultValue>4.3.0-SNAPSHOT</defaultValue>
kitchensink/src/test/resources/projects/basic/archetype.properties
5:richfaces-version=4.3.0-SNAPSHOT
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (RF-12077) Selection in extendedDataTable doesn't work in Chrome
by Vladimir Rom (JIRA)
Vladimir Rom created RF-12077:
---------------------------------
Summary: Selection in extendedDataTable doesn't work in Chrome
Key: RF-12077
URL: https://issues.jboss.org/browse/RF-12077
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.2.0.Final
Environment: Windows XP. JBoss AS 7 Chrome 17.0.963.83
Reporter: Vladimir Rom
Priority: Blocker
JavaScript error in console on rendered page with
Uncaught TypeError: Cannot read property 'length' of null
richfaces.utils.getCSSRule extendedDataTable.js.jsf:40
richfaces.ui.ExtendedDataTable.richfaces.BaseComponent.extendClass.initialize extendedDataTable.js.jsf:362
jQuery.extend.proxy.proxyjquery.js.jsf:814
jQuery.Callbacks.firejquery.js.jsf:1046
jQuery.Callbacks.self.fireWithjquery.js.jsf:1164
jQuery.extend.readyjquery.js.jsf:435
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (RF-11968) 4.2.0.CR1 contextMenu positioning incorrect when dynamically rendering on row select
by Brendan Healey (JIRA)
Brendan Healey created RF-11968:
-----------------------------------
Summary: 4.2.0.CR1 contextMenu positioning incorrect when dynamically rendering on row select
Key: RF-11968
URL: https://issues.jboss.org/browse/RF-11968
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-menu
Affects Versions: 4.2.0.CR1
Environment: Chrome browser Glassfish 3.1.1 Mojarra 2.1.6
Reporter: Brendan Healey
There's a positioning error with contextMenu in the following scenario.
I have an extendedDataTable which renders a rich:panel when a row in the
table is selected. Initially no row is selected and the rich:panel is not
rendered. I right click in the table and the menuItem appears way below
the row I right clicked.
<rich:extendedDataTable
id="mytable" value="#{bean.someList}" var="var"
selection="#{bean.selectedRow}"
selectionMode="single">
<a4j:ajax render="panelAjaxTarget"
event="selectionchange"
listener="#{bean.doRowSelect}"/>
...
</rich:extendedDataTable>
<h:panelGroup id="panelAjaxTarget">
<rich:panel rendered="#{bean.selectedDepartment != null}">
...
</rich:panel>
</h:panelGroup>
<rich:contextMenu target="mytable" mode="ajax">
<rich:menuItem label="Test" onclick="alert('hello');"/>
</rich:contextMenu>
public void doRowSelect(...) {
selectedDepartment = ... (usual stuff);
}
Also tried with contextMenu mode="client" with the same result.
Regards,
Brendan.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (RF-11996) ContextMenu on several rows in extendedDataTable
by Philip Maes (JIRA)
Philip Maes created RF-11996:
--------------------------------
Summary: ContextMenu on several rows in extendedDataTable
Key: RF-11996
URL: https://issues.jboss.org/browse/RF-11996
Project: RichFaces
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: component-tables
Affects Versions: 4.2.0.CR1
Reporter: Philip Maes
Hi,
I was using the contextmenu from the sandbox and now I'm using the one from 4.2.0.RC1.
With the old one, when several rows in a table were selected the right-click to open the contextmenu didn't unselect others rows.
The new contextMenu does it. It's quite embarassing because we can't use it to apply a contextmenu for several selected rows...
Thanks in advance,
best regards.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (RF-12013) Deadlock in push component
by Stian Thorgersen (JIRA)
Stian Thorgersen created RF-12013:
-------------------------------------
Summary: Deadlock in push component
Key: RF-12013
URL: https://issues.jboss.org/browse/RF-12013
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: component-push/poll
Affects Versions: 4.2.0.Final
Reporter: Stian Thorgersen
Deadlocked threads in the push component prevented server from stopping. Not sure whether or not this happened when I initiated shutdown or if these where hanging around for a while.
Relevant output from jstack:
{code}
Found one Java-level deadlock:
=============================
"push-publish-thread-1":
waiting to lock monitor 0x0000000042650238 (object 0x00000000e5ed5a50, a org.richfaces.application.push.impl.RequestImpl),
which is held by "Atmosphere-AsyncWrite-0"
"Atmosphere-AsyncWrite-0":
waiting to lock monitor 0x00000000427d9ec0 (object 0x00000000e5ed59a0, a org.richfaces.application.push.impl.SessionImpl),
which is held by "push-publish-thread-1"
Java stack information for the threads listed above:
===================================================
"push-publish-thread-1":
at org.richfaces.application.push.impl.RequestImpl.postMessages(RequestImpl.java:85)
- waiting to lock <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at org.richfaces.application.push.impl.SessionImpl.push(SessionImpl.java:237)
- locked <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.TopicImpl$TopicContext.publishMessages(TopicImpl.java:88)
at org.richfaces.application.push.impl.TopicImpl$PublishTask.run(TopicImpl.java:53)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
"Atmosphere-AsyncWrite-0":
at org.richfaces.application.push.impl.SessionImpl.disconnect(SessionImpl.java:117)
- waiting to lock <0x00000000e5ed59a0> (a org.richfaces.application.push.impl.SessionImpl)
at org.richfaces.application.push.impl.RequestImpl.disconnect(RequestImpl.java:107)
at org.richfaces.application.push.impl.RequestImpl.onResume(RequestImpl.java:115)
at org.atmosphere.cpr.AtmosphereResourceImpl.onResume(AtmosphereResourceImpl.java:651)
at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:600)
at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.AtmosphereResourceImpl.resume(AtmosphereResourceImpl.java:185)
- locked <0x00000000e5ee3380> (a org.atmosphere.cpr.AtmosphereResourceEventImpl)
at org.richfaces.application.push.impl.RequestImpl.onBroadcast(RequestImpl.java:129)
- locked <0x00000000e5ed5a50> (a org.richfaces.application.push.impl.RequestImpl)
at org.atmosphere.cpr.AtmosphereResourceImpl.onBroadcast(AtmosphereResourceImpl.java:663)
at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:608)
at org.atmosphere.cpr.AtmosphereResourceImpl.notifyListeners(AtmosphereResourceImpl.java:584)
at org.atmosphere.cpr.DefaultBroadcaster.executeAsyncWrite(DefaultBroadcaster.java:713)
at org.atmosphere.cpr.DefaultBroadcaster$3.run(DefaultBroadcaster.java:747)
- locked <0x00000000e5ed5a88> (a org.atmosphere.cpr.AtmosphereResourceImpl)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
Found 1 deadlock.
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months
[JBoss JIRA] (RF-12078) action fired twice, when invoked by a a4j:commandButton residing in a tables' footer facet
by Markus Staab (JIRA)
Markus Staab created RF-12078:
---------------------------------
Summary: action fired twice, when invoked by a a4j:commandButton residing in a tables' footer facet
Key: RF-12078
URL: https://issues.jboss.org/browse/RF-12078
Project: RichFaces
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 3.3.3.Final
Environment: Liferay 5.2.4, Portlet 2.0, JSF 1.2, Richfaces 3.3.3
Reporter: Markus Staab
when adding a a4j:commandButton inside a rich:databables footer-facet, the corresponding action will be invoked twice while the process action phase.
The problem only occurs, when the commandButton 'process'es the datatable itself.
{code}
<rich:dataTable id="myTable" value="#{aDataModel}" var="myVar" >
<rich:column >
<f:facet name="header">A HEADER</f:facet>
SOME CONTENT IN THE ROW
</h:inputText>
</rich:column>
<f:facet name="footer">
<rich:column>
<a4j:commandButton
value="ADD ANOTHER ROW"
reRender="myTable"
action="#{form.addNewRow}" ajaxSingle="true"
process="myTable"
/>
</rich:column>
</f:facet>
</rich:dataTable>
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 9 months