July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1013) Port Seam JSF controls to Ajax4JSF CDK

by Gavin King (JIRA)

Port Seam JSF controls to Ajax4JSF CDK -------------------------------------- Key: JBSEAM-1013 URL: http://jira.jboss.com/jira/browse/JBSEAM-1013 Project: JBoss Seam Issue Type: Feature Request Components: JSF Reporter: Gavin King Assigned To: Pete Muir Priority: Critical Fix For: 1.3.0.BETA1 We should also consider whether some of our controls would be better to belong in RichFaces. -- 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

17 years, 5 months

2
7
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1068) Seam JSF component library demonstration

by Pete Muir (JIRA)

Seam JSF component library demonstration ---------------------------------------- Key: JBSEAM-1068 URL: http://jira.jboss.com/jira/browse/JBSEAM-1068 Project: JBoss Seam Issue Type: Feature Request Components: Examples Affects Versions: 1.2.0.GA Reporter: Pete Muir Assigned To: Pete Muir Fix For: 1.3.0.BETA1 Examples of all the Seam JSF components running on the CDK -- 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

17 years, 5 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1054) Make Seam Filters orderable

by Michael Youngstrom (JIRA)

Make Seam Filters orderable --------------------------- Key: JBSEAM-1054 URL: http://jira.jboss.com/jira/browse/JBSEAM-1054 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.0.GA Reporter: Michael Youngstrom It would be nice if Seam web filters could be ordered. Although I don't have a pressing need for this right now I think it would be something needed eventually. -- 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

17 years, 5 months

3
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1045) enable the application message bundle to be connected to the core resource bundle

by Keith Naas (JIRA)

enable the application message bundle to be connected to the core resource bundle --------------------------------------------------------------------------------- Key: JBSEAM-1045 URL: http://jira.jboss.com/jira/browse/JBSEAM-1045 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Keith Naas On our projects, we wanted to be able to connect the core Seam ResourceBundle to the Faces Application message-bundle. Since the Faces Application message-bundle is instantiated by Faces, we cannot have it point directly to the Seam ResourceBundle. However, by fronting it with this class, we are able to make use of the nice Seam functionality from within core JSF controls (such as UIInput validation and conversion messages). {code} package com.biglots.common.web.util; import java.util.Enumeration; import org.jboss.seam.core.Interpolator; import org.jboss.seam.core.ResourceBundle; /** * The ApplicationResourceBundle is an attempt to fix the disconnect between having multiple resource bundles * and the lone application resource bundle used within the JSF. Within JSF2.1, it is possible to have multiple named * resource bundles. However, all error messages, validation messages, conversion messages, that are generated from * within core JSF classes go through the single message-bundle configured from within the faces-config.xml file. We * want to be able to reuse the messages in such a way that we only specify the message values once, and simply hook up * the messages bundles to the APIs in the seam components.xml. The ApplicationResourceBundle is just a class that * fronts the org.jboss.seam.core.ResourceBundle while also correctly handling EL expressions defined in any messages. * For instance, a message could be defined as "general.label.login.caption=#{someexpression}is invalid.". Pretty cool, * huh? So what else does it provide? It allows for resource bundles to have precedence. How do I configure this? * Well, pretty easily. To get the messasges available to Java classes, in the faces-config.xml just do * <code> * <application> * <message-bundle>com.biglots.common.web.util.ApplicationResourceBundle</message-bundle> * </application> * </code> * Then to configure the seam ResourceBundle that we are fronting, just do the following in components.xml. * Note that the order of the values is also the order of precedence during a lookup. * <code> * <core:resource-bundle> * <core:bundle-names> * <value>general</value> * <value>META-INF.messages</value> * <value>messages</value> * </core:bundle-names> * </core:resource-bundle> * </code> * * What if you want some named resource bundles? For instance to have a resource bundle named "generalMsg" * available in Session scope, just do the following in components.xml. * You can specify as many of the named resource bundles as you like, just make s * sure to configure the core resource bundle one as well. * <code> * <component name="generalMsg" class="org.jboss.seam.core.ResourceBundle"> * <property name="bundleNames"> * <value>general</value> * <value>META-INF.messages</value> * </property> * </component> * </code> * * @author knaas */ public class ApplicationResourceBundle extends java.util.ResourceBundle { /** * Returns the keys available in all of the configured resource bundles. * @return */ @Override public Enumeration<String> getKeys() { return ResourceBundle.instance().getKeys(); } /** * Returns the message that is looked up in the configured resource bundles. * It also interpolates any EL in the message so that we can put EL in messages * and they are properly evaluated in all Java Classes and JSF Views. * */ @Override protected Object handleGetObject(final String key) { return Interpolator.instance().interpolate(ResourceBundle.instance().getString(key), (Object[])null); } } {code} -- 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

17 years, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-864) Extend mailSession properties to be able to set mail.smtp.socketFactory.class and mail.smtp.socketFactory.port

by Piotr Walczyszyn (JIRA)

Extend mailSession properties to be able to set mail.smtp.socketFactory.class and mail.smtp.socketFactory.port -------------------------------------------------------------------------------------------------------------- Key: JBSEAM-864 URL: http://jira.jboss.com/jira/browse/JBSEAM-864 Project: JBoss Seam Issue Type: Feature Request Components: Mail Reporter: Piotr Walczyszyn Assigned To: Peter Muir In order to be able to send mails via gmail service it is required to set: mail.smtp.socketFactory.class = javax.net.ssl.SSLSocketFactory mail.smtp.socketFactory.port = 465 It would be good if it was possible to set additional options in the mail-session component. -- 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

17 years, 5 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-959) NullPointerException in ConversationEntry if stack is null

by Keith Naas (JIRA)

NullPointerException in ConversationEntry if stack is null ---------------------------------------------------------- Key: JBSEAM-959 URL: http://jira.jboss.com/jira/browse/JBSEAM-959 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.0.GA Reporter: Keith Naas When the conversation stack is null, the ConversationEntry constructor throws a NullPointerException. There is a conditional check earlier in the constructor that causes the conversationIdStack to be set to null. Then later it checks to see if the stack size is greater than 1. Kablooey! changed to if ( conversationIdStack != null && conversationIdStack.size()>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

17 years, 5 months

4
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1137) Potentially large security hole in Seam Captcha implementation

by Ian Hlavats (JIRA)

Potentially large security hole in Seam Captcha implementation -------------------------------------------------------------- Key: JBSEAM-1137 URL: http://jira.jboss.com/jira/browse/JBSEAM-1137 Project: JBoss Seam Issue Type: Bug Components: Security Affects Versions: 1.2.0.GA Environment: Any Reporter: Ian Hlavats I have been experiencing "holes" in the Seam captcha integration recently. The Seam documentation (section 21.1.1) recommends client-side state saving for JSF. The following scenario should point out a potential security issue with this approach. Suppose I have a JSF page with a typical user comment form on it that does not use Seam's captcha component. Now a malicious user scrapes my JSF page and stores a local copy on his computer, serialized UI component tree and all. In the meantime, I add Seam's captcha component to my JSF page, trusting it to cause a validation error when the form is submitted without the correct captcha text. Can the malicious user can now submit the previous copy of my form without the captcha component in the tree? I am using the MyFaces 1.1.4 JSF implementation. Thanks. -- 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

17 years, 5 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1723) Add jboss support to spring example

by Michael Youngstrom (JIRA)

Add jboss support to spring example ----------------------------------- Key: JBSEAM-1723 URL: http://jira.jboss.com/jira/browse/JBSEAM-1723 Project: JBoss Seam Issue Type: Feature Request Components: Spring Affects Versions: 2.0.0.CR1 Reporter: Michael Youngstrom Assigned To: Michael Youngstrom Fix For: 2.0.0.GA The spring example needs to be upgraded with jboss support when jboss .war support is added to the common example build. The jboss build should only need to have a different set of dependencies that don't conflict with the jboss common libraries. -- 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

17 years, 5 months

1
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1724) Add support for build a jboss war to common example build system

by Michael Youngstrom (JIRA)

Add support for build a jboss war to common example build system ---------------------------------------------------------------- Key: JBSEAM-1724 URL: http://jira.jboss.com/jira/browse/JBSEAM-1724 Project: JBoss Seam Issue Type: Feature Request Components: Examples Affects Versions: 2.0.0.CR1 Reporter: Michael Youngstrom Assigned To: Pete Muir Currently the example build system will only deploy and create for jboss a .ear. It would be nice if the example build system could support the creation and deployment of a jboss .war as well. -- 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

17 years, 5 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1667) Validators not working for ValueBindings from Trinidad

by Pete Muir (JIRA)

Validators not working for ValueBindings from Trinidad ------------------------------------------------------ Key: JBSEAM-1667 URL: http://jira.jboss.com/jira/browse/JBSEAM-1667 Project: JBoss Seam Issue Type: Bug Components: Core, EL, JSF Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Fix For: 2.0.0.CR1 When a ValueBinding from Trinidad is run through Validators invalidValues=null (even when there are invalidValues). Easy to replicate, just add @Length(max=5) to org.jboss.seam.example.seamdiscs.model.Artist.name, start up the seamdiscs example, log in, click on any artist from the Artists page, make sure they have a name longer than 5, and hit save. -- 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

17 years, 5 months

4
3
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues July 2007