December 2008 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-355) Constructor injection of component dependencies

by Jeremy Norris (JIRA)

[ https://jira.jboss.org/jira/browse/JBSEAM-355?page=com.atlassian.jira.plu... ] Jeremy Norris commented on JBSEAM-355: -------------------------------------- Gavin, you mentioned there is a reason why EJB3 doesn't support constructor injection. What is this reason? Is it a technical reason? Interestingly, Apache OpenEJB 3.1 supports constructor injection (http://www.infoq.com/news/2008/11/openejb-3.1-release). > Constructor injection of component dependencies > ----------------------------------------------- > > Key: JBSEAM-355 > URL: https://jira.jboss.org/jira/browse/JBSEAM-355 > Project: Seam > Issue Type: Feature Request > Components: Core > Reporter: Christian Bauer > Priority: Minor > > Take the registration example. The 'user' component is instantiated by Seam when JSF first looks for 'user' in a page. It is then put in the SESSION context (think CONVERSATION for other use cases of what I'm proposing). Seam uses the default constructor to instantiate the component. > Now imagine that some attributes of User are immutable and that the only way to set their values is through a different constructor. Also imagine that these values are actually present when Seam instantiates the 'user' component, e.g. in the current CONVERSATION. I'd like to tell Seam to call my constructor and use EL to bind the arguments. > Without this feature, immutable properties need to have public setter methods that I call later in an action method to wire in the required attributes manually. -- 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

15 years, 6 months

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3855) seam-gen pages.xml file is invalid, and contains "logLevel" instead of "log-level"

by Jay Balunas (JIRA)

seam-gen pages.xml file is invalid, and contains "logLevel" instead of "log-level" ---------------------------------------------------------------------------------- Key: JBSEAM-3855 URL: https://jira.jboss.org/jira/browse/JBSEAM-3855 Project: Seam Issue Type: Bug Components: Core Affects Versions: 2.1.1.GA Reporter: Jay Balunas Priority: Critical Fix For: 2.1.1.GA This can be reproduced by executing "ant validate" in a seam-gen project. It looks like r9777 did not make it into the tag at r9762. It should be as easy as merging this into the tag to solve this issue. -- 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

15 years, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3846) Authentication with identity management for abstract User

by Emil Iakoupov (JIRA)

Authentication with identity management for abstract User ---------------------------------------------------------- Key: JBSEAM-3846 URL: https://jira.jboss.org/jira/browse/JBSEAM-3846 Project: Seam Issue Type: Feature Request Components: Framework Affects Versions: 2.1.0.SP1 Environment: any Reporter: Emil Iakoupov Priority: Optional Hello, i ran into a little concern. I really want to use identity management. I have inheritence for Users. That is User is an abstract class and its children are different type of users. It basically has credentials (username, password and other option relevant to a user as a whole). Now how do i identityManagement.createUser? Since there could as many flows as types of users and for user-class i definately have to specify the User. I can always register a new user by persisting him/her to db, and then call identityManager.createUser? Would't second call return fallse? Having only one type of user for whole application would greatly complicate design. If you have any suggestions... -- 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

15 years, 6 months

1
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3066) Include JBoss 5 compatible version of Facelets

by Pete Muir (JIRA)

Include JBoss 5 compatible version of Facelets ---------------------------------------------- Key: JBSEAM-3066 URL: http://jira.jboss.com/jira/browse/JBSEAM-3066 Project: Seam Issue Type: Task Affects Versions: 2.0.2.SP1 Reporter: Pete Muir Assigned To: Jay Balunas Priority: Blocker Fix For: 2.0.3.CR1 -- 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

15 years, 6 months

3
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3602) examle seambay - can't register new user

by Marek Novotny (JIRA)

examle seambay - can't register new user ---------------------------------------- Key: JBSEAM-3602 URL: https://jira.jboss.org/jira/browse/JBSEAM-3602 Project: Seam Issue Type: Bug Affects Versions: 2.1.0.GA Environment: java 6, jboss 4.2.3 Reporter: Marek Novotny After filling registration form with user data and submitting the form it shows message Login failed and the user is not created. -- 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

15 years, 6 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2197) interpolate swallows FormatType and FormatStyle of MessageFormat

by Martin Trummer (JIRA)

interpolate swallows FormatType and FormatStyle of MessageFormat ---------------------------------------------------------------- Key: JBSEAM-2197 URL: http://jira.jboss.com/jira/browse/JBSEAM-2197 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.CR2 Environment: Application Server: jboss-4.2.0.GA Operating System: Windows XP Java: 1.6 Reporter: Martin Trummer Testcode: String source = "{0,number,#.#}"; String interpolated = Interpolator.instance().interpolate(source); System.out.println("soruce: '"+source+"'"); System.out.println("interpolated: '"+interpolated+"'"); Output is: 17:02:00,133 INFO [STDOUT] soruce: '{0,number,#.#}' 17:02:00,133 INFO [STDOUT] interpolated: '{0}' Expected output: 17:02:00,133 INFO [STDOUT] soruce: '{0,number,#.#}' 17:02:00,133 INFO [STDOUT] interpolated: '{0,number,#.#}' The interpolate() function should not swallow the FormatType and FormatStyle. Details can be found in the Forum Discussion -- 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

15 years, 6 months

5
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3847) Bad code indentation in translated manuals

by Nicola Benaglia (JIRA)

Bad code indentation in translated manuals ------------------------------------------ Key: JBSEAM-3847 URL: https://jira.jboss.org/jira/browse/JBSEAM-3847 Project: Seam Issue Type: Bug Components: Documentation Translation Environment: Ubuntu 8.04 Sun JDK 1.6.0.07 Reporter: Nicola Benaglia Priority: Trivial Translating into italian I copy all the code without translation. The translated manual has a lot of such copied copy not well-indented. Example: ------------------------------------------------------------------------- <pages> <page view-id="/hello.jsp" action="#{helloWorld.sayHello}"/> </pages > ---------------------------(note the last > at new line)---------- Some time is okay. Looking at the PO file I see that it's OKAY when: "<![CDATA[<pages>\n" " <page view-id=\"/hello.jsp\" action=\"#{helloWorld.sayHello}\"/>\n" "</pages>\n" "]]>" And it's WRONG when: "<![CDATA[<pages>\n" " <page view-id=\"/hello.jsp\" action=\"#{helloWorld.sayHello}\"/>\n" "</pages>]]>" i.e. it depends on ]]>, which must be at a new line. Bye, Nico -- 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

15 years, 6 months

2
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3448) MultipartFilter does not begin parsing until after transaction is started

by Clint Popetz (JIRA)

MultipartFilter does not begin parsing until after transaction is started ------------------------------------------------------------------------- Key: JBSEAM-3448 URL: https://jira.jboss.org/jira/browse/JBSEAM-3448 Project: Seam Issue Type: Bug Reporter: Clint Popetz Currently the multipart filter creates the request wrapper upon detecting a multipart post, but does not actually begin processing until the first time someone asks it for a parameter. This means that upon such a POST, multipart processing won't begin until after the transaction has been created by the SeamPhaseListener, and thus for large uploads (and/or slow network connections) it's very easy to exceed the transaction timeout, leading to failed uploads. I think that MultipartFilter should call getParam("") before invoking the rest of the chain so that the upload/parsing happen before the tx is created. -- 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

15 years, 6 months

3
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3459) IE6 (very specific version) Crash on Seam Remoting Callback

by Anthony Kitchin (JIRA)

IE6 (very specific version) Crash on Seam Remoting Callback ----------------------------------------------------------- Key: JBSEAM-3459 URL: https://jira.jboss.org/jira/browse/JBSEAM-3459 Project: Seam Issue Type: Bug Components: Remoting Affects Versions: 2.0.1.GA Environment: Microsoft Windows XP - Professional IE 6.0.2900.2180.xpsp_sp2_gdr.070227-2254 Intel (R) Core(TM) 2 Duo CPU (1.80Ghz) 1.99Gb of RAM Reporter: Anthony Kitchin Assignee: Shane Bryzak I tracked the issue down to one line of javascript code in remote.js req.onreadystatechange = function() {}; The following thread discusses the problem is with an old version of the JScript.dll 5.6.0.8820 which is the same version I've got on a laptop here. http://groups.google.com/group/Google-Web-Toolkit/browse_thread/thread/69... One solution is to upgrade JScript.dll to 5.6.0.8831 http://www.microsoft.com/technet/security/bulletin/ms06-023.mspx Or we can do what they did in GWT which is to move the req.onreadystatechange out of the scope of the current function window.setTimeout(function() { req.onreadystatechange = function() {}; }, 0 ); -- 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

15 years, 6 months

6
6
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-3843) Seamspace example - pages.xml uses logLevel attribute

by Jozef Hartinger (JIRA)

Seamspace example - pages.xml uses logLevel attribute ----------------------------------------------------- Key: JBSEAM-3843 URL: https://jira.jboss.org/jira/browse/JBSEAM-3843 Project: Seam Issue Type: Bug Components: Examples Affects Versions: 2.1.1.GA Reporter: Jozef Hartinger Assignee: Shane Bryzak Fix For: 2.1.1.GA According to recent schema changes log-level attribute should be used instead of logLevel. -- 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

15 years, 6 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues December 2008