[ https://jira.jboss.org/browse/RF-9163?page=com.atlassian.jira.plugin.syst... ] Ilya Shaikovsky updated RF-9163: -------------------------------- Fix Version/s: 4.0.0.Milestone3 Affects Version/s: 4.0.0.Milestone2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/RF-9163?page=com.atlassian.jira.plugin.syst... ] Nick Belaevski updated RF-9163: ------------------------------- Fix Version/s: 4.0.0.Milestone4 (was: 4.0.0.Milestone3) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/RF-9163?page=com.atlassian.jira.plugin.syst... ] Lukas Fryc reassigned RF-9163: ------------------------------ Assignee: Lukas Fryc (was: Prabhat Jha) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/browse/RF-9163?page=com.atlassian.jira.plugin.syst... ] Nick Belaevski edited comment on RF-9163 at 11/2/10 1:48 PM: ------------------------------------------------------------- Some notes for M4: Updated push implementation requires connection to JMS server. I've done development/testing with JBoss HornetQ. Also implementation is based on Atmosphere framework (https://atmosphere.dev.java.net/). web.xml configuration options: - org.richfaces.push.jms.connectionFactory ("/ConnectionFactory" by default) - org.richfaces.push.jms.topicsNamespace ("/topic" by default) - org.richfaces.push.jms.connectionUsername (empty string by default) - org.richfaces.push.jms.connectionPassword (empty string by default) Also org.richfaces.webapp.PushFilter should be configured and attached to FacesServlet. "topicsNamespace" is used as a root name from which all topics are resolved: i.e. 'chat' topic by default will be looked up via "/topics/chat" JNDI name. Application topics should be created/configured via TopicsContext - see demo.TopicsInitializer for example. Currently, message data serializer can be set and listener for users' connection added. Push component have the following push-specific attributes: - address - name of topic or subtopic in the following formats: address="information" address="weather@chatBus" where 'information', 'chatBus' are names of JMS topics and 'weather' is a name of one of the subtopics that will share the same 'chatBus' JMS topic. - ondatavailable - supports 'dataavailable' behavior event, allows to define handler for pushed data - onerror - supports 'error' behavior event, allows to define handler for erroneous states If there are several push components on the same page they are all exploiting single connection to the server. Messages can be pushed via TopicsContext/Topic or via directly sending to JMS bus. was (Author: nbelaevski): Some notes for M4: Updated push implementation requires connection to JMS server. I've done development/testing with JBoss HornetQ. web.xml configuration options: - org.richfaces.push.jms.connectionFactory ("/ConnectionFactory" by default) - org.richfaces.push.jms.topicsNamespace ("/topic" by default) - org.richfaces.push.jms.connectionUsername (empty string by default) - org.richfaces.push.jms.connectionPassword (empty string by default) Also org.richfaces.webapp.PushFilter should be configured and attached to FacesServlet. "topicsNamespace" is used as a root name from which all topics are resolved: i.e. 'chat' topic by default will be looked up via "/topics/chat" JNDI name. Application topics should be created/configured via TopicsContext - see demo.TopicsInitializer for example. Currently, message data serializer can be set and listener for users' connection added. Push component have the following push-specific attributes: - address - name of topic or subtopic in the following formats: address="information" address="weather@chatBus" where 'information', 'chatBus' are names of JMS topics and 'weather' is a name of one of the subtopics that will share the same 'chatBus' JMS topic. - ondatavailable - supports 'dataavailable' behavior event, allows to define handler for pushed data - onerror - supports 'error' behavior event, allows to define handler for erroneous states If there are several push components on the same page they are all exploiting single connection to the server. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-9163?page=com.atlassian.jira.plugin.sy... ] Nick Belaevski updated RF-9163: ------------------------------- Parent: (was: RF-7817) Issue Type: Task (was: Sub-task) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira