July 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-730) User/Role/Permission model

by Gavin King (JIRA)

User/Role/Permission model -------------------------- Key: JBSEAM-730 URL: http://jira.jboss.com/jira/browse/JBSEAM-730 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 an optional component which plugs into Seam/Security to provide the following model: Role (name, description, manager??) User extends Role (password, firstName, lastName, additionalNames, email) RoleRole (role, role) Permission(objectName, operationName) RolePermission(role,permission) RoleInstancePermission(objectName, operationName, objectId) This model would be extensible by the user, simply using inheritance. There would be a built-in management console for creating users and roles and assigning roles and permissions. -- 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

5
8
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1371) Unable to use TestNG groups with SeamTest

by Samuel Mendenhall (JIRA)

Unable to use TestNG groups with SeamTest ----------------------------------------- Key: JBSEAM-1371 URL: http://jira.jboss.com/jira/browse/JBSEAM-1371 Project: JBoss Seam Issue Type: Bug Components: Test Harness Affects Versions: 1.2.1.GA Reporter: Samuel Mendenhall Priority: Minor testng xml in build.xml ++++++++++++++++++++++++++++++ <testng outputdir="${basedir}/test-report" groups="SomeGroups"> <classfileset dir="classes" includes="**/*.class" /> <classpath path="${test.dir}" /> <classpath path="${embedded-ejb3.dir}" /> <classpath refid="build.classpath" /> </testng> ++++++++++++++++++++++++++++++ EmptyTest.java ++++++++++++++++++++++++++++++ public class EmptyTest extends SeamTest { @Test(groups = {"SomeGroups"}) public void testNothing() throws Exception { new FacesRequest() { @Override protected void invokeApplication() throws Exception { assert true; } }.run(); } @Test public void testNothingAgain() throws Exception { assert true; } } ++++++++++++++++++++++++++++++ command: ++++++++++++++++++++++++++++++ ant test ++++++++++++++++++++++++++++++ Exception: ++++++++++++++++++++++++++++++ [testng] java.lang.NullPointerException [testng] at org.jboss.seam.mock.SeamTest$Request.run(SeamTest.java:418) [testng] at com.mydomain.convotest.EmptyTest.testNothing(EmptyTest.java:10) .. ++++++++++++++++++++++++++++++ -- 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

5
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1323) MultipartRequest class incorrectly parses form post when field boundary occurs near end of internal buffer

by ROB b (JIRA)

MultipartRequest class incorrectly parses form post when field boundary occurs near end of internal buffer ---------------------------------------------------------------------------------------------------------- Key: JBSEAM-1323 URL: http://jira.jboss.com/jira/browse/JBSEAM-1323 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA, 1.2.0.GA Environment: Windows Vista, Firefox 2.0.0, Java 1.6u1, JBoss AS 4.0.5.GA, JBoss Seam 1.2.1 Reporter: ROB b Fix For: 1.3.0.BETA1 When a form post is processed by a MultipartRequest class and it has a field boundary that occurs near the end of the internal buffer of the MultipartRequest class, it fails to recognize the field boundary and interprets the field boundary and the following header to be a part of the previous field's contents. This bug can most easily be reproduced by creating a form of enctype="multipart/form-data" with 30 <h:inputText> fields. The fields should be submitted empty. This provides form post data with lots of field boundaries and little in between. One of the field boundaries is likely to be near the end of the 2KB class buffer. When the bug occurs, one of the blank fields will be shown to contain part of the form boundary text. The form may have to be submitted 5 or 10 times, before the bug occurs. This same technique also occasionally causes the JBSEAM-1322 bug to occur (rarely, though). Sorry, I don't have a suggested fix. The class has been kind of hard for me to debug. Submitting the following XHTML source multiple times can be used to demonstrate the bug: <!DOCTYPE composition PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:s="http://jboss.com/products/seam/taglib" xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:f="http://java.sun.com/jsf/core" xmlns:h="http://java.sun.com/jsf/html" xmlns:rich="http://richfaces.ajax4jsf.org/rich" > <h:form enctype="multipart/form-data"> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:inputText /> <h:commandButton /> </h:form> </html> -- 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

4
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-870) Security, login/out and user registration for Wiki

by Gavin King (JIRA)

Security, login/out and user registration for Wiki -------------------------------------------------- Key: JBSEAM-870 URL: http://jira.jboss.com/jira/browse/JBSEAM-870 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Gavin King Assigned To: Christian Bauer We need to integrate Seam security, and add a registration screen with captcha. -- 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

2
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-937) Implement live password strength verification hint

by Christian Bauer (JIRA)

Implement live password strength verification hint -------------------------------------------------- Key: JBSEAM-937 URL: http://jira.jboss.com/jira/browse/JBSEAM-937 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor A little AJAX-driven box next to the password field in registration, showing the strength of the entered password in real-time. Similar to progress bar, uses a couple of increasingly better regexes internally. -- 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

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-912) Add AJAX CLI

by Christian Bauer (JIRA)

Add AJAX CLI ------------ Key: JBSEAM-912 URL: http://jira.jboss.com/jira/browse/JBSEAM-912 Project: JBoss Seam Issue Type: Feature Request Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Priority: Minor A power-user CLI that I can bring up and type in commands in a simple language, with auto-completion and immediate help. Examples "view user christian blog" "edit An Area|This Document" "view This Directory" "create doc An Area|New Document" "create dir An Area|New Directory" "alter menu add This Document" "alter menu remove This Directory" "search doc "Search Terms"" etc. -- 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

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1438) Integrate subetha

by Christian Bauer (JIRA)

Integrate subetha ----------------- Key: JBSEAM-1438 URL: http://jira.jboss.com/jira/browse/JBSEAM-1438 Project: JBoss Seam Issue Type: Task Components: Wiki Reporter: Christian Bauer Assigned To: Christian Bauer Integrate subetha mailing list manager. Probably requires a new ML management interface based on a plugin but using the subetha domain model. -- 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

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1598) include "Clear" button for seam-gen search form

by Dan Allen (JIRA)

include "Clear" button for seam-gen search form ----------------------------------------------- Key: JBSEAM-1598 URL: http://jira.jboss.com/jira/browse/JBSEAM-1598 Project: JBoss Seam Issue Type: Feature Request Components: Tools Affects Versions: 2.0.0.BETA1 Reporter: Dan Allen Priority: Minor The search is a very nice feature to have on the list pages generated by seam-gen, but I have watched people (and struggled myself) with figuring out how to clear the current filter. It is very annoying to have to manually erase all the values entered in the form and then submit the form again once cleared. Far easier would be to have a Clear button on this form. The following button would do the trick. <h:commandButton id="clear" value="Clear" onclick="for (var i = 0, len = this.form.length; i < len; i++) { if (this.form[i].type == 'text') { this.form[i].value = ''; } }" action="/${listPageName}.xhtml"/> I will admit that the JavaScript is a little hacky, but it gets the point across. Feel free to refine. -- 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

3
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1454) DataSource connectionURL property

by Markus Wolf (JIRA)

DataSource connectionURL property --------------------------------- Key: JBSEAM-1454 URL: http://jira.jboss.com/jira/browse/JBSEAM-1454 Project: JBoss Seam Issue Type: Bug Reporter: Markus Wolf Priority: Blocker The datasource connectionURL property does not allow whitespaces around it. It would be better to add a trim for this in the xml parser 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

18 years

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1310) page configuration parameter no-cache

by Leo Baschy (JIRA)

page configuration parameter no-cache ------------------------------------- Key: JBSEAM-1310 URL: http://jira.jboss.com/jira/browse/JBSEAM-1310 Project: JBoss Seam Issue Type: Patch Components: Core Affects Versions: 1.2.1.GA Environment: all Reporter: Leo Baschy Have implemented page configuration parameter no-cache. It effects HTTP headers to say no-cache. Waiting for JBSEAM-1009 to submit a patch because it changes some of the same files as JBSEAM-1009 so it would be a mixed patch unless we'd bother to make a separate copy of the project etc... So if 1009 is in we should follow up with this no-cache patch. For no-cache we've also used the same pattern of allowing more specific paths/directories to override less specific directories, if someone cares to set it that way. Better way. Means DTD must use <!ATTLIST page no-cache (true|false) #IMPLIED> and must NOT be <!ATTLIST page no-cache (true|false) "false"> and internally in Page it is coded to store as object Boolean to allow null if not set, it does NOT store primitive boolean. -- 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

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 July 2007