May 2009 - seam-issues - Jboss List Archives

[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, 8 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, 8 months

3
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, 8 months

2
1
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, 8 months

3
5
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, 8 months

2
1
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, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3197) RememberMe authentication for wiki

by Christian Bauer (JIRA)

RememberMe authentication for wiki ---------------------------------- Key: JBSEAM-3197 URL: https://jira.jboss.org/jira/browse/JBSEAM-3197 Project: Seam Issue Type: Task Components: WS Reporter: Christian Bauer Assignee: Christian Bauer Persistent cookies for RememberMe automatic logins require significant changes to the wiki: 1. Decouple user profile password changing UI from main profile, require authentication with existing password before entering new password. 2. Decouple user profile email changing UI from main profile, require authentication through regular login, notify user if she is logged in through persistent cookie. 3. (Optional) Require confirmation email procedure after email address change. 4. Add authentication token storage table/entity and implement TokenStore. 5. Implement RememberMe user interface checkbox. 6. Implement configurable expiration policy for cleanup of authentication token table. -- 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, 8 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2410) Editing of comments/forum posts

by Christian Bauer (JIRA)

Editing of comments/forum posts ------------------------------- Key: JBSEAM-2410 URL: http://jira.jboss.com/jira/browse/JBSEAM-2410 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor Users should be able to edit their own comments and forum posts if that is enabled in the system preferences. There is basically only the UI missing for that. -- 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, 8 months

6
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2689) FeedAggregator uses escapeAtSymbol() but should use escapeEmailAddress()

by Christian Bauer (JIRA)

FeedAggregator uses escapeAtSymbol() but should use escapeEmailAddress() ------------------------------------------------------------------------ Key: JBSEAM-2689 URL: http://jira.jboss.com/jira/browse/JBSEAM-2689 Project: JBoss Seam Issue Type: Bug Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer On the seamframework.org home page we have a feed aggregator that obfuscates the e-mail addresses which show up in the aggregated Fisheye feed. The routine just replaces all @ symbols, which is no good if someone posts a forum topic/reply with for example @In in the subject. We need a new WikiUtil.escapeEmailAddress() method that uses a proper regex to do the obfuscation job. -- 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, 8 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1852) Implement dynamic privilege system with assignment to roles and users

by Christian Bauer (JIRA)

Implement dynamic privilege system with assignment to roles and users --------------------------------------------------------------------- Key: JBSEAM-1852 URL: http://jira.jboss.com/jira/browse/JBSEAM-1852 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer -- 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, 8 months

2
3
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues May 2009