January 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3793) Null pointer dereference of name in org.jboss.seam.security.permission.ClassIdentifierStrategy.getIdentifierName(Class)

by Francisco Jose Peredo Noguez (JIRA)

Null pointer dereference of name in org.jboss.seam.security.permission.ClassIdentifierStrategy.getIdentifierName(Class) ----------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3793 URL: https://jira.jboss.org/jira/browse/JBSEAM-3793 Project: Seam Issue Type: Bug Reporter: Francisco Jose Peredo Noguez Null pointer dereference of name in org.jboss.seam.security.permission.ClassIdentifierStrategy.getIdentifierName(Class) String name = null; if (cls.isAnnotationPresent(Identifier.class)) { Identifier identifier = (Identifier) cls.getAnnotation(Identifier.class); if (identifier.name() != null && !"".equals(name.trim())) { name = identifier.name(); } } -- 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, 10 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3790) Missing nullcheck in org.jboss.seam.core.Validators.equals

by Francisco Jose Peredo Noguez (JIRA)

Missing nullcheck in org.jboss.seam.core.Validators.equals ---------------------------------------------------------- Key: JBSEAM-3790 URL: https://jira.jboss.org/jira/browse/JBSEAM-3790 Project: Seam Issue Type: Bug Reporter: Francisco Jose Peredo Noguez In @Override public boolean equals(Object other) { Key key = (Key) other; return key.validatableClass.equals(validatableClass) && key.locale.equals(locale); } If the parameter other is null, the line return key.validatableClass... will crash with null pointer exception. -- 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, 10 months

4
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3028) add ContainerManagedPersistenceContext

by Dan Allen (JIRA)

add ContainerManagedPersistenceContext -------------------------------------- Key: JBSEAM-3028 URL: http://jira.jboss.com/jira/browse/JBSEAM-3028 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.A1, 2.0.2.GA Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.1.0.GA Attachments: JBSEAM-3028-v1.txt Perhaps this is silly, perhaps not. I have developed a wrapper around a container-managed persistence manager, avoiding the need to have to lookup the EntityManagerFactory in JNDI. The main limitation here is that you cannot use this with EJB components, so it is really just a convenience of configuration if the Java EE application server happens to offer the ability to create an EntityManager for you. This also only works with the default persistence unit. -- 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, 10 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3804) Need to clean examples prior to deployment during functional testing

by Jay Balunas (JIRA)

Need to clean examples prior to deployment during functional testing -------------------------------------------------------------------- Key: JBSEAM-3804 URL: https://jira.jboss.org/jira/browse/JBSEAM-3804 Project: Seam Issue Type: Task Components: Test Harness Affects Versions: 2.1.1.CR1 Reporter: Jay Balunas Assignee: Jozef Hartinger Fix For: 2.1.2.CR1 When deploying example in the functional tests we need to clean the target example prior to deployment. The problem comes if you attempt to deploy some examples to tomcat after the example had been built for jboss. -- 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3910) columns to process for workbook generation should be custumizable, as frontend and sheet might differ

by Rene FelgentrÃ¤ger (JIRA)

columns to process for workbook generation should be custumizable, as frontend and sheet might differ ----------------------------------------------------------------------------------------------------- Key: JBSEAM-3910 URL: https://jira.jboss.org/jira/browse/JBSEAM-3910 Project: Seam Issue Type: Feature Request Components: Excel Affects Versions: 2.1.1.GA Reporter: Rene FelgentrÃ¤ger So far, the excel-exporter tries to generate a workbook by copying all columns of the datatable ignoring the rendered attribute. Furthermore, it should be possible to ignore "action/details" columns, as they are useless in an excel-sheet -- 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, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3057) DataModelSelection and sortBy Not Functional

by Stefano Zaccaria (JIRA)

DataModelSelection and sortBy Not Functional -------------------------------------------- Key: JBSEAM-3057 URL: http://jira.jboss.com/jira/browse/JBSEAM-3057 Project: Seam Issue Type: Bug Components: JSF Integration Affects Versions: 2.0.2.SP1 Reporter: Stefano Zaccaria Moreover, in my webapp where I use a rich:dataTable with a columns and one rich:toolTip for any columns the tooltip not work -- 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, 10 months

4
3
0 / 0

[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, 10 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, 10 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, 10 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, 10 months

3
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues January 2009