December 2009 - seam-issues - Jboss List Archives

[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

14 years, 11 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

14 years, 11 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

14 years, 11 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

14 years, 11 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

14 years, 11 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

14 years, 11 months

4
16
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4334) Useless lock in Initialization.redeploy

by Stuart Douglas (JIRA)

Useless lock in Initialization.redeploy --------------------------------------- Key: JBSEAM-4334 URL: https://jira.jboss.org/jira/browse/JBSEAM-4334 Project: Seam Issue Type: Bug Components: Core Reporter: Stuart Douglas Initialization.redeploy has the following bit of code: ReentrantLock lock = new ReentrantLock(); if (lock.tryLock(500, TimeUnit.MILLISECONDS)) This lock does not provide any level of protection, as every thread creates a new lock and then locks it. This will only cause potential problems in debug mode. -- 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

3
3
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, 11 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, 11 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, 11 months

6
7
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009