February 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-474) Extending the framework using EJB3 components

by Gavin King (JIRA)

Extending the framework using EJB3 components --------------------------------------------- Key: JBSEAM-474 URL: http://jira.jboss.com/jira/browse/JBSEAM-474 Project: JBoss Seam Issue Type: Feature Request Components: Framework Affects Versions: 1.1.0.BETA1, 1.1.0.BETA2 Reporter: Gavin King Assigned To: Gavin King Priority: Critical Fix For: 1.1.0.CR1 The documentation claims that it is possible to inherit EJB3 components from the framework, but in practice it turns out to not be so easy :-( -- 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 months

6
12
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-660) Externally switching parameters on a form page backed by "page parameters" constructs yields erratic behaviour

by Giampaolo Tomassoni (JIRA)

Externally switching parameters on a form page backed by "page parameters" constructs yields erratic behaviour -------------------------------------------------------------------------------------------------------------- Key: JBSEAM-660 URL: http://jira.jboss.com/jira/browse/JBSEAM-660 Project: JBoss Seam Issue Type: Bug Affects Versions: 1.1.0.GA, 1.1.1.GA, 1.1.5.GA, 1.2.0.BETA1 Environment: JBoss-4.0.5.GA Reporter: Giampaolo Tomassoni When a form with "page parameters" is shown and then the same page but with new parameters is attempted by some external action (in example, by manually changing the parameter values in the browser's navigation bar, the page still holds the previous parameter values. This is particularly annoing in frame-based sites, in which a frame is used to "navigate" on the parameter's space of a form in the right frame. -- 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, 7 months

6
10
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-568) provide a mechanism to split a datetime into date and time components

by Norman Richards (JIRA)

provide a mechanism to split a datetime into date and time components --------------------------------------------------------------------- Key: JBSEAM-568 URL: http://jira.jboss.com/jira/browse/JBSEAM-568 Project: JBoss Seam Issue Type: Feature Request Reporter: Norman Richards We need a way to support splitting a date+time field into separate date and time fields for an input. The datepicker component could be used to select the date while another component (or even a raw input field) could select the time. Ideally this would be generic enough to be used for other types of a conversations: splitting a pure date object into month + day or a time into hours and minutes. -- 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, 7 months

3
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-907) pages.xml ought to accept plain strings as well as valuebindings

by Peter Muir (JIRA)

pages.xml ought to accept plain strings as well as valuebindings ---------------------------------------------------------------- Key: JBSEAM-907 URL: http://jira.jboss.com/jira/browse/JBSEAM-907 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.1.6.GA Reporter: Peter Muir Priority: Minor In JSF in most places you can put a vb you can put a string, but in pages.xml you can't (it blows up if you try). This would be useful e.g. <end-task transition="end" /> or <end-task transition="#{foo.transition}" />. Obviously you can just work around this in the Pages parser (if it starts with #{...) but a general solution would be better IMO -- 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, 7 months

2
2
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-910) s:columns

by Peter Muir (JIRA)

s:columns --------- Key: JBSEAM-910 URL: http://jira.jboss.com/jira/browse/JBSEAM-910 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.1.6.GA Reporter: Peter Muir Assigned To: Peter Muir Priority: Optional Iterate over columns as well as rows (similar to t:columns) -- 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, 7 months

5
7
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

18 years, 8 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

18 years, 8 months

4
13
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-951) IDE support for "Seam Component" project view

by Christian Bauer (JIRA)

IDE support for "Seam Component" project view --------------------------------------------- Key: JBSEAM-951 URL: http://jira.jboss.com/jira/browse/JBSEAM-951 Project: JBoss Seam Issue Type: Feature Request Components: Tools Reporter: Christian Bauer Assigned To: Max Andersen In IntelliJ I can change the project navigator view to different scopes, a scope being a user-defined filter with a package name regex. This is not what I want, I want a project navigator display where the root folders are "Stateless", "Application", "Event", "Conversation", "Session", "Entities", and maybe "Other", and the second grouping is by package name (or whatever custom scope). -- 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, 8 months

2
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-947) Problem with seam component <s:fileUpload/> in JBoss Portal

by Pietro Passantini (JIRA)

Problem with seam component <s:fileUpload/> in JBoss Portal ----------------------------------------------------------- Key: JBSEAM-947 URL: http://jira.jboss.com/jira/browse/JBSEAM-947 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 1.1.6.GA, 1.1.5.GA Environment: Windows XP Pro service pack 2, I.E. and FireFox, JBossAS 4.0.5.GA, JBoss Portal 2.4.1 Reporter: Pietro Passantini I need to upload a file to Jackrabbit Repository using Seam Framework running on Portlet, with the <s:fileUpload/> component. It doesn't work. I've tried different ways to solve the problem, but none worked. It could be a bug. It seams that when the enctype of h:form is ="multipart/form-data", the method upload of fileManager is not called; if I don't set the enctype of h:form the method upload is called, but the bean file is null. I'm trying with this configutaration: JSP <h:form id="myForm" enctype="multipart/form-data" > <s:fileUpload accept="" fileName="#{file.filename}" data="#{file.data}" /> <h:commandButton value="Upload" action="#{fileManager.upload}"/> </h:form> BEAN "file" is the bean that represents the file uploaded "fileManager" is the bean that use the file uploaded WEB.XML ... <filter-name>Seam Filter</filter-name> <filter-class>org.jboss.seam.servlet.SeamMultipartFilter</filter-class> <filter-mapping> <filter-name>Seam Filter</filter-name> <url-pattern>*.seam</url-pattern> </filter-mapping> ... -- 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, 9 months

7
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-761) Modify the default interception practices

by Mike Quilleash (JIRA)

Modify the default interception practices ----------------------------------------- Key: JBSEAM-761 URL: http://jira.jboss.com/jira/browse/JBSEAM-761 Project: JBoss Seam Issue Type: Feature Request Components: Core Affects Versions: 1.1.0.GA Environment: Any. Reporter: Mike Quilleash Currently all methods on a Seam component will be intercepted. In some circumstances this can make debugging difficult as a lot of debuggers call toString() on objects visible from the breakpoint which executes all the Bijection incl the DisInjection which can damage the state of the object depending where the breakpoint is in the process. Perhaps the interception logic could ignore calls to any method on the Object class so the default toString() doesn't cause problems. Another complementary change would be to expand the @Intercept to be allowed on methods (and fields?) to allow the interception logic to be configured on individual methods (like a custom toString()) method. -- 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, 9 months

3
5
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 February 2007