April 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-990) Check Hotels in Yucatan

by Emmanuel Bernard (JIRA)

Check Hotels in Yucatan ----------------------- Key: JBSEAM-990 URL: http://jira.jboss.com/jira/browse/JBSEAM-990 Project: JBoss Seam Issue Type: Task Affects Versions: 1.2.0.GA, 1.1.7.CR1, 1.1.6.GA, 1.1.5.GA, 1.1.1.GA, 1.1.0.GA, 1.1.0.CR2, 1.1.0.CR1, 1.1.0.BETA2, 1.1.0.BETA1, 1.0.1, 1.0, 1.0 beta 2, 1.0 beta 1 Reporter: Emmanuel Bernard Assigned To: Gavin King Priority: Blocker I can't believe you dared to release the project with such a flaw. It's simply unusable. -- 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, 6 months

3
2
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, 6 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-1156) s:selectDate performs bad when ajaxRendered

by Bram Biesbrouck (JIRA)

s:selectDate performs bad when ajaxRendered ------------------------------------------- Key: JBSEAM-1156 URL: http://jira.jboss.com/jira/browse/JBSEAM-1156 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 1.2.1.GA Environment: Ubuntu Linux (Edgy), Jboss 4.0.5.GA Reporter: Bram Biesbrouck Priority: Minor Noticed a few problems with s:selectDate when it is rendered through ajax. i have the following code Code: <a4j:outputPanel id="details"> <h:inputText id="regDate" <s:convertDateTime pattern="dd/MM/yyyy" /> </h:inputText> <s:selectDate id="selectRegDate" for="regDate" dateFormat="dd/MM/yyyy"> <h:graphicImage url="/images/dtpick.gif" style="margin-left:5px;cursor:pointer" /> </s:selectDate> </a4j:outputPanel> When the outputPanel is rendered using an event from other component with the following code. Code: <a4j:support event="onchange" reRender="details"> The dateformat sometimes defaults to MM/dd/yyyy. and also the selectdate component does not generate any events for validation. i.e i cannot have a4j:support for ajax invocation inside h:inputText -- 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

4
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1208) Improvement for <s:selectDate /> tag

by Richard Leherpeur (JIRA)

Improvement for <s:selectDate /> tag ------------------------------------ Key: JBSEAM-1208 URL: http://jira.jboss.com/jira/browse/JBSEAM-1208 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.2.1.GA Reporter: Richard Leherpeur First when the calendar is open, the user can click anywhere to close it but on the calendar icon. A click to this icon will close the calendar and reopen it right away. I find it a little annoying as instinctively I expect that image to be a toggle button. Also if the page in which the calendar is rendered as a vertical scrollbar, the calendar doesn't "stick" with its associated field but remain static while the user is scrolling. I think this would be less confusing for the user if the calendar remains open where it was open (next the it associated field). Another possibility would be to close the calendar when the user scrolls the page. -- 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
1
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1174) Change s:selectDate to default the date format pattern based on the Seam Locale

by Daniel Young (JIRA)

Change s:selectDate to default the date format pattern based on the Seam Locale ------------------------------------------------------------------------------- Key: JBSEAM-1174 URL: http://jira.jboss.com/jira/browse/JBSEAM-1174 Project: JBoss Seam Issue Type: Feature Request Components: JSF Affects Versions: 1.2.1.GA Reporter: Daniel Young If no pattern is specified, s:selectDate defaults the javascript CAL_DATE_FORMAT to "MM/dd/yyyy". If you use this in conjunction with s:convertDateTime in a locale that uses "dd/MM/yyyy", there calendar behaves very strangely. It should be possible to use s:selectDate and s:convertDateTime together and not have to specify a date pattern. It should default to the correct pattern for that locale. Any application with a locale switcher really needs this behaviour. One open question would be whether to use the FULL, LONG, MEDIUM or SHORT pattern for the locale, perhaps this could be specified as a parameter. The default is generally medium. -- 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
1
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-974) Document Seam dependencies

by Carsten H?hne (JIRA)

Document Seam dependencies -------------------------- Key: JBSEAM-974 URL: http://jira.jboss.com/jira/browse/JBSEAM-974 Project: JBoss Seam Issue Type: Feature Request Components: Documentation Reporter: Carsten H?hne There is a wiki page here: http://wiki.jboss.org/wiki/Wiki.jsp?page=SeamDependencies But this page is not uptodate. I would like to see an apendix to the documentation where all Seam dependencys are described. This appendix can than be updated every new release. -- 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-1261) Pageflow page action is never invoked

by Nathaniel Stoddard (JIRA)

Pageflow page action is never invoked ------------------------------------- Key: JBSEAM-1261 URL: http://jira.jboss.com/jira/browse/JBSEAM-1261 Project: JBoss Seam Issue Type: Bug Components: BPM Affects Versions: 1.2.1.GA Environment: Glassfish on Fedora 6 Reporter: Nathaniel Stoddard For pages that are part of a pageflow defined in a JPDL definition, actions are not invoked. Actions work for transitions, but not for the pages themselves. -- 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
3
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 April 2007