December 2008 - seam-issues - Jboss List Archives

[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, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2855) Reply link in email notifications to seam-forums@lists.jboss.org not opening reply box

by Pete Muir (JIRA)

Reply link in email notifications to seam-forums(a)lists.jboss.org not opening reply box -------------------------------------------------------------------------------------- Key: JBSEAM-2855 URL: http://jira.jboss.com/jira/browse/JBSEAM-2855 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Pete Muir Assigned To: Christian Bauer Priority: Minor -- 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, 7 months

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2627) Use labels to improve usability of seamframework.org

by Keith Naas (JIRA)

Use labels to improve usability of seamframework.org ---------------------------------------------------- Key: JBSEAM-2627 URL: http://jira.jboss.com/jira/browse/JBSEAM-2627 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Environment: Firefox 2.0.0.12 Reporter: Keith Naas Assigned To: Christian Bauer Priority: Trivial Use label tags to improve the usability of the forms, especially for checkboxes/radiobuttons. The "Exact Phrase" checkbox on the find screen and the Account preferences are a few examples. I would be happy to make the changes necessary for this. -- 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, 7 months

3
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2980) Unify and extend wiki URL rendering

by Christian Bauer (JIRA)

Unify and extend wiki URL rendering ----------------------------------- Key: JBSEAM-2980 URL: http://jira.jboss.com/jira/browse/JBSEAM-2980 Project: Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Although we have WikiUrlRenderer, it's not powerful enough and it isn't used everywhere. -- 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, 7 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2611) <s:prefocus/> tag for setting focus on page entry

by Nicklas Karlsson (JIRA)

<s:prefocus/> tag for setting focus on page entry ------------------------------------------------- Key: JBSEAM-2611 URL: http://jira.jboss.com/jira/browse/JBSEAM-2611 Project: JBoss Seam Issue Type: Feature Request Components: JSF Controls Reporter: Nicklas Karlsson It might be convenient to have a <s:prefocus/> tag that could be e.g. nested inside an inputText field you would like to have focused when the page is loaded. It could be implemented with a simple document.getElementById('...').focus(); (or other browser-compatible code) at the end of the page. -- 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, 7 months

6
37
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3844) Hot deployment : You are trying to use a connection factory that has been shut down

by Bernard Labno (JIRA)

Hot deployment : You are trying to use a connection factory that has been shut down ----------------------------------------------------------------------------------- Key: JBSEAM-3844 URL: https://jira.jboss.org/jira/browse/JBSEAM-3844 Project: Seam Issue Type: Bug Components: Hot Deploy Affects Versions: 2.1.1.CR2 Reporter: Bernard Labno When using war exploded deployment and invoke "explode" ant target to hot deploy components (even if there is no changes) I get this error : Caused by: javax.resource.ResourceException: You are trying to use a connection factory that has been shut down: ManagedConnectionFactory is null. As I've inspected the problem is that javax.persistence.EntityManagerFactory changes and org.jboss.seam.persistence.EntityManagerFactory does not get reinitiated on hot deployment. 2008-12-15 13:53:18,326 INFO ConnectionFactoryBindingService - Unbound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' from JNDI name 'java:seamcourseDatasource' 2008-12-15 13:53:18,412 INFO ConnectionFactoryBindingService - Bound ConnectionManager 'jboss.jca:service=DataSourceBinding,name=seamcourseDatasource' to JNDI name 'java:seamcourseDatasource' I think that Initialization.redeploy method needs to be updated to reinitialize all EntityManagerFactory instances but I'm not sure and need confirmation from experienced seam dev. -- 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, 7 months

8
14
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3838) Permission check fails on collections that contain lazily initialized entities

by Georges Berscheid (JIRA)

Permission check fails on collections that contain lazily initialized entities ------------------------------------------------------------------------------ Key: JBSEAM-3838 URL: https://jira.jboss.org/jira/browse/JBSEAM-3838 Project: Seam Issue Type: Bug Components: Security Affects Versions: 2.1.0.SP1 Reporter: Georges Berscheid org.jboss.seam.security.permission.PermissionMapper.filterByPermission:94 The permission filter checks if the target of the check is of the same class as the target of the permission. If the collection-parameter is the result of a javax.persistence.Query.getResultList() (using Hibernate), and one of the entities returned in that List had previously been lazily fetched (e.g. as part of an entity relationship) this check will fail. Hibernate probably does some optimization and knows that it had fetched this entity before, and hence puts the lazy proxy into the result list. The proxy's class name is something like Entity_$$_javassist_12 which won't match the class name of the permission target (Entity). The only work-around I could find for this is to eagerly fetch all entity relationships that are affected by this behavior, which kills the performance of the application. -- 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, 8 months

7
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3778) MDB - IllegalStateException: No event context active

by John Gilbert (JIRA)

MDB - IllegalStateException: No event context active ---------------------------------------------------- Key: JBSEAM-3778 URL: https://jira.jboss.org/jira/browse/JBSEAM-3778 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.GA Reporter: John Gilbert ManagedPersistenceContext throws "IllegalStateException: No event context active" after MDB closes contexts. see - http://seamframework.org/Community/MDBIllegalStateExceptionNoEventContext... -- 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, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1246) pages.xml fails to load during application startup

by Mike Quilleash (JIRA)

pages.xml fails to load during application startup -------------------------------------------------- Key: JBSEAM-1246 URL: http://jira.jboss.com/jira/browse/JBSEAM-1246 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Any Reporter: Mike Quilleash pages.xml will not be found by the resource loader when the Pages component is @Created during startup ie outside a JSF request. One of my components that queries the Pages component is causing the component to be created and look for its pages outside a JSF request. The only resource lookup that can succeed for something in WEB-INF is the ExternalContext.getResource() but this is not available outside a JSF request. Using ServletContext.getResource() will work instead however this is not portable to Portlets etc. -- 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, 8 months

6
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3752) Allow to kill all conversation with the "s:conversationPropagation" tag

by Denis Forveille (JIRA)

Allow to kill all conversation with the "s:conversationPropagation" tag ------------------------------------------------------------------------ Key: JBSEAM-3752 URL: https://jira.jboss.org/jira/browse/JBSEAM-3752 Project: Seam Issue Type: Feature Request Affects Versions: 2.1.1.CR1 Reporter: Denis Forveille Add the possibility to kill the conversation stack with the "s:conversationPropagation" is missing. It is possible to do that with annotation (@End(root=true),via the API or with pages.xml, but not with the "s:conversationPropagation" annotation maybe with <s:conversationPropagation type="endAll" /> ? -- 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, 8 months

5
21
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008