February 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3940) JbossPojoCacheProvider get method implementation error

by Hakan Uygun (JIRA)

JbossPojoCacheProvider get method implementation error ------------------------------------------------------ Key: JBSEAM-3940 URL: https://jira.jboss.org/jira/browse/JBSEAM-3940 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Environment: JBoss 4.2.3.GA Reporter: Hakan Uygun JbossPojoCacheProvider get method implementation is wrong. Region parameter ignored and return Node instance : public Object get(String region, String key) { try { return cache.get(getFqn(key)); } catch (CacheException e) { throw new IllegalStateException(String.format("Cache throw exception when trying to get %s from region %s.", key, region), e); } } It shoul be like JbossCacheProvider get method : public Object get(String region, String key) { try { Node node = cache.get(getFqn(region)); if (node != null) { return node.get(key); } else { return null; } } catch (CacheException e) { throw new IllegalStateException(String.format("Cache throw exception when trying to get %s from region %s.", key, region), e); } } -- 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3964) Upgrade JSF included with Seam to resolve async mail problems

by Zoltan Tiringer (JIRA)

Upgrade JSF included with Seam to resolve async mail problems ------------------------------------------------------------- Key: JBSEAM-3964 URL: https://jira.jboss.org/jira/browse/JBSEAM-3964 Project: Seam Issue Type: Bug Components: JSF Integration, Mail Affects Versions: 2.1.1.GA Environment: All Reporter: Zoltan Tiringer Asynchronous mail has been broken for quite a long time. According to JIRA-3187 the fix is to upgrade JSF. Unfortunately issue seems to have been forgotten, Seam still has JSF 1.2_09BETA1. https://jira.jboss.org/jira/browse/JBSEAM-3187 -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3961) Don't Outject on Destroy

by John Gilbert (JIRA)

Don't Outject on Destroy ------------------------ Key: JBSEAM-3961 URL: https://jira.jboss.org/jira/browse/JBSEAM-3961 Project: Seam Issue Type: Feature Request Components: Performance and Scalability Affects Versions: 2.1.1.GA Reporter: John Gilbert Priority: Minor It appears that Seam is performing outjection on destroy for SFSBs, which seems unnecessary. -- 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
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3970) A message with body type 'plain' will not send attachments

by Anthony Ogier (JIRA)

A message with body type 'plain' will not send attachments ---------------------------------------------------------- Key: JBSEAM-3970 URL: https://jira.jboss.org/jira/browse/JBSEAM-3970 Project: Seam Issue Type: Bug Components: Mail Affects Versions: 2.1.1.GA Environment: Windows XP SP3 / JDK 1.6.0.5 Reporter: Anthony Ogier Assignee: Pete Muir If the type of a m:body is set to "plain", then no attachment is sent with the mail. -- 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

1
1
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-3949) CSV export should take user defined separation character

by Zoltan Tiringer (JIRA)

CSV export should take user defined separation character -------------------------------------------------------- Key: JBSEAM-3949 URL: https://jira.jboss.org/jira/browse/JBSEAM-3949 Project: Seam Issue Type: Feature Request Components: Excel Affects Versions: 2.1.1.GA Reporter: Zoltan Tiringer CSV export should take user defined separation character (; or tab), should have "" wrapping optional, and probably even allow fixed length column export. -- 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
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-3950) Interceptor sort order: log a warning if around or within clause contains bad InterceptorType

by Julien Kronegg (JIRA)

Interceptor sort order: log a warning if around or within clause contains bad InterceptorType --------------------------------------------------------------------------------------------- Key: JBSEAM-3950 URL: https://jira.jboss.org/jira/browse/JBSEAM-3950 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.1.1.GA Environment: Seam Trunk source code http://fisheye.jboss.org/browse/Seam/trunk/src/main/org/jboss/seam/Compon... Reporter: Julien Kronegg Priority: Minor In the Component class, Interceptors are separated between client-side and server-side interceptors by mean of the @Interceptor's InterceptorType type property (see Component.addInterceptor(Interceptor)). The Interceptor's around and within properties allows to define the sort order (see also Component.newSort(List)). Problem: Since the client-side and server-side Interceptors are stored in two different lists, and since client-side interceptors are prioritary over server-side Interceptors, the programmer may write around/within clause that are ignored. For example, he may want to put a server-side Interceptor around a client-side Interceptor. In the current Component code, these cases are simply ignored. Solution: In case of bad server-side / client-side mix in the Interceptor annotation definition, the newSort(List) method should raise a warning. Proposition: - insert after line 1020: if (interceptorAnn.type()==InterceptorType.SERVER && cl.getAnnotation(Interceptor.class).type()==InterceptorType.CLIENT ) log.warn("Interceptor "+clazz.getName()+": a server-side Interceptor cannot be around the client-side Interceptor "+cl.getName()+" since client-side Interceptors are always prioritary"); - insert after line 1025: if (interceptorAnn.type()==InterceptorType.CLIENT && cl.getAnnotation(Interceptor.class).type()==InterceptorType.SERVER) log.warn("Interceptor "+clazz.getName()+": a client-side Interceptor cannot be within the server-side Interceptor "+cl.getName()+" since client-side Interceptors are always prioritary"); Pros: - programmer friendly Cons: - sorting takes (a bit) more 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, 10 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3967) resteasy xsd has typo in file name

by Norman Richards (JIRA)

resteasy xsd has typo in file name ---------------------------------- Key: JBSEAM-3967 URL: https://jira.jboss.org/jira/browse/JBSEAM-3967 Project: Seam Issue Type: Feature Request Reporter: Norman Richards Assignee: Norman Richards reasteasy -> resteasy -- 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

1
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2009