seam-issues February 2010

seam-issues@lists.jboss.org

1 participants
313 discussions

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2646) Templates

by Gavin King (JIRA)

Templates --------- Key: JBSEAM-2646 URL: http://jira.jboss.com/jira/browse/JBSEAM-2646 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Gavin King Assigned To: Christian Bauer Allow creation of document templates with defined header/footer, and content sections. Then user can select a template with creating a document. Things like FAQ entries and Forum posts would then use a specific template. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2452) Event logging and notification system

by Christian Bauer (JIRA)

Event logging and notification system ------------------------------------- Key: JBSEAM-2452 URL: http://jira.jboss.com/jira/browse/JBSEAM-2452 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Notification system that supports user personalization: - All actions should throw events with a payload (otherwise context lookup in the generic event listener gets complicated) - A generic event listener is the router for these events, pushes events to more specialized registered listeners (how do we observe all wiki.* events?) - There has to be some asynchronous processing at that point, the generic event listener should not block - Specialized listeners can register on the generic listener based on groups of events, e.g. "Document actions" or "User actions" - The API for the specialized listeners (and how they are registered) has to be usable for the core and plugins In a second step, implement the following core specialized listeners: - access logging (document reads, etc.) - channels bound to user, e.g. a user can build his own channel(s) by picking event groups he is interested in Not sure at this point how notification looks like, that is, how listeners can push notifications (or whole channels?) to some endpoint (e-mail). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4318) SEAM and Richfaces rich:tree component using a dynamic model

by Horacio Vico (JIRA)

SEAM and Richfaces rich:tree component using a dynamic model ------------------------------------------------------------ Key: JBSEAM-4318 URL: https://jira.jboss.org/jira/browse/JBSEAM-4318 Project: Seam Issue Type: Bug Components: JSF Controls, JSF Integration Affects Versions: 2.1.1.GA Environment: Tested on SuSE Linux / OS X Leopard / and Windows using Firefox 3.0 / 3.5. Reporter: Horacio Vico It seems that there is a bug that avoids us to use a Richfaces tree component with a dynamic model (tree is populated dynamically using AJAX). This bug is present when using Richfaces integrated with SEAM. This bug has been reported here: 1) http://seamframework.org/Community/DynamicTreeAndNodeSelectListener 2) http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4131257#4131257 3) http://seamframework.org/Community/TreenodeSelectListenerNeverGetsFired Here there is a really good example on how to implement a dynamic tree using Richfaces: http://random-thoughts-vortex.blogspot.com/2009/05/richfaces-tree-dynamic...) The problem we are experiencing is that the nodeSelectListener method is only fired at the first click on the tree. Child nodes appear but clicking over them produces no action (their childs are not loaded because nodeSelectListener is not fired again). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 11 months

2
3
0 / 0

← Newer
1
...
29
30
31
32
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2010