July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3206) Upload jexcel jars to jboss repo

by Daniel Roth (JIRA)

Upload jexcel jars to jboss repo -------------------------------- Key: JBSEAM-3206 URL: https://jira.jboss.org/jira/browse/JBSEAM-3206 Project: Seam Issue Type: Task Components: Excel Reporter: Daniel Roth Attachments: jxl.jar As discussed with Pete M, we need to get the jxl jars into the jboss repo: 2.6.6 is availible in this maven repo: http://www4.rothamsted.bbsrc.ac.uk/ondex/maven2/jexcelapi/jxl/2.6.6/ 2.6.8 is not to be found in any maven repo, but will be attached. This is the preferred library to upload. -- 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, 3 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3157) Generate profile-specific components.properties definitions through seam-gen

by Jacob Orshalick (JIRA)

Generate profile-specific components.properties definitions through seam-gen ---------------------------------------------------------------------------- Key: JBSEAM-3157 URL: http://jira.jboss.com/jira/browse/JBSEAM-3157 Project: Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.1.0.A1 Reporter: Jacob Orshalick Priority: Optional Seam-gen profiles provides a great way for Ant users to enable environment-specific configuration. It would be great to also provide the option to configure Seam components based on profile without having to edit the build (currently seam-gen is using filter tokens to swap out env-config reported at JBSEAM-3031). The approach is described here: http://solutionsfit.com/blog/2008/06/17/managing-environment-specific-con... Essentially creation of the following in a seam-gen'd project: components-dev.properties components-test.properties components-prod.properties and using the build to pick the appropriate properties file based on the current profile. Dependendent on JBSEAM-3031. -- 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, 3 months

2
9
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3031) components.properties not being used in seam-gen EAR

by Dan Allen (JIRA)

components.properties not being used in seam-gen EAR ---------------------------------------------------- Key: JBSEAM-3031 URL: http://jira.jboss.com/jira/browse/JBSEAM-3031 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.A1, 2.0.2.GA Reporter: Dan Allen Assigned To: Dan Allen Priority: Minor Fix For: 2.0.2.SP1, 2.1.0.BETA1 In the EAR build produced by seam-gen, the components.properties never gets a chance to do its job because the replacement tokens in components.xml are being filled in by the Ant build instead. -- 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, 3 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2860) Allow subclass of BaseSeamTest to provide an alternate MockServletContext implementation

by Clint Popetz (JIRA)

Allow subclass of BaseSeamTest to provide an alternate MockServletContext implementation ---------------------------------------------------------------------------------------- Key: JBSEAM-2860 URL: http://jira.jboss.com/jira/browse/JBSEAM-2860 Project: JBoss Seam Issue Type: Feature Request Affects Versions: 2.1.0.A1 Reporter: Clint Popetz Attachments: ExtendedServletContext.java, mockServletContext.diff I'm integrating seam into an environment which has a mock servlet context based on servletunit...but BaseSeamTest doesn't provide a hook for using that. This patch provides identical behavior by default, but allows subclasses to provide an alternate servletContext implementation. Note that BaseSeamTest wants to be able to call getInitParameters, so I've provided a subinterface "ExtendedServletContext," made BaseSeamTest use that interface, and made MockServletContext implement that interface. -- 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, 3 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3125) seam conversation and session.disconnect()

by Florian Keusch (JIRA)

seam conversation and session.disconnect() ------------------------------------------ Key: JBSEAM-3125 URL: http://jira.jboss.com/jira/browse/JBSEAM-3125 Project: Seam Issue Type: Bug Components: Spring Environment: Seam 2.0.2.SP1 Spring 2.5.4 Reporter: Florian Keusch hi, we use seam/spring/hibernate in our application. We detected a problem that database connections are not released after each request during seam conversations. Then if we have many conversations we can run out of connections. Let me explain this issue a little bit more: If a conversation starts a session is opened. This session is bound to the conversation and borrows a database connection from the pool. After the request the session doesn't have to be closed necessarily, but the session should be disconnected (to release the connection). What happens in the code (org.jboss.seam.ioc.spring.SeamManagedSessionFactoryBean) is that the session only is 'marked' as closed. Later seam recognizes that the conversation is still opened and the session will not be closed at the end of the request. The connection is therefore not returned to the pool for many requests until the conversation ends. For our case we fixed this problem by slightly changing the code of org.jboss.seam.ioc.spring.SeamManagedSessionFactoryBean (see the patch). We added code to disconnect the session greetings fke patch: --- SeamManagedSessionFactoryBean.java 2008-06-19 09:17:09.152049800 +0200 +++ SeamManagedSessionFactoryBeanPatched.java 2008-05-27 20:16:46.000000000 +0200 @@ -165,8 +165,6 @@ } if (method.getName().equals("close")) { - Session session = getSession(); - session.disconnect(); isClosed = true; return null; } @@ -290,7 +288,6 @@ if (method.getName().equals("close")) { log.debug("Closing Session Proxy."); - delegate.disconnect(); closed = true; return null; } -- 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, 3 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1818) Patch proposed to LocaleSelector

by Marco Pancotti (JIRA)

Patch proposed to LocaleSelector -------------------------------- Key: JBSEAM-1818 URL: http://jira.jboss.com/jira/browse/JBSEAM-1818 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Marco Pancotti Priority: Minor org.jboss.seam.international.LocaleSelector does not implement a getDefaultLocale method. I think it can be useful in a multi-language application. So I propose to apply the following patch in the LocaleSelector class adding the following methods (it can be more complex if you want orthogonal returns respect the return of the specified locale): public Locale getDefaultLocale(){ return FacesContext.getCurrentInstance().getApplication().getDefaultLocale() ; } public String getDefaultLocaleLanguage(){ return FacesContext.getCurrentInstance().getApplication().getDefaultLocale() .getLanguage(); } Marco Pancotti -- 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, 3 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2675) Search superclasses of components for @Interceptor

by Clint Popetz (JIRA)

Search superclasses of components for @Interceptor -------------------------------------------------- Key: JBSEAM-2675 URL: http://jira.jboss.com/jira/browse/JBSEAM-2675 Project: JBoss Seam Issue Type: Feature Request Reporter: Clint Popetz Attachments: component-superclass-interceptors.diff Currently Component.initInterceptors doesn't search superclasses of the bean class for an @Interceptors annotation. This patch adds that functionality. -- 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, 3 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3106) Enable "@In QuartzTriggerHandle timer" in currently running Job.

by Cloves Almeida (JIRA)

Enable "@In QuartzTriggerHandle timer" in currently running Job. ---------------------------------------------------------------- Key: JBSEAM-3106 URL: http://jira.jboss.com/jira/browse/JBSEAM-3106 Project: Seam Issue Type: Patch Components: Async Affects Versions: 2.0.2.GA Environment: Any Reporter: Cloves Almeida When using EJB Timer, the "timer" event context variable is accessible during the currently executing job, returning a javax.ejb.Timer. This enables the executing timer to cancel itself. This patch does the equivalent for Quartz, populating the variable with a QuartzTriggerHandle. -- 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, 3 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3120) SeamCollectionModel in Seam-Trinidad example is not handling the sorting in the most efficient way

by Alex Savitsky (JIRA)

SeamCollectionModel in Seam-Trinidad example is not handling the sorting in the most efficient way -------------------------------------------------------------------------------------------------- Key: JBSEAM-3120 URL: http://jira.jboss.com/jira/browse/JBSEAM-3120 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.0.3.CR1 Reporter: Alex Savitsky Priority: Optional The way the sorting is handled in SeamCollectionModel, is not anywhere near optimal. I undernstand that this is only an example, but since people often just paste this into the real apps, it might as well be a little more polished. The way the setSortCriteria is coded up, a new query will be issued every time this method is called, as Query.setOrder triggers an automatic refresh(), which wipes out the data model in the process - thus forcing the creation of a new one, which won't have the criteria property set. -- 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, 3 months

2
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3186) org.jboss.seam.Entity$NotEntityException: Unable to establish name of entity class

by Julien Buret (JIRA)

org.jboss.seam.Entity$NotEntityException: Unable to establish name of entity class ---------------------------------------------------------------------------------- Key: JBSEAM-3186 URL: https://jira.jboss.org/jira/browse/JBSEAM-3186 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.0.2.SP1 Environment: JBoss 4.2.1 Hibernate 3.2.6 Reporter: Julien Buret Priority: Minor Attachments: HibernatePersistenceProvider.patch Sometimes I've got this kind of exception : org.jboss.seam.Entity$NotEntityException: Unable to establish name of entity class Test_$$_javassist_40 at org.jboss.seam.Entity.mergeAnnotationAndOrmXml(Entity.java:181) at org.jboss.seam.Entity.<init>(Entity.java:58) at org.jboss.seam.Entity.forClass(Entity.java:165) at org.jboss.seam.Entity.forBean(Entity.java:145) at org.jboss.seam.persistence.PersistenceProvider.getId(PersistenceProvider.java:64) at org.jboss.seam.persistence.HibernatePersistenceProvider.getId(HibernatePersistenceProvider.java:168) at org.jboss.seam.framework.EntityIdentifier.<init>(EntityIdentifier.java:13) at org.jboss.seam.ui.converter.entityConverter.EntityLoader.createIdentifier(EntityLoader.java:40) at org.jboss.seam.ui.converter.entityConverter.AbstractEntityLoader.put(AbstractEntityLoader.java:50) -- 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, 3 months

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2008