[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2722) Wiki plugin metadata
by Christian Bauer (JIRA)
Wiki plugin metadata
--------------------
Key: JBSEAM-2722
URL: http://jira.jboss.com/jira/browse/JBSEAM-2722
Project: JBoss Seam
Issue Type: Task
Components: Wiki
Reporter: Christian Bauer
Assigned To: Christian Bauer
Priority: Blocker
Plugins/macros need metadata, some random ideas:
protected String[] skins = {"d", "m"}
protected long accessLevel = 0;
protected boolean documentDiscriminator = false;
protected boolean reentrant = true;
protected boolean renderedOnce = false;
protected boolean affectsRenderingOnly = true;
protected boolean appliesToHeader = false;
protected boolean appliesToContent = true;
protected boolean appliesToFooter = false;
protected boolean displayedInPreview = true;
createMethodBuildTime
createMethodRenderTime
--
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, 10 months
[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, 10 months