February 2009 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2514) EntityQuery can't be used in PAGE Scope

by Martin Hoffmann (JIRA)

EntityQuery can't be used in PAGE Scope --------------------------------------- Key: JBSEAM-2514 URL: http://jira.jboss.com/jira/browse/JBSEAM-2514 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.0.0.GA Environment: Seam 2.0.0.GA, JBoss AS 4.2.2.GA Reporter: Martin Hoffmann Priority: Optional The EntityHome is not able to operate in PAGE scope and the documentation says nothing about compatible scopes and framework classes. It throws an exeption: aused by: javax.el.ELException: /client/claim_list.xhtml @16,52 value="#{testList.dataModel}": Error reading 'dataModel' on type de.iseki.garantieext.card.Test List_$$_javassist_0 at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.ja va:76) at javax.faces.component.UIOutput.getValue(UIOutput.java:173) ... 69 more Caused by: java.lang.IllegalStateException: EntityManager is closed at org.hibernate.ejb.EntityManagerImpl.getSession(EntityManagerImpl.java :42) -- 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

14 years, 11 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3095) observing events in the same component the raised one results in interceptors not being run on the observer message

by Norman Richards (JIRA)

observing events in the same component the raised one results in interceptors not being run on the observer message ------------------------------------------------------------------------------------------------------------------- Key: JBSEAM-3095 URL: http://jira.jboss.com/jira/browse/JBSEAM-3095 Project: Seam Issue Type: Bug Reporter: Norman Richards Assigned To: Norman Richards Fix For: 2.0.3.GA, 2.1.0.BETA1 This is due to the MethodContextInterceptor imposing the unproxied object on the user. I think the fix is to make sure that events happen in a distinct method context. I've tested this with javabean components, but session beans might be trickier. -- 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

14 years, 11 months

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3132) Seam text parser produces newline when HTML is used beginning of a line

by Christian Bauer (JIRA)

Seam text parser produces newline when HTML is used beginning of a line ----------------------------------------------------------------------- Key: JBSEAM-3132 URL: http://jira.jboss.com/jira/browse/JBSEAM-3132 Project: Seam Issue Type: Bug Components: Seam Text Reporter: Christian Bauer Assigned To: Christian Bauer foobar is rendered as foo bar This seems to affect all HTML tags that are at beginning of line, not inside a paragraph. -- 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

14 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2231) Setup wizard for wiki

by Christian Bauer (JIRA)

Setup wizard for wiki --------------------- Key: JBSEAM-2231 URL: http://jira.jboss.com/jira/browse/JBSEAM-2231 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Write a setup wizard that replaces the manual wiki-data.sql editing and import. We should have the following setup procedure: - Get the recommended environment ready (JBoss AS, MySQL) - Deploy the wiki-ddl.sql on a new database - Deploy the wiki.war on the appserver - Open http://server/wiki/ and go through the setup wizard The wizard will first import the minimum dataset (guest/admin users, roles, start page) and then ask the usual setup questions (site base URL, etc.). Depending on the future of the plugin API, it could also optionally allow you to configure some plugin defaults so you don't have to go into the Admin screen to change them after the install. Also, we can offer prepackaged datasets for certain use cases that can be imported with the wizard, e.g. "Help Documents", "Blog Website", "Forum Website". -- 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

14 years, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2872) Duplicate command in the directory browser or be able to set creation time to Now

by Max Andersen (JIRA)

Duplicate command in the directory browser or be able to set creation time to Now --------------------------------------------------------------------------------- Key: JBSEAM-2872 URL: http://jira.jboss.com/jira/browse/JBSEAM-2872 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Max Andersen Assigned To: Christian Bauer My problem was that I created 2 blogs A and B and published B first then A later. On the feed it looked correct, but on the front page B was listed before A because the sort is based on creation times. Christian suggested to have a duplicate command... What I would like is a way to either sort based on the first publish time or be able to set the create timestamp to now so I don't have to affect the feeds and risk publishing the same entry twice. -- 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

14 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1505) Application-level log

by Christian Bauer (JIRA)

Application-level log --------------------- Key: JBSEAM-1505 URL: http://jira.jboss.com/jira/browse/JBSEAM-1505 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor Create a persistent LogEvent and raise a Seam event whenever anything interesting happens in the app (user registered, document deleted, notification stopped because of bounces, and so on). Show log in the admin interface and allow admin to set log level and clear the log. -- 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

14 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3150) Published / Unpublished status on wiki documents

by Per Wiklander (JIRA)

Published / Unpublished status on wiki documents ------------------------------------------------ Key: JBSEAM-3150 URL: http://jira.jboss.com/jira/browse/JBSEAM-3150 Project: Seam Issue Type: Feature Request Components: Wiki Reporter: Per Wiklander Assigned To: Christian Bauer It would be nice to be able to choose if a document is "published" i.e. visible (without using permissions as a workaround). The document could be a work in progress or something that you want to prepare in advance but not release before a certain time. Being able to choose the time the document goes from the unpublished to published state would be even better. This way you can work on a new part of the site and have it published Monday morning 0700 without having to actually be there pushing the button. This shouldn't be too hard (said by someone with about zero knowledge of the wiki code) and I'd be glad to help if the idea is approved. -- 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

14 years, 11 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3070) Tomcat not cleaning up HttpSessions after a single FeedServlet request

by Christian Bauer (JIRA)

Tomcat not cleaning up HttpSessions after a single FeedServlet request ---------------------------------------------------------------------- Key: JBSEAM-3070 URL: http://jira.jboss.com/jira/browse/JBSEAM-3070 Project: Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Critical Only reproducible in production: The number of HttpSessions is growing over several days. I wrote a listener and it shows the following pattern: <User> <Action> <Creation timestamp> <Last access timestamp> <Idle> <Expired since> Guest Feed: 1 04. Jun 2008, 16:01:46 04. Jun 2008, 16:01:46 00:13:49 00:03:49 (EXPIRED!) 5 KiB Guest Feed: 1 04. Jun 2008, 15:59:56 04. Jun 2008, 15:59:56 00:15:39 00:05:39 (EXPIRED!) 5 KiB Guest Feed: 1450 04. Jun 2008, 16:03:31 04. Jun 2008, 16:03:31 00:12:04 00:02:04 (EXPIRED!) 5 KiB The EXPIRED! sessions are alive past their maxInactiveInterval (see the time next to it). Tomcat does not clean them up and I don't know why. The only recognizable pattern is that they are all from the FeedServlet, and a single request to that servlet. At this point I suspect that something in Seams ContextualRequest filter is wrong and influencing Tomcat negatively. Will keep this assigned to the wiki until the cause is clearer. -- 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

14 years, 11 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2700) Switch wiki to better feed parsing/generation library

by Christian Bauer (JIRA)

Switch wiki to better feed parsing/generation library ----------------------------------------------------- Key: JBSEAM-2700 URL: http://jira.jboss.com/jira/browse/JBSEAM-2700 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer The Rome feed parser/generator is missing some crucial elements related to Atom feeds, for example, rendering <updated> and <published> timestamps on a feed item is not possible. The API is also stuck in JDK 1.4 land, making it a pain to use. Evaluate these feed parsers/generators as candidates for a possible replacement: http://yarfraw.sourceforge.net/ http://commons.apache.org/sandbox/feedparser/ Yarfraw seems to support most of the Atom 1.0 spec, so that might be the best candidate. -- 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

14 years, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3872) album plugin

by wu haixing (JIRA)

album plugin ------------ Key: JBSEAM-3872 URL: https://jira.jboss.org/jira/browse/JBSEAM-3872 Project: Seam Issue Type: Feature Request Components: Wiki Reporter: wu haixing Assignee: Christian Bauer There should has directories manage the user's pictures.Besides current WikiDirectory and WikiUploadImage features,the album should accessable by password!So User should maintain the access token to albums in session. -- 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

14 years, 11 months

2
1
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues February 2009