March 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1117) support enum types in @RaiseEvent or a new @RaiseEventType annotation

by Bradley Smith (JIRA)

support enum types in @RaiseEvent or a new @RaiseEventType annotation --------------------------------------------------------------------- Key: JBSEAM-1117 URL: http://jira.jboss.com/jira/browse/JBSEAM-1117 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Bradley Smith RaiseEvent: @Target(METHOD) @Retention(RUNTIME) @Documented public @interface RaiseEvent { /** * The event name, defaults to the name * of the method. * * @return the event name */ String value() default ""; //TODO: String[] ifOutcome() default {}; } Is it possible to make the value be based on an enum type? I currently have all my application event types enumerated in enum called EventType. I've tried doing: @RaiseEvent(EventType.ApplicationSaved.name()) however, this doesn't count as a constant String and is invalid syntax. It seems more 'elegant' to be able to enumerate the event types of an application in something like an enum than to sprinkle strings throughout the code with the specific event String values. Maybe an alternate annotation is called for - say, @RaiseEventType(MyEnum.MyEventType)? I'm not sure - I don't have a solid grasp of the syntax used to define an annotation. -- 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

18 years, 10 months

3
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1110) Support multiple bundle for a view-id in pages.xml

by Bing Zou (JIRA)

Support multiple bundle for a view-id in pages.xml -------------------------------------------------- Key: JBSEAM-1110 URL: http://jira.jboss.com/jira/browse/JBSEAM-1110 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.0.GA Reporter: Bing Zou Since Seam supports Facelets. A typical thing we do by using Facelets is the idea of templates. For example, two concrete pages a.xhtml, b.xhtml both extend from template.xhtml. We want to separate the resource bundle for each concrete page as a coding standard. Then in pages.xml we will have <page view-id="/parentfolder/a.xhtml" bundle="parentFolder/a" /> <page view-id="/parentfolder/b.xhtml" bundle="parentFolder/b" /> However, since both a.xhtml and b.xhtml has the same template.xhtml, we want to separate the common fields from template.xhtml to it's own resource bundle. Therefore, for each view-id should have an additional bundle, for example, <page view-id="/parentfolder/a.xhtml" bundle="parentFolder/a,parentFolder/template" /> Or maybe Seam can be smart to find out that a.xhtml extends from template.xhtml and there is a <page view-id="/parentFolder/template.xhtml" bundle="parentFolder/template" /> and then both bundle will be available for view-id a.xhtml. Of course, if there is any conflict, the child page always override parent page's property. -- 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

18 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-739) JSF postback authorization

by Gavin King (JIRA)

JSF postback authorization -------------------------- Key: JBSEAM-739 URL: http://jira.jboss.com/jira/browse/JBSEAM-739 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.2.0.BETA1 There should be a permission check that occurs when we submit a form from a JSF view id. There might also be value in securing particular actions or outcomes for a view id, but that is more speculative. -- 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

18 years, 10 months

4
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1055) Query Pagination in JBoss Seam Framework

by Antonio Navas (JIRA)

Query Pagination in JBoss Seam Framework ---------------------------------------- Key: JBSEAM-1055 URL: http://jira.jboss.com/jira/browse/JBSEAM-1055 Project: JBoss Seam Issue Type: Patch Components: Framework Affects Versions: 1.2.0.GA Reporter: Antonio Navas Priority: Minor I'm not sure that this is the correct procedure, but I want to contribute to this project.... I think there is an issue regarding pagination in EntityQuery. The problem is that it adds an unnecessary last page when the actual size of the result list equals the maxResults attribute. For example, if maxResults is set to 5 and the total result count for the query is 10, the pagination returns 3 pages instead of 2, and the last page is empty. I think that the implementation of the methods "isNextExists" and "getLastFirstResult" are wrong, and the correct implementation should be: public boolean isNextExists() { return getResultCount() > (getFirstResult() == null ? 0 : getFirstResult()) + getMaxResults(); } public long getLastFirstResult() { return ( (getResultCount()-1) / getMaxResults() ) * getMaxResults(); } -- 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

18 years, 10 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1020) Configurable Drools event listeners (primarily for debug logging)

by Christian Bauer (JIRA)

Configurable Drools event listeners (primarily for debug logging) ----------------------------------------------------------------- Key: JBSEAM-1020 URL: http://jira.jboss.com/jira/browse/JBSEAM-1020 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Christian Bauer Assigned To: Shane Bryzak Priority: Minor I want to see what is going on when my rules are evaluated, according to the Drools docs this is how: workingMemory.addEventListener( new DebugWorkingMemoryEventListener() ); I have to do that in code right now, would be nice to be able to configure the identity component externally in config file. It also doesn't work, at least not in JBoss with a WAR deployment. I don't see any debug printed on System.out. Task: Ask the drools guys how we get logging for Seam users. -- 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

18 years, 10 months

5
22
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-449) Get CRUD messages out of components.xml and into resource bundles

by Gavin King (JIRA)

Get CRUD messages out of components.xml and into resource bundles ----------------------------------------------------------------- Key: JBSEAM-449 URL: http://jira.jboss.com/jira/browse/JBSEAM-449 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.0.BETA1 Reporter: Gavin King Assigned To: Gavin King Fix For: 1.1.0.BETA2 update/delete/create messages don't belong in components.xml -- 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

18 years, 10 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-642) Improve seam-gen generated look and feel

by Ronald van Kuijk (JIRA)

Improve seam-gen generated look and feel ---------------------------------------- Key: JBSEAM-642 URL: http://jira.jboss.com/jira/browse/JBSEAM-642 Project: JBoss Seam Issue Type: Task Components: Tools Affects Versions: 1.1.0.GA Environment: N/A Reporter: Ronald van Kuijk Assigned To: Ronald van Kuijk Priority: Minor Fix For: 1.2.0.BETA1 The look and feel of the pages generated by seam-gen should have a more professional look and feel. Things to do: - show/hide optional elements - mark required elements as such - font types - colors - menu - breadcrums - footer - validation errors / message -- 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

18 years, 11 months

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1051) Conversation Picker no longer renders

by Tony Herstell (JIRA)

Conversation Picker no longer renders ------------------------------------- Key: JBSEAM-1051 URL: http://jira.jboss.com/jira/browse/JBSEAM-1051 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.2.0.GA Environment: Seam 1.2.0.Patch 1, IceFaces 1.6.0.DR1, JBoss Server Reporter: Tony Herstell http://gaming.homeip.net:8080/risingstars (it should be rendering when you jump out of a conversation using the menu i.e. Find+update and then use the menu to Find+Start a delete. This stopped working when I moved onto Seam 1.2.0.Patch 1 -- 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

18 years, 11 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-614) API Documentation for the org.jboss.seam.ui.* classes

by Todd Smart (JIRA)

API Documentation for the org.jboss.seam.ui.* classes ----------------------------------------------------- Key: JBSEAM-614 URL: http://jira.jboss.com/jira/browse/JBSEAM-614 Project: JBoss Seam Issue Type: Task Components: Documentation Affects Versions: 1.1.1.GA Reporter: Todd Smart This is related in some ways to http://jira.jboss.org/jira/browse/JBSEAM-301. It is very difficult (without reviewing the source code) to understand the Seam UI class and tag libraries. At a minimum, the API should be included in the documentation IMO. Regards, Todd -- 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

18 years, 11 months

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-844) Fire an event on AuthorizationException

by Ben Catherall (JIRA)

Fire an event on AuthorizationException --------------------------------------- Key: JBSEAM-844 URL: http://jira.jboss.com/jira/browse/JBSEAM-844 Project: JBoss Seam Issue Type: Feature Request Components: Security Affects Versions: 1.1.6.GA Reporter: Ben Catherall When an AuthorizationException is thrown in Identity.checkRestriction, it would be useful if an event is raised in the same way it is for a NotLoggedInException. A suitable event name might be "org.jboss.seam.notAuthorized" -- 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

18 years, 11 months

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