April 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4002) InstantiationException at Stateful bean (Could not instantiate Seam component)

by Tamas Malatinszki (JIRA)

InstantiationException at Stateful bean (Could not instantiate Seam component) ------------------------------------------------------------------------------ Key: JBSEAM-4002 URL: https://jira.jboss.org/jira/browse/JBSEAM-4002 Project: Seam Issue Type: Bug Components: EJB3 Affects Versions: 2.1.1.GA, 2.1.1.CR2 Environment: JBoss AS 4.2.2 / 4.2.3 / 5.0.0, WinXP / Debian Linux, JD1.6 update 7/11/12 Reporter: Tamas Malatinszki Stateful beans are failing with "Could not instantiate Seam component" error in Seam 2.1.1 CR2 and above. The root cause is "java.lang.ClassNotFoundException: No ClassLoaders found for: <stateful bean>". The application is working fine with Seam 2.1.1 CR1 (and before). See the whole stacktrace and the related code at http://www.seamframework.org/Community/StatefulBeanErrorInSeam211GAAndCR2 -- 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

15 years, 1 month

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4062) Conversation deadlock for seam wicket pages with multiple request targets

by Clint Popetz (JIRA)

Conversation deadlock for seam wicket pages with multiple request targets ------------------------------------------------------------------------- Key: JBSEAM-4062 URL: https://jira.jboss.org/jira/browse/JBSEAM-4062 Project: Seam Issue Type: Bug Components: Wicket Reporter: Clint Popetz Assignee: Clint Popetz Fix For: 2.2.0.CR1 If onRequestTarget is called multiple times in a given request thread, Manager.restoreConversation() will be called twice, and that class does not defend against this by making the second call a no-op, but instead increments the lock count on the conversation blindly, so when the request returns the conversation will be erroneously left with a lock count of one, and can't be subsequently used. -- 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

15 years, 1 month

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4061) Seam booking example throws NotLoggedInException

by Marek Novotny (JIRA)

Seam booking example throws NotLoggedInException ------------------------------------------------ Key: JBSEAM-4061 URL: https://jira.jboss.org/jira/browse/JBSEAM-4061 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.1.GA Reporter: Marek Novotny Priority: Minor To reproduce: 1.) Log in 2.) Go to change-password-page using Settings link 3.) Click Logout After this NotLoggedInException appears in the server log. See attached stack trace for details. -- 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

15 years, 1 month

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4046) Downloading big files with s:resource is slow

by Stefano Travelli (JIRA)

Downloading big files with s:resource is slow --------------------------------------------- Key: JBSEAM-4046 URL: https://jira.jboss.org/jira/browse/JBSEAM-4046 Project: Seam Issue Type: Bug Components: JSF Controls Affects Versions: 2.1.2.CR1 Reporter: Stefano Travelli The reason is in the way method DocumentStoreUtils.writeStream() moves data between streams, that is one byte at time. -- 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

15 years, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3852) Specifically include "explode" and "deploy" seam-gen testing in release-process.txt

by Jay Balunas (JIRA)

Specifically include "explode" and "deploy" seam-gen testing in release-process.txt ----------------------------------------------------------------------------------- Key: JBSEAM-3852 URL: https://jira.jboss.org/jira/browse/JBSEAM-3852 Project: Seam Issue Type: Task Components: Test Harness Affects Versions: 2.1.1.GA Reporter: Jay Balunas Assignee: Jay Balunas Fix For: 2.1.2.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

15 years, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3867) Automation seam-gen testing of JBSEAM-3866

by Jay Balunas (JIRA)

Automation seam-gen testing of JBSEAM-3866 ------------------------------------------ Key: JBSEAM-3867 URL: https://jira.jboss.org/jira/browse/JBSEAM-3867 Project: Seam Issue Type: Task Components: Test Harness Affects Versions: 2.1.1.GA Reporter: Jay Balunas Assignee: Jay Balunas Fix For: The future When the automation suite for seam-gen is being written we should automate the testing of JBSEAM-3866. -- 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

15 years, 1 month

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4064) Seam eclipse perspective, New seam project, Seam facet, Existing seam runtime not displayed. Exists error when try to newly create it

by Jeff Wexler (JIRA)

Seam eclipse perspective, New seam project, Seam facet, Existing seam runtime not displayed. Exists error when try to newly create it ------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-4064 URL: https://jira.jboss.org/jira/browse/JBSEAM-4064 Project: Seam Issue Type: Bug Components: Tools Affects Versions: 2.1.1.GA Environment: Windows 2003 server, 4GB memory, eclipse-jee-ganymede-SR2-win32.zip, JBossTools-ALL-win32-3.0.0.GA-R200903141626-H5.zip, PostgreSQL 8.3.7 JDBC Driver 8.3-604.jdbc4 Reporter: Jeff Wexler Created a new Seam project. In doing so, added Seam Runtime. Deployed as EAR. After project was created, mistakenly selected BuildAll which built and deployed all projects in the workspace. Subsequently deleted the Seam project created above and deleted the directories for the project on the hard disk. Was able to select the jboss server etc that I had previously created, however, the previously created Seam Runtime in the Seam Facet dialog of the New Seam Project dialog is not displayed. When select the Add button and then select the jboss-seam-1.2.1.GA directory, then the name defaults as jboss-seam-2.1.1.GA which is the name I used previously. This time, unable to select any version other than 1.2. Previously was able to select 2.1. -- 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

15 years, 1 month

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4015) Security Vulnerability in booking example

by Stuart Douglas (JIRA)

Security Vulnerability in booking example ----------------------------------------- Key: JBSEAM-4015 URL: https://jira.jboss.org/jira/browse/JBSEAM-4015 Project: Seam Issue Type: Bug Components: Examples Reporter: Stuart Douglas It is possible to leak details (real name and username) of a previously logged in user to an un-authenticated user in the booking example. This is because the 'user' field on the SLSB authenticator is not cleared on every log in attempt. If an unauthenticated user gets a previously used SLSB then the 'user' field will already be set to another users details, and if their login attempt fails then the other users details will be outjected to the session. If this user then clicks the 'create account' button the username and real name fields will be pre-filled with the other users details. This of course depends on the SLSB pooling mechanism used by the AS, however it is easy to reproduce and it is possible to pull peoples details out of the demo hosted at exadel.com. Anywhere that uses SLSB's and outjection is vulnerable to similar problems unless the outjected field is set to a specific value every time. A framework wide approach to this problem would be to nullify all outjected fields on SLSB's after method invocation. -- 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

15 years, 1 month

2
6
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2009