June 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2301) JBoss EL bug handling overloaded methods with varargs mixed in

by Matthew Lieder (JIRA)

JBoss EL bug handling overloaded methods with varargs mixed in -------------------------------------------------------------- Key: JBSEAM-2301 URL: http://jira.jboss.com/jira/browse/JBSEAM-2301 Project: JBoss Seam Issue Type: Bug Components: EL Affects Versions: 2.0.0.GA Reporter: Matthew Lieder Doing facesMessages.add("Message") from an EL expression doesn't work, complaining about the String class not being compatible with the FacesMessage class. The problem is caused by a combination of two things: 1. There are two FacesMessages.add(...) that can accept one parameter: add(FacesMessage facesMessage) and add(String messageTemplate, Object... params) 2. The FacesMessages.add(...) that accepts a String as the first parameter can optionally accept additional parameters through a vararg If only one of those was the case, it'd work fine. However, having both at the same time triggers the error. -- 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, 2 months

3
5
0 / 0

[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

16 years, 2 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

16 years, 2 months

5
8
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

16 years, 2 months

2
2
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

16 years, 2 months

2
1
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

16 years, 2 months

2
1
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

16 years, 2 months

2
1
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

16 years, 2 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

16 years, 2 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

16 years, 2 months

2
1
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues June 2008