November 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3089) Provide a list of world time zones

by Dan Allen (JIRA)

Provide a list of world time zones ---------------------------------- Key: JBSEAM-3089 URL: http://jira.jboss.com/jira/browse/JBSEAM-3089 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.A1 Reporter: Dan Allen Priority: Minor Fix For: The future Many projects need to be able to display a list of time zones. However, there is no good way to do this in Java. It would be great if Seam provided a good enough for the common project list in one of the international components. The project could always maintain its own list if this one doesn't suffice. -- 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

16 years, 2 months

4
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3077) org.jboss.seam.handledException results in error "The class 'org.jboss.seam.Namespace' does not have the property 'handledException'" when this variable is not present

by Alex Savitsky (JIRA)

org.jboss.seam.handledException results in error "The class 'org.jboss.seam.Namespace' does not have the property 'handledException'" when this variable is not present ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3077 URL: http://jira.jboss.com/jira/browse/JBSEAM-3077 Project: Seam Issue Type: Bug Reporter: Alex Savitsky This variable (org.jboss.seam.handledException) is normally defined by Seam when an unhandled exception is thrown, and is subsequently displayed on an error page. However, when user refreshes the error page, they would get an error "The class 'org.jboss.seam.Namespace' does not have the property 'handledException'", due to the way Seam evaluates expressions - "org.jboss.seam" evaluates to an instance of Namespace, and "org.jboss.seam.handledException" is interpreted as "property 'handledException' of an object 'org.jboss.seam'". What's worse, there's no way to prevent this error from appearing, as the usual way of checking for variable existence - "empty org.jboss.seam.handledException" wouldn't work here, as it never evaluates to null - it's either there, or throws an error if it's not. -- 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

16 years, 2 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3116) use a transaction failed event rather than message

by Dan Allen (JIRA)

use a transaction failed event rather than message -------------------------------------------------- Key: JBSEAM-3116 URL: http://jira.jboss.com/jira/browse/JBSEAM-3116 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.0.A1 Reporter: Dan Allen Priority: Minor Fix For: 2.1.0.GA A FacesMessage should not be added by the SeamPhaseListener when the transaction fails. Instead, it should raise an event that would be observed by a component named FacesTransactionEvents. That observer would then add the FacesMessage to the response. This allows developers to override the behavior or perhaps add a JSF or log message. @see FacesSecurityEvents -- 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

16 years, 2 months

4
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3172) Shutting down cluster node gracefully, causes NoSuchEJBException on next request

by Nikolay Elenkov (JIRA)

Shutting down cluster node gracefully, causes NoSuchEJBException on next request -------------------------------------------------------------------------------- Key: JBSEAM-3172 URL: https://jira.jboss.org/jira/browse/JBSEAM-3172 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.3.CR1 Environment: OS: Linux (RHEL 5), JBoss 4.2.2, Seam 2.0.3-SNAPSHOT (same for 2.0.2.SP1, 2.0.3.CR1) Reporter: Nikolay Elenkov Application (ear) is deployed to a two node JBoss cluster. Setup: 1. two nodes (node1, node2) 2. load balancing/failover by Apache with mod_jk 3. sticky sessions 4. session replication confirmed to work for http session and SFSB (by JBoss trace log) 5. shared database Steps to reproduce: 1. login to app, go to same page backed by a SFSB, start new conversation 2. enter some data (saved in SFSB fields) 3. stop JBoss on node1 gracefully (shutdown.sh) 4. click submit 5. NoSuchEJBException: "Could not find stateful bean: 4sv1g5o-jqzric-fhyhsk09-1-fhyhunhd-9" The next request, creates a new SFSB/conversation and it works as expected from there. Note that if I kill -s 9 JBoss, SFSB's are not removed and failover works as expected. -- 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

16 years, 2 months

5
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3278) seam-gen generate-ui problem - entity in a different package

by Guido Simone (JIRA)

seam-gen generate-ui problem - entity in a different package ------------------------------------------------------------- Key: JBSEAM-3278 URL: https://jira.jboss.org/jira/browse/JBSEAM-3278 Project: Seam Issue Type: Bug Components: Tools Reporter: Guido Simone Here is an example: The entity class PersonAddress has a ManyToOne relationship with Address which happens to be in a different package. The seam generate-ui command will generate (among other things) an EntityHome class named PersonAddressHome. //================================== // PersonAddress package com.domain.model.person; import com.domain.model.location.Address; @Entity public class PersonAddress { private Address address; private PersonAddressTypeLookup addressTypeLookup; private Person person; @ManyToOne @NotNull public Address getAddress() {return address;} @ManyToOne @NotNull public PersonAddressTypeLookup getAddressTypeLookup() { return addressTypeLookup; } @ManyToOne @NotNull public Person getPerson() {return person;} // setters omitted } which generates: //================================== // PersonAddressHome package com.domain.action; import com.domain.model.person.*; import org.jboss.seam.annotations.In; import org.jboss.seam.annotations.Name; import org.jboss.seam.framework.EntityHome; @Name("personAddressHome") public class PersonAddressHome extends EntityHome<PersonAddress> { // code omitted... public void wire() { getInstance(); Address address = addressHome.getDefinedInstance(); if (address != null) { getInstance().setAddress(address); } PersonAddressTypeLookup addressTypeLookup = addressTypeLookupHome .getDefinedInstance(); if (addressTypeLookup != null) { getInstance().setAddressTypeLookup(addressTypeLookup); } Person person = personHome.getDefinedInstance(); if (person != null) { getInstance().setPerson(person); } } The generated code imports all entities in com.domain.model.person, but does not import anything from com.domain.model.location so the compilation fails in the second line of the wire() method (Address cannot be resolved to a type). -- 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

16 years, 2 months

4
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3030) Don't be so hostile to alternate JPA providers when attempt is made to use manual flush mode

by Dan Allen (JIRA)

Don't be so hostile to alternate JPA providers when attempt is made to use manual flush mode -------------------------------------------------------------------------------------------- Key: JBSEAM-3030 URL: http://jira.jboss.com/jira/browse/JBSEAM-3030 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1, 2.0.2.GA Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.2.SP1, 2.1.0.BETA1 Attachments: JBSEAM-3030-branch20-v1.txt, JBSEAM-3030-trunk-v1.txt Right now, alternate JPA providers (such as TopLink) are *unusable* in Seam. This is because, prior to the render response phase, Seam attempts to put the touched persistence contexts into manual flush mode. This trickles down to a call to setManualFlushMode() on the component returned by PersistenceProvider.instance(). The generic implementation (PersistenceProvider) throws an exception when this method is called. Throwing an exception here is overkill and hostile. I propose a log warning message, which would allow the developer to tune the log settings to hush it, or if they really don't like the log message, they can provide their own implementation. But at least the damn thing will be usable. -- 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

16 years, 2 months

3
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3032) count query used by EntityHome is not compliant JPQL

by Dan Allen (JIRA)

count query used by EntityHome is not compliant JPQL ---------------------------------------------------- Key: JBSEAM-3032 URL: http://jira.jboss.com/jira/browse/JBSEAM-3032 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.0.A1, 2.0.2.GA Reporter: Dan Allen Assigned To: Dan Allen Fix For: 2.0.2.SP1, 2.1.0.BETA1 The count query used by getCountEjbQl() in EntityHome is not compliant JPQL. It should be: select count(Entity) from Entity entity instead of select count(*) from Entity entity Where "entity" is the class name of the entity (for instance, Person). You can test this by using TopLink or OpenJPA. All we need to do is replace the * with the name of the Entity. (We don't even need to fish for the alias used in the query). -- 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

16 years, 2 months

5
18
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3034) EJB Stateless Session Bean Injection using @In Glassfish server

by Senthilkumar Muthusamy (JIRA)

EJB Stateless Session Bean Injection using @In Glassfish server ---------------------------------------------------------------- Key: JBSEAM-3034 URL: http://jira.jboss.com/jira/browse/JBSEAM-3034 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.1.GA Environment: Glassfish Application Server V2ur2 Reporter: Senthilkumar Muthusamy Priority: Critical I have 2 stateless ejbs, from ejb1, i am trying inject ejb2 using @In annotation. I got below exception Caused by: org.jboss.seam.InstantiationException: Could not instantiate Seam component: slave at org.jboss.seam.Component.newInstance(Component.java:1970) at org.jboss.seam.Component.getInstance(Component.java:1873) at org.jboss.seam.Component.getInstance(Component.java:1840) at org.jboss.seam.Component.getInstanceInAllNamespaces(Component.java:2182) at org.jboss.seam.Component.getValueToInject(Component.java:2134) at org.jboss.seam.Component.injectAttributes(Component.java:1598) at org.jboss.seam.Component.inject(Component.java:1416) at org.jboss.seam.core.BijectionInterceptor.aroundInvoke(BijectionInterceptor.java:45) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.core.MethodContextInterceptor.aroundInvoke(MethodContextInterceptor.java:42) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.persistence.EntityManagerProxyInterceptor.aroundInvoke(EntityManagerProxyInterceptor.java:26) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.persistence.HibernateSessionProxyInterceptor.aroundInvoke(HibernateSessionProxyInterceptor.java:27) at org.jboss.seam.intercept.SeamInvocationContext.proceed(SeamInvocationContext.java:68) at org.jboss.seam.intercept.RootInterceptor.invoke(RootInterceptor.java:118) at org.jboss.seam.intercept.SessionBeanInterceptor.aroundInvoke(SessionBeanInterceptor.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at com.sun.ejb.containers.interceptors.AroundInvokeInterceptor.intercept(InterceptorManager.java:579) at com.sun.ejb.containers.interceptors.AroundInvokeChainImpl.invokeNext(InterceptorManager.java:483) at com.sun.ejb.containers.interceptors.InterceptorManager.intercept(InterceptorManager.java:205) at com.sun.ejb.containers.BaseContainer.intercept(BaseContainer.java:3978) at com.sun.ejb.containers.EJBLocalObjectInvocationHandler.invoke(EJBLocalObjectInvocationHandler.java:197) ... 53 more Caused by: javax.naming.NameNotFoundException: No object bound to name java:comp/env/evolve/SlaveBean/local at com.sun.enterprise.naming.NamingManagerImpl.lookup(NamingManagerImpl.java:834) at com.sun.enterprise.naming.java.javaURLContext.lookup(javaURLContext.java:173) at com.sun.enterprise.naming.SerialContext.lookup(SerialContext.java:396) at javax.naming.InitialContext.lookup(InitialContext.java:392) at org.jboss.seam.Component.instantiateSessionBean(Component.java:1287) at org.jboss.seam.Component.instantiate(Component.java:1273) at org.jboss.seam.Component.newInstance(Component.java:1966) ... 78 more Please look at the below link for more details and how to reproduce. http://www.seamframework.org/Community/AuthenticationUsingSeamRemoting http://www.seamframework.org/Community/EJBSLSBInjectionIssues -- 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

16 years, 2 months

6
23
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2399) Document no-conversation-view-id and conversation-required

by Christian Bauer (JIRA)

Document no-conversation-view-id and conversation-required ---------------------------------------------------------- Key: JBSEAM-2399 URL: http://jira.jboss.com/jira/browse/JBSEAM-2399 Project: JBoss Seam Issue Type: Task Components: Documentation Reporter: Christian Bauer These two options are mentioned only in passing in the Seam reference and the behavior they trigger is unclear. -- 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

16 years, 2 months

5
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2082) JMS Topic subscriptions never released

by Scott McNab (JIRA)

JMS Topic subscriptions never released -------------------------------------- Key: JBSEAM-2082 URL: http://jira.jboss.com/jira/browse/JBSEAM-2082 Project: JBoss Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.0.CR2, 2.0.0.CR1, 1.2.1.GA, 1.2.0.GA, 2.0.0.GA Environment: JBossAS 4.2.0.GA, All platforms. Reporter: Scott McNab Assigned To: Shane Bryzak In the current Seam remoting implementation, there is no mechanism to clean up and release JMS topic subscriptions for clients that may have subscribed to a JMS topic, but who do not explicitly unsubscribe() (e.g. due to a coding error or if the client simply disappears) Unless a web-client specifically calls Seam.Remoting.unsubscribe(), the RemoteSubscriber object is never released, and the corresponding TopicSession and TopicSubscriber resources will be held open indefinitely. This will cause the JMS provider to store an ever-growing list of undelivered topic messages, which will eventually result in an out of memory crash. Seam Remoting needs to be able to correctly identify situations whereby a RemoteSubscriber is no longer in use, and release resources accordingly. One possible solution might be to periodically check all subscriptions in the SubscriptionRegistry and release any which have not had a recent poll request beyond a certain time limit. -- 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

16 years, 2 months

6
12
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2008