December 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4474) Hibernate class org.hibernate.lob.ReaderInputStream is now org.hibernate.engine.jdbc.ReaderInputStream and that breaks Seam

by Scott Marlow (JIRA)

Hibernate class org.hibernate.lob.ReaderInputStream is now org.hibernate.engine.jdbc.ReaderInputStream and that breaks Seam --------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4474 URL: https://jira.jboss.org/jira/browse/JBSEAM-4474 Project: Seam Issue Type: Bug Affects Versions: 2.1.1.GA Reporter: Scott Marlow Priority: Blocker Jira JBAS-7440 is about a JBoss app server 6.0.0.M1 unit test failure. The failure is showing that the Seam and Hibernate integration is broken. This problem occurred when we upgraded AS (5_x branch) to the recent Hibernate 3.5.0-Beta-2. Hibernate 3.5.0-Beta-2 contains a fix for HHH-2412 (Support for JDBC4), which involved repackaging org.hibernate.lob.ReaderInputStream to now be org.hibernate.engine.jdbc.ReaderInputStream. However, Seam has a dependency on the old package name org.hibernate.lob.ReaderInputStream. This package name change results in an app server integration test for Seam failure (error = java.lang.NoClassDefFoundError: org/hibernate/lob/ReaderInputStream). -- 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
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4037) Define required SPI for RESTEasy integration

by Christian Bauer (JIRA)

Define required SPI for RESTEasy integration -------------------------------------------- Key: JBSEAM-4037 URL: https://jira.jboss.org/jira/browse/JBSEAM-4037 Project: Seam Issue Type: Task Components: WS Reporter: Christian Bauer Assignee: Christian Bauer Priority: Critical This issue is a compilation of other issues that help us summarize and define the SPI we need from RESTEasy for Seam integration. -- 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

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4191) TransactionsAttribute.SUPPORTS in EjbSynchronisations

by Wolfgang Schwach (JIRA)

TransactionsAttribute.SUPPORTS in EjbSynchronisations ----------------------------------------------------- Key: JBSEAM-4191 URL: https://jira.jboss.org/jira/browse/JBSEAM-4191 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.2.CR2 Environment: Affects all versions. Reporter: Wolfgang Schwach The class org.jboss.seam.transaction.EjbSynchronizations violates the Java-Specs. As stated in http://java.sun.com/blueprints/guidelines/designing_enterprise_applicatio... classes that implement SessionSynchronization may not have the TransactionsAttribute TransactionAttributeType.SUPPORTS. -- 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-1206) improve i18n in seam-gen

by Pierre Raoul (JIRA)

improve i18n in seam-gen ------------------------ Key: JBSEAM-1206 URL: http://jira.jboss.com/jira/browse/JBSEAM-1206 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 1.2.1.GA Reporter: Pierre Raoul It would be great that seam-gen will generate crud pages and classes for an existing Entity class: - with all the literals replaced with #{messages['key']} - and i18n default messages generated Herewith files of a draft version. I used the jpaconfiguration propositions from JBSEAM-843. It works under Eclipse: the target "updatecrud" in the project build.xml can be run from Eclipse. Nota: to translated Enum type, test of this type had to be added. I did it through file inclusion. So it can be used with any other project specific types, e.g. in the attached zip with joda-time type. -- 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

3
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4165) Document includePageParams attribute

by Samuel Mendenhall (JIRA)

Document includePageParams attribute ------------------------------------ Key: JBSEAM-4165 URL: https://jira.jboss.org/jira/browse/JBSEAM-4165 Project: Seam Issue Type: Task Components: Documentation Issues Reporter: Samuel Mendenhall Assignee: Shane Bryzak Priority: Minor Per subject, the includePageParams should be documented, not currently in there that I see. -- 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1878) Validation for Hibernate Class Level Validators

by Martin Hoffmann (JIRA)

Validation for Hibernate Class Level Validators ----------------------------------------------- Key: JBSEAM-1878 URL: http://jira.jboss.com/jira/browse/JBSEAM-1878 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.2.1.GA Reporter: Martin Hoffmann Priority: Optional A JSF Component for Validation of Hibernate Class Validators. This Component should be used like s:validateAll Tag. Currently SEAM throws an exception in case of a not validating class validator. -- 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

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4186) HTTP caching for SeamResourceServlet resources

by Christian Bauer (JIRA)

HTTP caching for SeamResourceServlet resources ---------------------------------------------- Key: JBSEAM-4186 URL: https://jira.jboss.org/jira/browse/JBSEAM-4186 Project: Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assignee: Christian Bauer Priority: Minor This affects built-in Seam stuff like the remote.js that is always delivered with 200 OK and can be quite large. We need to explore how/when we can send 304. I've assigned this to the 'wiki' component because I want to try different solutions there first. -- 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
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2761) Verify other JPA providers can used by seam applications.

by Jay Balunas (JIRA)

Verify other JPA providers can used by seam applications. --------------------------------------------------------- Key: JBSEAM-2761 URL: http://jira.jboss.com/jira/browse/JBSEAM-2761 Project: JBoss Seam Issue Type: Task Components: Examples, Test Harness Reporter: Jay Balunas Assigned To: Jay Balunas Priority: Minor This would entail replacing Hibernate JPA with another JPA implementation such as OpenJPA. A subset of examples should be modified, tested and if appropriate documented so work with alternate JPA providers. Examples: Booking DVD TBD -- 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

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4312) Exception while checking out transaction causing infinite loop trying to render error page

by Matthew Lieder (JIRA)

Exception while checking out transaction causing infinite loop trying to render error page ------------------------------------------------------------------------------------------ Key: JBSEAM-4312 URL: https://jira.jboss.org/jira/browse/JBSEAM-4312 Project: Seam Issue Type: Bug Components: Exception Handling Affects Versions: 2.2.0.CR1 Environment: java 6, Tomcat 6, c3p0 0.9.2 Reporter: Matthew Lieder We have the following pretty typical exception config in our pages.xml: <exception> <end-conversation /> <redirect view-id="/seam/error.xhtml"> <message severity="error">#{org.jboss.seam.handledException}</message> </redirect> </exception> That works great, except when our database server is down. In that case a com.mchange.v2.resourcepool.TimeoutException is thrown and the exception handler is properly called, but Seam then tries to access the database again when rendering the error page and thus the cycle repeats ad infinitum. I don't believe this is specific to the TimeoutException exception or even to c3p0; this seems to be a pretty general problem. There needs to be some way to prevent Seam from trying to start a transaction while rendering the error page, either always or maybe by an attribute on the <exception> tag. -- 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-3525) Analyse JNDI lookups in an EJB app (Booking) and a EntityHome based app (seam-gen)

by Pete Muir (JIRA)

Analyse JNDI lookups in an EJB app (Booking) and a EntityHome based app (seam-gen) ---------------------------------------------------------------------------------- Key: JBSEAM-3525 URL: https://jira.jboss.org/jira/browse/JBSEAM-3525 Project: Seam Issue Type: Task Affects Versions: 2.1.0.BETA1 Reporter: Pete Muir Assignee: Jay Balunas Fix For: 2.1.1.CR1 -- 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
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2009