[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
[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">
<!-- Security configuration -->
<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
[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
[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