January 2010 - 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

16 years, 2 months

2
1
0 / 0

[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

16 years, 2 months

3
3
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

16 years, 2 months

2
3
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

16 years, 2 months

6
37
0 / 0

[JBoss JIRA] Created: (JBSEAM-4505) SAX error when parsing Seam 2.1 s.tld - org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'description'.

by Ondrej Žižka (JIRA)

SAX error when parsing Seam 2.1 s.tld - org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'description'. -------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4505 URL: https://jira.jboss.org/jira/browse/JBSEAM-4505 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.SP1 Environment: AS 6 trunk, EmbJopr Reporter: Ondrej Žižka Caught when starting Seam on AS 6 trunk. org.xml.sax.SAXException: cvc-complex-type.2.4.a: Invalid content was found starting with element 'description'. One of '{"http://java.sun.com/xml/ns/javaee":type, "http://java.sun.com/xml/ns/javaee":deferred-value, "http://java.sun.com/xml/ns/javaee":deferred-method}' is expected. @ vfszip:/home/ondra/work/JOPRembedded/AS-svn-trunk/build/output/jboss-6.0.0-SNAPSHOT/server/default/deploy/jbas5-admin-console/WEB-INF/lib/jboss-seam-ui-2.1.0.SP1.jar/META-INF/s.tld[2205,18] at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$MetaDataErrorHandler.error(SaxJBossXBParser.java:426) at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source) at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source) at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source) at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source) at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source) at org.apache.xerces.parsers.XMLParser.parse(Unknown Source) at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Source) at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBParser.java:199) ... 38 more -- 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

16 years, 2 months

4
13
0 / 0

[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

16 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBSEAM-4499) Improve wiki data model/schema

by Christian Bauer (JIRA)

Improve wiki data model/schema ------------------------------ Key: JBSEAM-4499 URL: https://jira.jboss.org/jira/browse/JBSEAM-4499 Project: Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assignee: Christian Bauer Motivation: The current data model based on nested sets has few advantages compared to a traditional schema. It complicates ad-hoc queries and it is more difficult to understand. The locking requirements of the nested set approach are in conflict with stateful persistence context management and bugs are extremely hard to detect and fix. Also, some of the problematic query performance we observed might be related to the nested set schema, however, that is not clear at this point as alternative schemas have not been compared with the same queries. Goal: A simpler schema and removal of all query performance bottlenecks. Steps: 1. Create a dummy traditional schema that reflects the domain and create dummy data (Benerator). 2. Write and analyze the most costly queries against that schema. 3. Once proven that the nested set schema is indeed the cause of these performance issues, replace the nested set schema with the traditional schema and write data migration scripts. 4. Consider replacing the nested set schema anyway, for reasons other than performance (simplicity, bugfixing, locking problems). -- 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

16 years, 2 months

1
2
0 / 0

[JBoss JIRA] Created: (JBSEAM-4498) Upgrade Hibernate libs in wiki

by Christian Bauer (JIRA)

Upgrade Hibernate libs in wiki ------------------------------ Key: JBSEAM-4498 URL: https://jira.jboss.org/jira/browse/JBSEAM-4498 Project: Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assignee: Christian Bauer Upgrade to latest Hibernate (3.5) and especially Hibernate Search to a) utilize the new mass indexing API and b) resolve the severe index-out-of-sync problems we had for years (assuming that it was fixed by coincidence in a newer version of HS). -- 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

16 years, 2 months

1
4
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

16 years, 2 months

8
14
0 / 0

[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

16 years, 2 months

4
16
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2010