July 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2537) Document pluggable deployment handler

by Pete Muir (JIRA)

Document pluggable deployment handler ------------------------------------- Key: JBSEAM-2537 URL: http://jira.jboss.com/jira/browse/JBSEAM-2537 Project: JBoss Seam Issue Type: Task Components: Core Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor Fix For: 2.0.1.GA -- 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-2431) Finish of StyleResource

by Pete Muir (JIRA)

Finish of StyleResource ----------------------- Key: JBSEAM-2431 URL: http://jira.jboss.com/jira/browse/JBSEAM-2431 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 2.0.1.CR1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor Fix For: 2.0.x Split out the id prefixing stuff and merge back into wiki. Document the style resource stuff. -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2250) Listing returns no records found if current page number is higher than expected results

by Terry (JIRA)

Listing returns no records found if current page number is higher than expected results --------------------------------------------------------------------------------------- Key: JBSEAM-2250 URL: http://jira.jboss.com/jira/browse/JBSEAM-2250 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Win XP, JDK 6, JBoss AS 4.2.2. Reporter: Terry Priority: Minor When browsing search results based on EntityQuery, and current results page number is higher than results based on further search criteria entered. Then seam returns no records found. See Forum issue for further details. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3202) When using pagination in EntityQuery, firstResult is not reset when query parameters are changed

by Timothy Whitehead (JIRA)

When using pagination in EntityQuery, firstResult is not reset when query parameters are changed ------------------------------------------------------------------------------------------------- Key: JBSEAM-3202 URL: https://jira.jboss.org/jira/browse/JBSEAM-3202 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.3.CR1 Reporter: Timothy Whitehead Priority: Minor When using pagination in EntityQuery, firstResult is not reset when query parameters are changed resulting in the possibility of pages beyond the end of the results being displayed. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2128) annotations on components installed by default can't be overriden

by Matt Drees (JIRA)

annotations on components installed by default can't be overriden ----------------------------------------------------------------- Key: JBSEAM-2128 URL: http://jira.jboss.com/jira/browse/JBSEAM-2128 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR2 Reporter: Matt Drees Priority: Minor This may actually be intended; I can't tell for sure. Certain annotation shouldn't be overrideable, like @Install or @Name. But it seems to me some should ( like @Scope or @JndiName). I'll attach a test case with more comments inline. It'd be helpful if a seam dev could look it over and say "Yes, it's behaving correctly", or "Something's broken". -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1690) Errors wrapped by ServletExceptions are not logged by ExceptionFilter

by Matt Drees (JIRA)

Errors wrapped by ServletExceptions are not logged by ExceptionFilter --------------------------------------------------------------------- Key: JBSEAM-1690 URL: http://jira.jboss.com/jira/browse/JBSEAM-1690 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Matt Drees Priority: Minor Errors (in particular, OutOfMemoryErrors), are not logged when they're wrapped by a servletException. ExceptionFilter.java (line 66) has this: log.error( "exception root cause", EJB.getCause(e) ); But EJB.getCause(e) returns null if e is a ServletException whose rootCause is not an Exception (like an OutOfMemoryError). -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-905) Using the debug page without exceptions

by Christian Bauer (JIRA)

Using the debug page without exceptions --------------------------------------- Key: JBSEAM-905 URL: http://jira.jboss.com/jira/browse/JBSEAM-905 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Christian Bauer Priority: Minor I'd like to call /debug.seam manually to look into my conversations. I usually don't enable it because I don't like being redirected to it from an exception. Why? It hides the URL that caused the exception and it fills my log with hundreds of lines after the exception stacktrace. -- 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] Updated: (JBSEAM-2907) seam-gen should make their List classes type safe

by Pete Muir (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-2907?page=com.atlassian.jira.pl... ] Pete Muir updated JBSEAM-2907: ------------------------------ Fix Version/s: 2.1.0.BETA2 (was: 2.1.0.GA) Assignee: Dan Allen (was: Max Rydahl Andersen) > seam-gen should make their List classes type safe > ------------------------------------------------- > > Key: JBSEAM-2907 > URL: https://jira.jboss.org/jira/browse/JBSEAM-2907 > Project: Seam > Issue Type: Bug > Components: Tools > Affects Versions: 2.0.0.GA > Reporter: Max Rydahl Andersen > Assignee: Dan Allen > Fix For: 2.1.0.BETA2 > > > Currently seam-gen generates CustomerList extends EntityQuery > If it instead did CustomerList extends EntityQuery<Customer> then the code java and EL based completion would know its methods referred to Customer and not just Object. -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2590) EntityQuery components hold the whole untruncated resultset if maxResults property is set and the underlying dialect does not support limits

by vargadan (JIRA)

EntityQuery components hold the whole untruncated resultset if maxResults property is set and the underlying dialect does not support limits --------------------------------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-2590 URL: http://jira.jboss.com/jira/browse/JBSEAM-2590 Project: JBoss Seam Issue Type: Bug Components: Framework Affects Versions: 2.0.1.GA Reporter: vargadan If the dialect supports limits then query objects only hold the number of rows set by the maxResults property. So i.e. if the search results 10000 rows but the page size is 10, only 10 objects are kept. But if the dialect does not support limits (like derby) then truncation of the result list in done in EntityQuery.getResultList() which in the previous example results in the following: - 10000 objects are kept in EntityQuery.resultList - only 10 of them is displayed in one page - EntityQuery.getResultList() returns EntityQuery.resultList the sublist every time when invoked - when paginating the query is executed for every page, so there is no point in holding all the rows. It causes quite a big overhead when query components are kept in conversation scope, which is the case most of the times. If the truncation was done just after querying against the DB, there would not be such an overhead. I.e. Query.truncResultList gets invoked in EntityQuery.initResultList and EntityQuery.resultList holds only the truncated list of results. -- 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
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2524) Exceptions ending conversations

by Alessandro Lazarotti (JIRA)

Exceptions ending conversations ------------------------------- Key: JBSEAM-2524 URL: http://jira.jboss.com/jira/browse/JBSEAM-2524 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.GA Environment: Windows Vista, Jboss APPServer 4.2, InternetExplorer 7 - FireFox 2.0.0 Reporter: Alessandro Lazarotti If any exception is thrown, objects in long-running conversation are discarded. I described how to simulate this in the forum: http://www.jboss.com/index.html?module=bb&op=viewtopic&t=127694&postdays=... -- 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
18
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