April 2011 - seam-issues - Jboss List Archives

[JBoss JIRA] Created: (SEAMFACES-46) @End should probably not throw exceptions if a conversation could not be ended because it does not exist

by Lincoln Baxter III (JIRA)

@End should probably not throw exceptions if a conversation could not be ended because it does not exist -------------------------------------------------------------------------------------------------------- Key: SEAMFACES-46 URL: https://jira.jboss.org/browse/SEAMFACES-46 Project: Seam Faces Issue Type: Feature Request Components: Conversations Affects Versions: 3.0.0.Alpha4 Reporter: Lincoln Baxter III The @End annotation calls conversation.end() without first checking conversation.isTransient(). This results in exceptions when invoking the method on a transient conversation. This should either be a configuration option of the annotation, or should not occur: @End(ConversationPropagation.REQUIRED) @End(ConversationPropagation.OPTIONAL) Etc... something like that(). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

6
6
0 / 0

[JBoss JIRA] Created: (SEAMSECURITY-58) identity.inGroup method should return true for a user when the user is assigned a role within that group using identity.addRole

by Martin Gencur (JIRA)

identity.inGroup method should return true for a user when the user is assigned a role within that group using identity.addRole ------------------------------------------------------------------------------------------------------------------------------- Key: SEAMSECURITY-58 URL: https://issues.jboss.org/browse/SEAMSECURITY-58 Project: Seam Security Issue Type: Feature Request Affects Versions: 3.0.0.Final Reporter: Martin Gencur Assignee: Shane Bryzak Fix For: Future Currently when I use identity.addRole("admin", "USERS", "GROUP") for certain user and then invoke identity.inGroup("USERS", "GROUP") on that user, I get false. This is visible e.g. in an Authorization example. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (SEAMFACES-122) Find a way to use the @ViewConfig enums to provide yype-safe navigation rules

by Brian Leathem (JIRA)

Find a way to use the @ViewConfig enums to provide yype-safe navigation rules ----------------------------------------------------------------------------- Key: SEAMFACES-122 URL: https://issues.jboss.org/browse/SEAMFACES-122 Project: Seam Faces Issue Type: Feature Request Components: View Configuration Reporter: Brian Leathem Fix For: 3.0.1 Option 1) instead of using a @ViewPattern annotation, instead pass it to the constructor of the enum, to be stored as a property of the enum. Problem: the application developer would have to implement the constructor Option 2) require the developer to implement an interfaces, that specifies a setViewId method for an enum value, programmatically set that viewId with what is in the @ViewPattern annotation Feel free to provide more implementation options in the comments! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
11
0 / 0

[JBoss JIRA] Created: (SOLDER-78) Add convenient APIs for creating a bean instance

by Dan Allen (JIRA)

Add convenient APIs for creating a bean instance ------------------------------------------------ Key: SOLDER-78 URL: https://issues.jboss.org/browse/SOLDER-78 Project: Seam Solder Issue Type: Feature Request Components: Core Affects Versions: 3.0.0.Beta4 Reporter: Dan Allen Fix For: 3.0.0.Final Migrate the convenience APIs for creating bean instances from Seam Faces. Although use of these APIs should be discouraged as a general practice, they are often crucial time savers for use in extension writing and test environments. https://github.com/seam/faces/blob/master/impl/src/main/java/org/jboss/se... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
4
0 / 0

[JBoss JIRA] Created: (SOLDER-79) Provide convenience APIs for injecting into a non-managed instance

by Dan Allen (JIRA)

Provide convenience APIs for injecting into a non-managed instance ------------------------------------------------------------------ Key: SOLDER-79 URL: https://issues.jboss.org/browse/SOLDER-79 Project: Seam Solder Issue Type: Feature Request Components: Core Affects Versions: 3.0.0.Beta4 Reporter: Dan Allen Fix For: 3.0.0.Final Migrate the APIs for injecting into a non-managed instance from Seam Wicket. https://github.com/seam/wicket/blob/master/impl/src/main/java/org/jboss/s... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-4464) <totalPages>-tag for pdf generation

by Robert Becker (JIRA)

<totalPages>-tag for pdf generation ----------------------------------- Key: JBSEAM-4464 URL: https://jira.jboss.org/jira/browse/JBSEAM-4464 Project: Seam Issue Type: Feature Request Reporter: Robert Becker When creating official documents it is often required to add something like "Page X of Y" to the footer. The p:pageNumber-tag provides the first value whereas a totalPages-tag is missing. Márcio Dantas created and published a wokarround for this under http://seamframework.org/Community/SeamPdfPageXOfY but this approach is somewhat "dirty". I see that it culd be problematic to provide the number of total pages while rendering the document so perhaps a placeholder could be used and altered when onCloseDocument in UIDocument is called. -- 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

13 years, 3 months

4
3
0 / 0

[JBoss JIRA] Created: (SEAMINTL-42) Description of how to alter the User Locale in the documentation is missing @Client

by Ken Finnigan (JIRA)

Description of how to alter the User Locale in the documentation is missing @Client ----------------------------------------------------------------------------------- Key: SEAMINTL-42 URL: https://issues.jboss.org/browse/SEAMINTL-42 Project: Seam International Issue Type: Bug Affects Versions: 3.0.0.Final Reporter: Ken Finnigan Assignee: Ken Finnigan The means of updating the User Locale described here: http://docs.jboss.org/seam/3/international/snapshot/reference/en-US/html_... is incorrect as it is missing @Client at the Event injection point. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (SEAMINTL-44) BundleTemplateMessage breaks with non-String ResourceBundles

by Nicklas Karlsson (JIRA)

BundleTemplateMessage breaks with non-String ResourceBundles ------------------------------------------------------------ Key: SEAMINTL-44 URL: https://issues.jboss.org/browse/SEAMINTL-44 Project: Seam International Issue Type: Bug Components: Messages Affects Versions: 3.0.0.Final Reporter: Nicklas Karlsson Assignee: Ken Finnigan BundleTemplateMessages has in build() {code} try { text = bundles.get(clientLocale, textKey.getBundle()).getString(textKey.getKey()); } catch (Exception e) { log.warn("Could not load bundle: " + textKey); text = textDefault; } {code} which will result in a ClassCastException if the resource is non-string (because ResourceBundle.getString implementation casts getObject to String) and is further translated to a "Could not load bundle" warning followed by the BundleKey being outputted. Since ResourceBundle.getString is final, there is no way of overloading this behaviour. Using toString on a non-null resource would give some flexibility to this, perhaps. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

2
8
0 / 0

[JBoss JIRA] Created: (SEAMFACES-91) Add JSF File Upload Component

by Alex Durgin (JIRA)

Add JSF File Upload Component ----------------------------- Key: SEAMFACES-91 URL: https://issues.jboss.org/browse/SEAMFACES-91 Project: Seam Faces Issue Type: Feature Request Components: UI Components Reporter: Alex Durgin Seam 2 featured a file upload jsf component. Including it in Seam Faces would be very useful until the mainline JSF project gets around to adding it. RichFaces and similar have upload components, but there are situations where a standard HTML file upload is more appropriate. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
2
0 / 0

[JBoss JIRA] Created: (SEAMFACES-83) Would be nice to do @Inject @Faces List<Locale> supportedLocales

by Leiv Hellebo (JIRA)

Would be nice to do @Inject @Faces List<Locale> supportedLocales ---------------------------------------------------------------- Key: SEAMFACES-83 URL: https://issues.jboss.org/browse/SEAMFACES-83 Project: Seam Faces Issue Type: Feature Request Reporter: Leiv Hellebo Seam 2 picked up the available faces locales with localeSelector.getSupportedLocales would be nice to have the same for the seam 3 faces module (SEAMINTL has the component AvailableLocales, but doesn't use any jsf stuff) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 3 months

3
4
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues April 2011