September 2007 - seam-issues - Jboss List Archives

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1639) <s:selectDate javascript error

by Paul Thorp (JIRA)

<s:selectDate javascript error ------------------------------ Key: JBSEAM-1639 URL: http://jira.jboss.com/jira/browse/JBSEAM-1639 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.BETA1 Environment: Windows XP, JBoss 4.2 Reporter: Paul Thorp A javascript error is thrown (line 459) when the calendar icon is clicked, using IE7, and no calendar is displayed. Firefox 2.0 did not throw the error and displayed the calendar popup. -- 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
2
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-1763) Renable description elements in converters and validators

by Pete Muir (JIRA)

Renable description elements in converters and validators --------------------------------------------------------- Key: JBSEAM-1763 URL: http://jira.jboss.com/jira/browse/JBSEAM-1763 Project: JBoss Seam Issue Type: Task Components: JSF Reporter: Pete Muir Assigned To: Pete Muir Priority: Trivial -- 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

1
4
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1761) Remove EntityConverterTag

by Pete Muir (JIRA)

Remove EntityConverterTag ------------------------- Key: JBSEAM-1761 URL: http://jira.jboss.com/jira/browse/JBSEAM-1761 Project: JBoss Seam Issue Type: Task Components: JSF Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Assigned To: Pete Muir Priority: Minor This is a workaround, and can be removed when we next upgrade the CDK. -- 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

1
3
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1904) calendar.js has script error on IE 6&7

by Chris Rudd (JIRA)

calendar.js has script error on IE 6&7 -------------------------------------- Key: JBSEAM-1904 URL: http://jira.jboss.com/jira/browse/JBSEAM-1904 Project: JBoss Seam Issue Type: Bug Components: JSF Affects Versions: 2.0.0.BETA1 Reporter: Chris Rudd Line 458 causes an error in IE 6 & 7 if( divs[i] != popupDiv && divs[i].style && !/\d/(divs[i].style.zIndex)) Im assuming the code is attempting to say if its not a number.. so this should be the equivelant (verified on both IE and Firefox) if( divs[i] != popupDiv && divs[i].style && isNaN(parseInt(divs[i].style.zIndex)) ) -- 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-1860) login-required and no-conversation-view-id causing infinite redirect on POST request after session timeout

by Jacob Orshalick (JIRA)

login-required and no-conversation-view-id causing infinite redirect on POST request after session timeout ---------------------------------------------------------------------------------------------------------- Key: JBSEAM-1860 URL: http://jira.jboss.com/jira/browse/JBSEAM-1860 Project: JBoss Seam Issue Type: Bug Affects Versions: 2.0.0.BETA1 Reporter: Jacob Orshalick When a page is setup as login-required="true" in pages.xml and a no-conversation-view-id is specified an infinite redirect occurs if the session times out and a POST request is then made by the user. Here is a snippet of my pages.xml configuration: <pages login-view-id="/common/login.jsp">  <page view-id="*" scheme="http"/> <page view-id="/administration/*" scheme="http" login-required="true"> <restrict>#{s:hasRole('Administrator')}</restrict> </page> <page view-id="/status/*" login-required="true" no-conversation-view-id="/status/search.xhtml"> <restrict>#{s:hasRole('appRole')}</restrict> </page> When accessing a page under /status/* the first access always redirects to login.jsp as expected. The user then logs in and continues working with the application. If the HTTP session is then allowed to timeout, a GET request will behave as expected and redirect to the login.jsp. A POST on the other hand will cause an infinite redirect. The stacktrace can be found at the forum reference. If the no-conversation-view-id is removed, the redirect works as expected but or course an error occurs if you return to a page that requires a conversation after logging in. -- 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
11
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1877) s:link, PAGE scope and datamodelselection

by Pete Muir (JIRA)

s:link, PAGE scope and datamodelselection ----------------------------------------- Key: JBSEAM-1877 URL: http://jira.jboss.com/jira/browse/JBSEAM-1877 Project: JBoss Seam Issue Type: Bug Components: Core Affects Versions: 2.0.0.BETA1 Reporter: Pete Muir Fix For: 2.0.0.CR1 If an s:link is used then the datamodel isn't available in the page context in injectDataModelSelection. This is fine if h:commandLink is used. -- 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
5
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1903) Facelets EL functions do not work

by Martin Kouba (JIRA)

Facelets EL functions do not work --------------------------------- Key: JBSEAM-1903 URL: http://jira.jboss.com/jira/browse/JBSEAM-1903 Project: JBoss Seam Issue Type: Bug Components: EL, JSF Affects Versions: 1.2.1.GA Environment: Linux 2.6.20-16-generic (i386) JBoss AS 4.2.0.GA JSF 1.2 (Sun) 1.2_04 Facelets 1.1.12 Ajax4jsf 1.1.1 Richfaces 3.0.1 Reporter: Martin Kouba Facelets EL functions do not work after form submit (both normal and ajax). It is certainly classloading problem - org.apache.el tries to load EL function impl. class but there is no appropriate classloader. I studied JBoss classloading model and probed various configurations - without result. 10:22:56,291 ERROR [STDERR] java.lang.ClassNotFoundException: No ClassLoaders found for: cz.mydomain.CoreELFunctions 10:22:56,293 ERROR [STDERR] at org.jboss.mx.loading.LoadMgr3.beginLoadTask(LoadMgr3.java:212) 10:22:56,293 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClassImpl(RepositoryClassLoader.java:514) 10:22:56,293 ERROR [STDERR] at org.jboss.mx.loading.RepositoryClassLoader.loadClass(RepositoryClassLoader.java:408) 10:22:56,293 ERROR [STDERR] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) 10:22:56,293 ERROR [STDERR] at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) 10:22:56,293 ERROR [STDERR] at java.lang.Class.forName0(Native Method) 10:22:56,293 ERROR [STDERR] at java.lang.Class.forName(Class.java:164) 10:22:56,293 ERROR [STDERR] at org.apache.el.lang.FunctionMapperImpl$Function.getMethod(FunctionMapperImpl.java:147) 10:22:56,294 ERROR [STDERR] at org.apache.el.lang.FunctionMapperImpl.resolveFunction(FunctionMapperImpl.java:53) 10:22:56,294 ERROR [STDERR] at org.apache.el.parser.AstFunction.getValue(AstFunction.java:71) 10:22:56,294 ERROR [STDERR] at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:186) 10:22:56,294 ERROR [STDERR] at com.sun.facelets.el.TagValueExpression.getValue(TagValueExpression.java:71) It is somehow related to bug JBSEAM-1179. However this bug does not offer any solution. -- 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] Commented: (JBSEAM-341) Support for Regex-es in pages.xml

by Pierre Raoul (JIRA)

[ http://jira.jboss.com/jira/browse/JBSEAM-341?page=comments#action_12375297 ] Pierre Raoul commented on JBSEAM-341: ------------------------------------- I just finished to implement an alternative to current wildcards: - by default it's still the final "*" - or, if specified in component configuration, full Ant path wildcards About Regex: i don't see how to order the priority of patterns when many of them can be applied to the same viewId. Any idea? > Support for Regex-es in pages.xml > --------------------------------- > > Key: JBSEAM-341 > URL: http://jira.jboss.com/jira/browse/JBSEAM-341 > Project: JBoss Seam > Issue Type: Feature Request > Components: JSF > Reporter: Raja > > Currently the pages.xml supports wildcards but that too very limited(ending with *). If we have support for Regex-es in pages.xml , that would help the developers write page actions that can match a particular viewid. > For e.g. I was trying to create a filter that will make my application go to the login page for any request but the login.seam page. Having a regex support for pages.xml will make this easier. > An alternative solution would be to have an except attribute that indicates that the page actions should be performed for all the view-ids that match it but except the ones in the "except" attribute. -- 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

1
0
0 / 0

[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-1894) missing a:support for BigInteger in editproperty.xhtml.ftl

by Pierre Raoul (JIRA)

missing a:support for BigInteger in editproperty.xhtml.ftl ---------------------------------------------------------- Key: JBSEAM-1894 URL: http://jira.jboss.com/jira/browse/JBSEAM-1894 Project: JBoss Seam Issue Type: Bug Components: Tools Affects Versions: 2.0.0.BETA1 Reporter: Pierre Raoul Attachments: SeamGenBigInteger.diff In editproperty.xhtml.ftl, in the second occurrence of big_integer input, there is no a:support. -- 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

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

seam-issues September 2007