December 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3680) Locking issue for ConversationEntry when redirecting at ExceptionFilter

by Hiroyuki Wada (JIRA)

Locking issue for ConversationEntry when redirecting at ExceptionFilter ----------------------------------------------------------------------- Key: JBSEAM-3680 URL: https://jira.jboss.org/jira/browse/JBSEAM-3680 Project: Seam Issue Type: Bug Components: Exception Handling Affects Versions: 2.1.0.SP1 Environment: Windows XP SP2, JBoss EAP 4.3 Reporter: Hiroyuki Wada Priority: Critical When redirecting at ExceptionFilter, it seems that the ConversationEntry lock is not released. Therefore, if next request is processed by the another thread, the thread wait for until unlocking. This results in the user being redirected to the no-conversation-view-id after the concurrent-request-timeout expires. I checked the Seam 2.0.2.SP1 source. It seems that the unlocking process for ConversationEntry is skipped when Exception is thrown from JSF Action that invoked in INVOKE_APPLICATION phase. When Exception is not thrown, the lock is release after INVOKE_APPLICATION phase. (at method calling "afterResponseComplete(facesContext)" at 249 line of SeamPhaseListener.java) When Exception is thrown, this method is not called because of the result of FacesContext#getResponseComplete() is FALSE. -- 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, 8 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3751) Verify validate.xml validates xsd's and if needed update it so that is does

by Jay Balunas (JIRA)

Verify validate.xml validates xsd's and if needed update it so that is does --------------------------------------------------------------------------- Key: JBSEAM-3751 URL: https://jira.jboss.org/jira/browse/JBSEAM-3751 Project: Seam Issue Type: Task Components: Build, Test Harness Affects Versions: 2.1.1.CR1 Reporter: Jay Balunas Assignee: Jozef Hartinger Fix For: 2.1.1.CR2 There was an issue with the validate.xml setting in the testsuite for the release testing of 2.1.1.CR1. We need to verify that this is fixed and that it will validate and test the various xsd's and other xml files. If it does not we need to update it so that is does. -- 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, 8 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1590) Problem when deploying seam application as directory deployment in glassfish

by ivica c (JIRA)

Problem when deploying seam application as directory deployment in glassfish ---------------------------------------------------------------------------- Key: JBSEAM-1590 URL: http://jira.jboss.com/jira/browse/JBSEAM-1590 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Environment: glassfish V2 build 53 seam 2.0.0 beta1 jdk 1.6.0 update1 netbeans 6 daily build Reporter: ivica c Fix For: 2.0.0.CR1 Problem occurs when deploying seam application as directory deployment in glassfish. I am getting this exception: Exception occured in J2EEC Phasejava.lang.IllegalArgumentException: Invalid ejb jar [lib/jboss-seam.jar]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar. com.sun.enterprise.deployment.backend.IASDeploymentException: Error loading deployment descriptors for module [ctg-main] -- Invalid ejb jar [lib/jboss-seam.jar]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar. at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:388) at com.sun.enterprise.deployment.backend.AppDeployerBase.loadDescriptors(AppDeployerBase.java:358) at com.sun.enterprise.deployment.backend.AppDeployer.deploy(AppDeployer.java:226) at com.sun.enterprise.deployment.backend.AppDeployer.doRequestFinish(AppDeployer.java:148) at com.sun.enterprise.deployment.phasing.J2EECPhase.runPhase(J2EECPhase.java:191) at com.sun.enterprise.deployment.phasing.DeploymentPhase.executePhase(DeploymentPhase.java:108) at com.sun.enterprise.deployment.phasing.PEDeploymentService.executePhases(PEDeploymentService.java:905) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:279) at com.sun.enterprise.deployment.phasing.PEDeploymentService.deploy(PEDeploymentService.java:774) at com.sun.enterprise.management.deploy.DeployThread.deploy(DeployThread.java:187) at com.sun.enterprise.management.deploy.DeployThread.run(DeployThread.java:223) Caused by: java.lang.IllegalArgumentException: Invalid ejb jar [lib/jboss-seam.jar]: it contains zero ejb. Note: 1. A valid ejb jar requires at least one session, entity (1.x/2.x style), or message driven bean. 2. EJB3+ entity beans (@Entity) are POJOs and please package them as library jar. at com.sun.enterprise.deployment.util.EjbBundleValidator.accept(EjbBundleValidator.java:95) at com.sun.enterprise.deployment.util.ApplicationValidator.accept(ApplicationValidator.java:82) at com.sun.enterprise.deployment.EjbBundleDescriptor.visit(EjbBundleDescriptor.java:729) at com.sun.enterprise.deployment.Application.visit(Application.java:1754) at com.sun.enterprise.deployment.archivist.ApplicationArchivist.validate(ApplicationArchivist.java:470) at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:790) at com.sun.enterprise.deployment.archivist.ApplicationArchivist.openArchive(ApplicationArchivist.java:744) at com.sun.enterprise.deployment.backend.Deployer.loadDescriptors(Deployer.java:349) ... 10 more but when I deploy as norma arhive(when upload it) everything works fine. -- 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

15 years, 8 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3398) To extend seam's Pages component to override "pages.xml" loading strategy

by Alex Sun (JIRA)

To extend seam's Pages component to override "pages.xml" loading strategy ------------------------------------------------------------------------- Key: JBSEAM-3398 URL: https://jira.jboss.org/jira/browse/JBSEAM-3398 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.BETA1 Reporter: Alex Sun Fix For: 2.1.0.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, 8 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3466) @UserRoles only works when using one ManyToMany-Relation instead of two OneToMany-Relations

by nimo stephan (JIRA)

@UserRoles only works when using one ManyToMany-Relation instead of two OneToMany-Relations ------------------------------------------------------------------------------------------- Key: JBSEAM-3466 URL: https://jira.jboss.org/jira/browse/JBSEAM-3466 Project: Seam Issue Type: Quality Risk Components: Security Affects Versions: 2.1.0.BETA1 Environment: EJB 3.0, JBOSS 4.2, SEAM 2.1, RichFaces (3.2) Reporter: nimo stephan Priority: Minor @UserRoles only works in ManyToMany-Relation. If we provide two @OneToMany-relations instead of one @ManyToMany, then @UserRoles does not work! The UserRolesProperty returns the UserRoles-Instance instead of the Roles-Instance. However, when having additional attributes in UserRoles we should better use two @OneToMany-Relations - but then @UserRoles does not work. As Shane said: "I don't think that we currently support cross reference tables in this manner, although we should. " Yes, it would be fine:-) thanks. -- 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, 8 months

4
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3117) Configure label direction of chart's domain axis

by Alexander Kunkel (JIRA)

Configure label direction of chart's domain axis ------------------------------------------------ Key: JBSEAM-3117 URL: http://jira.jboss.com/jira/browse/JBSEAM-3117 Project: Seam Issue Type: Feature Request Components: PDF Reporter: Alexander Kunkel -- 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

15 years, 9 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3825) <script> not allowed in seam pageflow xsd

by Samuel Mendenhall (JIRA)

15 years, 9 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2242) null injected values(synchronization problem?)

by Andrei Gh (JIRA)

null injected values(synchronization problem?) ---------------------------------------------- Key: JBSEAM-2242 URL: http://jira.jboss.com/jira/browse/JBSEAM-2242 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.GA, 1.2.1.GA Reporter: Andrei Gh am inside a long running conversation and I have a search page with a search button that triggers myBean.search(). myBean has several conversation scoped variables, injected with @In. While the search page is rendered in the browser, before the render finishes, I click the search button that calls method myBean.search() on server. The problem is that injected values are null. The problem only occurs when I call bean method(by clicking a button), BEFORE the page that contains that button finishes to render in the browser. -- 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

15 years, 9 months

5
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3760) Add JEE5 example to functional testing (also verify recent changes)

by Dan Allen (JIRA)

Add JEE5 example to functional testing (also verify recent changes) ------------------------------------------------------------------- Key: JBSEAM-3760 URL: https://jira.jboss.org/jira/browse/JBSEAM-3760 Project: Seam Issue Type: Task Components: Test Harness Affects Versions: 2.1.1.CR1 Reporter: Dan Allen Assignee: Jozef Hartinger Fix For: 2.1.1.GA The JEE5 test is very important because it validates that Seam runs using standard Java EE 5 resources (such as EJB references). It should be validated on JBoss 5 AS (and possibly GlassFish). Changes were made to it recently to further test the integration, so it should be verified anyway. -- 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, 9 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3820) JEE5 booking example fails on deploy

by Jozef Hartinger (JIRA)

JEE5 booking example fails on deploy ------------------------------------ Key: JBSEAM-3820 URL: https://jira.jboss.org/jira/browse/JBSEAM-3820 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.1.CR2 Environment: JDK 5 JBoss AS 5.0.0.GA Reporter: Jozef Hartinger Fix For: 2.1.2.CR1 When the example is being deployed I can see errors in server log. Despite these errors the main page loads however when I try to login the application fails because it is not able to create an instance of authenticator component. See jee5-as5-jdk5.txt for deployment errors and jee5-as5-jdk5-login.txt for the exception during login attempt. -- 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, 9 months

3
9
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008