[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
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4036) Wicket Example - Missing jars in tomcat.deploy ant task
by Cruz Fernandez (JIRA)
Wicket Example - Missing jars in tomcat.deploy ant task
-------------------------------------------------------
Key: JBSEAM-4036
URL: https://jira.jboss.org/jira/browse/JBSEAM-4036
Project: Seam
Issue Type: Patch
Components: Examples
Affects Versions: 2.1.1.GA
Environment: All OS, Tomcat 6.0 with Embedded Jboss 3
Reporter: Cruz Fernandez
Priority: Minor
Fix For: 2.1.1.GA
The war generated for Tomcat misses wicket Jars, (like the generated ear has) in the wicket example. The command
ant tomcat.deploy
generates an incorrect war.
Adding this lines to build.xml fixes it:
Index: seam/examples/build.xml
===================================================================
--- seam/examples/build.xml (revisión: 10203)
+++ seam/examples/build.xml (copia de trabajo)
@@ -885,6 +885,9 @@
<fileset refid="cache.jar" />
<fileset refid="jbpm.jar" />
<fileset refid="tomcat.jbpm.jar" />
+ <fileset refid="wicket-extensions.jar" />
+ <fileset refid="wicket-datetime.jar" />
+ <fileset refid="seam.wicket.jar" />
<fileset refid="spring.jar" />
<fileset refid="gwt.jar" />
<fileset refid="openid.jar" />
--
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
[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, 11 months
[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4316) Classloader cannot find XML files in multiple WARs
by Reind D (JIRA)
Classloader cannot find XML files in multiple WARs
--------------------------------------------------
Key: JBSEAM-4316
URL: https://jira.jboss.org/jira/browse/JBSEAM-4316
Project: Seam
Issue Type: Bug
Components: Core
Affects Versions: 2.2.0.CR1
Environment: JBoss AS 5.0.0.GA. Seam 2.2 r11299
Reporter: Reind D
I have an EAR that contains multiple WAR files. The first webapp to be accessed works fine. Any web request to the 2nd WAR to be accessed causes the following error:
WARN [VFSScanner] Error handling item 'login/index.page.xml': java.lang.NullPointerException: Cannot find URL from classLoader for login/index.page.xml, loading from org.jboss.web.tomcat.service.WebCtxLoader$ENCLoader@1ed964f
FileDescriptor.java calls:
Resources.getResource(name, ServletLifecycle.getServletContext());
Which returns a static reference to the ServletContext which is overwritten by the last webapp to be initialized.
private static ServletContext servletContext;
public static ServletContext getServletContext()
{
//don't throw an exception if null, because of unit tests
return servletContext;
}
The 2nd webapp to be initialized will have a reference to the first webapp's ServletContext.
--
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