November 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2195) Converters should be created in stateless scope

by Adam Warski (JIRA)

Converters should be created in stateless scope ----------------------------------------------- Key: JBSEAM-2195 URL: http://jira.jboss.com/jira/browse/JBSEAM-2195 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.CR3 Reporter: Adam Warski Priority: Minor Now, the converter scope is event, however it should be stateless, so that multiple usages of one converter on a page would work, in conjuction with facelets converter tags. For more details, see the forum. Also, what about validators? -- 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, 11 months

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1532) include jar-versions.xml file

by Dan Allen (JIRA)

include jar-versions.xml file ----------------------------- Key: JBSEAM-1532 URL: http://jira.jboss.com/jira/browse/JBSEAM-1532 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Affects Versions: 1.3.0.ALPHA Environment: seam CVS HEAD Reporter: Dan Allen Priority: Minor It would be so helpful if a jar-versions.xml file could be kept up to date in the root of the seam source code to track the versions of the bundle libraries, in the absence of other solutions. This idea comes from the JBoss AS, which uses this file to communicate the versions of libraries used. Documenting the versions helps: 1. developers, who may find challenge in combining APIs of libraries without knowing the version 2. users who are unable to determine the contents of what they downloaded 3. for legal reasons, just in case there are differences in licenses amongst releases of third party products, to protect seam itself as well as integrators of seam. With all that said, the better solution is to use ant-ivy or maven2 to get the jar files out of the source code. But I digress. -- 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, 11 months

2
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2227) Write some docs on how to use SeamTest without TestNG

by Dmitriy Lapko (JIRA)

Write some docs on how to use SeamTest without TestNG ----------------------------------------------------- Key: JBSEAM-2227 URL: http://jira.jboss.com/jira/browse/JBSEAM-2227 Project: JBoss Seam Issue Type: Feature Request Components: Test Harness Affects Versions: 2.0.0.GA Reporter: Dmitriy Lapko -- 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, 11 months

2
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1679) passing callId to callback after async call

by Christoph Aigner (JIRA)

passing callId to callback after async call ------------------------------------------- Key: JBSEAM-1679 URL: http://jira.jboss.com/jira/browse/JBSEAM-1679 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Affects Versions: 2.0.0.BETA1 Reporter: Christoph Aigner Assigned To: Shane Bryzak Priority: Trivial passing callId (remote.js / line 732): call.callback(value, context, callId); makes it possible to differentiate between simultanous calls of certain functions, as callId is already returned on function call necessary if options/variables are related to certain backend-calls. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1672) Dependency on JMS

by Ralph Schaer (JIRA)

Dependency on JMS ----------------- Key: JBSEAM-1672 URL: http://jira.jboss.com/jira/browse/JBSEAM-1672 Project: JBoss Seam Issue Type: Feature Request Components: Remoting Affects Versions: 2.0.0.BETA1 Environment: JavaBeans, Hibernate, Tomcat 6.0.13, Java 6, Windows XP Reporter: Ralph Schaer Assigned To: Shane Bryzak Priority: Optional Seam Remoting has a dependency on JMS. The problem is that the RequestHandlerFactory instantiate the PollHandler in the constructor. In a non EE environment like Tomcat I have to put a JMS library into the classpath although the application does not need JMS. Not a big deal, but maybe it's possible to change Seam Remoting that it loads PollHandler only when there is a JMS library in the classpath. -- 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, 11 months

2
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1224) Consider integration of security with App Framework

by Pete Muir (JIRA)

Consider integration of security with App Framework --------------------------------------------------- Key: JBSEAM-1224 URL: http://jira.jboss.com/jira/browse/JBSEAM-1224 Project: JBoss Seam Issue Type: Feature Request Components: Core, Security Affects Versions: 1.2.1.GA Reporter: Pete Muir Assigned To: Shane Bryzak >From the forums: 'One down side to using EntityHome for generic crud is lack of built in security. One needs to be careful when using Homes for crud operations that allow or require RequestParameters. You need to ensure the operation on this ID is valid. You don't want to expose information you shouldn't and you definitely don't want to modify or destroy information you shouldn't. For example, you don't want a user to update or delete another user's entity just by changing an ID in the URL and hitting return. Seam supports entity level security and you can probably extend a Home to double check access restrictions prior to operations. Likewise, you don't want private information available on lets say a user profile screen, to be available to anyone able to modify a URL.' -- 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, 11 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-895) Support re-setting the principal in identity without relogin

by Christian Bauer (JIRA)

Support re-setting the principal in identity without relogin ------------------------------------------------------------ Key: JBSEAM-895 URL: http://jira.jboss.com/jira/browse/JBSEAM-895 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Christian Bauer Assigned To: Shane Bryzak Priority: Minor I'm allow my users to change passwords and usernames while they are logged in. After such a change of credentials, I need to replace the principal in the identity component. This can currently only be done through logout() and login(), manually by the user. I want to do this automatically, and I don't want to destroy the session 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, 11 months

3
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1507) Make Identity usable outside of JSF app

by Gavin King (JIRA)

Make Identity usable outside of JSF app --------------------------------------- Key: JBSEAM-1507 URL: http://jira.jboss.com/jira/browse/JBSEAM-1507 Project: JBoss Seam Issue Type: Feature Request Components: Security Reporter: Gavin King Assigned To: Shane Bryzak Fix For: 1.3.0.BETA2 Currently the Identity class has hard dependencies to JSF classes. This really would not be a big deal except that we cant split it into Identity/FacesIdentity, since it is already split into Identity/RuleBasedIdentity. We would need to split some functionality out to another component. (yick) -- 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, 11 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2071) Introduce log attribute to exception handlers

by Shane Bryzak (JIRA)

Introduce log attribute to exception handlers --------------------------------------------- Key: JBSEAM-2071 URL: http://jira.jboss.com/jira/browse/JBSEAM-2071 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 2.0.0.CR2 Reporter: Shane Bryzak Assigned To: Shane Bryzak Priority: Minor Fix For: 2.0.x As suggested by Gavin in the forum post, we should be able to suppress logging of specific exception types. That way people can decide whether they want NotLoggedInException etc errors cluttering up their log file. <exception class="MyException" log="false"> ... </exception> -- 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, 11 months

6
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1634) More customizable hot redeployment

by Christian Bauer (JIRA)

More customizable hot redeployment ---------------------------------- Key: JBSEAM-1634 URL: http://jira.jboss.com/jira/browse/JBSEAM-1634 Project: JBoss Seam Issue Type: Feature Request Components: Core Reporter: Christian Bauer Priority: Minor Attachments: flexible_hot_redployment.patch The attached patch adds several things: - ability to specify the hot deployment directory as a servlet context init parameter (seam.HOT_DEPLOY_DIRECTORY) - ability to access the used RedeployableStrategy from the application context (to get the classloader, etc) - an additional descriptor (hot-components.xml) that can be used in the hot deploy directory I use this to boot Seam from an embeddable webserver with a custom parent classloader and to start Embedded JBoss with the same child classloader that Seam is using. I effectively get complete hot redeployment of all Seam components, EJBs, and persistence units. -- 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, 11 months

2
2
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues November 2007