February 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-6267) JSTL will fail with tags using x:out nested in a x:forEach

by Matthew Casperson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6267?page=com.atlassian.jira.plugin.... ] Matthew Casperson updated WFLY-6267: ------------------------------------ Description: See https://github.com/mcasperson/wildfly_jstl_bug/ What happens is you have a x:forEach in a JSP page. Inside this x:forEach you call a tag that itself has a x:forEach. The variable created by the second x:forEach is inaccessible to any nested x:out elements. This happens because the x:out pageContext is actually linked to the pageContext from the jsp page, which doesn't hold any variables created by the x:whatever elements in the tag file. See https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... and https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... for more details. was: See https://github.com/mcasperson/wildfly_jstl_bug/ What happens is you have a x:forEach in a JSP page. Inside this x:forEach you call a tag that itself has a x:forEach. The variable created by the second x:forEach is inaccessible to any nested x:out elements. This happens because the x:out pageContext is actually linked to the pageContext from the jsp page. See https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... and https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... for more details. > JSTL will fail with tags using x:out nested in a x:forEach > ---------------------------------------------------------- > > Key: WFLY-6267 > URL: https://issues.jboss.org/browse/WFLY-6267 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Matthew Casperson > Assignee: Stuart Douglas > > See https://github.com/mcasperson/wildfly_jstl_bug/ > What happens is you have a x:forEach in a JSP page. Inside this x:forEach you call a tag that itself has a x:forEach. The variable created by the second x:forEach is inaccessible to any nested x:out elements. > This happens because the x:out pageContext is actually linked to the pageContext from the jsp page, which doesn't hold any variables created by the x:whatever elements in the tag file. > See https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... and https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6267) JSTL will fail with tags using x:out nested in a x:forEach

by Matthew Casperson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6267?page=com.atlassian.jira.plugin.... ] Matthew Casperson updated WFLY-6267: ------------------------------------ Description: See https://github.com/mcasperson/wildfly_jstl_bug/ What happens is you have a x:forEach in a JSP page. Inside this x:forEach you call a tag that itself has a x:forEach. The variable created by the second x:forEach is inaccessible to any nested x:out elements. This happens because the x:out pageContext is actually linked to the pageContext from the jsp page. See https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... for more details. > JSTL will fail with tags using x:out nested in a x:forEach > ---------------------------------------------------------- > > Key: WFLY-6267 > URL: https://issues.jboss.org/browse/WFLY-6267 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Matthew Casperson > Assignee: Stuart Douglas > > See https://github.com/mcasperson/wildfly_jstl_bug/ > What happens is you have a x:forEach in a JSP page. Inside this x:forEach you call a tag that itself has a x:forEach. The variable created by the second x:forEach is inaccessible to any nested x:out elements. > This happens because the x:out pageContext is actually linked to the pageContext from the jsp page. > See https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6267) JSTL will fail with tags using x:out nested in a x:forEach

by Matthew Casperson (JIRA)

[ https://issues.jboss.org/browse/WFLY-6267?page=com.atlassian.jira.plugin.... ] Matthew Casperson updated WFLY-6267: ------------------------------------ Description: See https://github.com/mcasperson/wildfly_jstl_bug/ What happens is you have a x:forEach in a JSP page. Inside this x:forEach you call a tag that itself has a x:forEach. The variable created by the second x:forEach is inaccessible to any nested x:out elements. This happens because the x:out pageContext is actually linked to the pageContext from the jsp page. See https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... and https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... for more details. was: See https://github.com/mcasperson/wildfly_jstl_bug/ What happens is you have a x:forEach in a JSP page. Inside this x:forEach you call a tag that itself has a x:forEach. The variable created by the second x:forEach is inaccessible to any nested x:out elements. This happens because the x:out pageContext is actually linked to the pageContext from the jsp page. See https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... for more details. > JSTL will fail with tags using x:out nested in a x:forEach > ---------------------------------------------------------- > > Key: WFLY-6267 > URL: https://issues.jboss.org/browse/WFLY-6267 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Reporter: Matthew Casperson > Assignee: Stuart Douglas > > See https://github.com/mcasperson/wildfly_jstl_bug/ > What happens is you have a x:forEach in a JSP page. Inside this x:forEach you call a tag that itself has a x:forEach. The variable created by the second x:forEach is inaccessible to any nested x:out elements. > This happens because the x:out pageContext is actually linked to the pageContext from the jsp page. > See https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... and https://github.com/mcasperson/wildfly_jstl_bug/blob/master/src/main/webap... for more details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6267) JSTL will fail with tags using x:out nested in a x:forEach

by Matthew Casperson (JIRA)

Matthew Casperson created WFLY-6267: --------------------------------------- Summary: JSTL will fail with tags using x:out nested in a x:forEach Key: WFLY-6267 URL: https://issues.jboss.org/browse/WFLY-6267 Project: WildFly Issue Type: Bug Components: Web (Undertow) Reporter: Matthew Casperson Assignee: Stuart Douglas -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-14) Conflicting feature pack dependency versions should not be allowed

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFBUILD-14?page=com.atlassian.jira.plugin... ] Stuart Douglas resolved WFBUILD-14. ----------------------------------- Fix Version/s: 1.1.7.Final Resolution: Done > Conflicting feature pack dependency versions should not be allowed > ------------------------------------------------------------------ > > Key: WFBUILD-14 > URL: https://issues.jboss.org/browse/WFBUILD-14 > Project: WildFly Build Tools > Issue Type: Bug > Reporter: James Netherton > Assignee: Stuart Douglas > Fix For: 1.1.7.Final > > > There was a brief discussion about this on the WildFly dev mailing list so I'm capturing the problem here as well. > Consider the following. > Feature pack 'A' has a dependency on the WildFly 9 feature pack. E.g: > {code:xml} > <dependencies> > <artifact name="org.wildfly:wildfly-feature-pack:9.0.1.Final" /> > </dependencies> > {code} > Feature pack 'B' has a dependency on the WildFly 10 feature pack and also on feature pack 'A'. E.g: > {code:xml} > <dependencies> > <artifact name="org.wildfly:wildfly-feature-pack:10.0.0.CR3" /> > <artifact name="org.foo:feature-pack-A" /> > </dependencies> > {code} > The result is that you'll have overlapping and possibly problematic non-overlapping file paths coming from the conflicting WildFly versions > At the moment the plugins allow this scenario, which can lead to all sorts of horrors when using the server-provisioning plugin to provision an app server. > CrossRef: https://github.com/wildfly-extras/fuse-patch/issues/101 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6266) Allow for millisecond resolution for access log entries via %t formatting

by Stuart Douglas (JIRA)

[ https://issues.jboss.org/browse/WFLY-6266?page=com.atlassian.jira.plugin.... ] Stuart Douglas resolved WFLY-6266. ---------------------------------- Resolution: Out of Date Should be already available via %{time,[dd/MMM/yyyy:HH:mm:ss.S Z]} Basically you should able to pass in any format that is understood by SimpleDataFormat > Allow for millisecond resolution for access log entries via %t formatting > ------------------------------------------------------------------------- > > Key: WFLY-6266 > URL: https://issues.jboss.org/browse/WFLY-6266 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Travis Rogers > Assignee: Stuart Douglas > > Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the [capabilities provided by Apache|http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats] via the formatting: {code}%{msec}t{code} > It gets difficult to correlate times across servers when you don’t have millisecond granularity. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6266) Allow for millisecond resolution for access log entries via %t formatting

by Travis Rogers (JIRA)

[ https://issues.jboss.org/browse/WFLY-6266?page=com.atlassian.jira.plugin.... ] Travis Rogers updated WFLY-6266: -------------------------------- Description: Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the [capabilities provided by Apache|http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats] via the formatting: {code}%{msec}t{code} It gets difficult to correlate times across servers when you don’t have millisecond granularity. was: Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the capabilities provided by Apache [1] via the formatting. It gets difficult to correlate times across servers when you don’t have millisecond granularity. [1] http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats > Allow for millisecond resolution for access log entries via %t formatting > ------------------------------------------------------------------------- > > Key: WFLY-6266 > URL: https://issues.jboss.org/browse/WFLY-6266 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Travis Rogers > Assignee: Stuart Douglas > > Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the [capabilities provided by Apache|http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats] via the formatting: {code}%{msec}t{code} > It gets difficult to correlate times across servers when you don’t have millisecond granularity. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6266) Allow for millisecond resolution for access log entries via %t formatting

by Travis Rogers (JIRA)

[ https://issues.jboss.org/browse/WFLY-6266?page=com.atlassian.jira.plugin.... ] Travis Rogers updated WFLY-6266: -------------------------------- Description: Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the capabilities provided by Apache [1] via the formatting. It gets difficult to correlate times across servers when you don’t have millisecond granularity. [1] http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats was: Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the capabilities provided by Apache [1] via the formatting: {{%{msec}t}} It gets difficult to correlate times across servers when you don’t have millisecond granularity. [1] http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats > Allow for millisecond resolution for access log entries via %t formatting > ------------------------------------------------------------------------- > > Key: WFLY-6266 > URL: https://issues.jboss.org/browse/WFLY-6266 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Travis Rogers > Assignee: Stuart Douglas > > Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the capabilities provided by Apache [1] via the formatting. > It gets difficult to correlate times across servers when you don’t have millisecond granularity. > [1] > http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6266) Allow for millisecond resolution for access log entries via %t formatting

by Travis Rogers (JIRA)

[ https://issues.jboss.org/browse/WFLY-6266?page=com.atlassian.jira.plugin.... ] Travis Rogers updated WFLY-6266: -------------------------------- Description: Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the capabilities provided by Apache [1] via the formatting `%{msec}t`. It gets difficult to correlate times across servers when you don’t have millisecond granularity. [1] http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats was: Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the capabilities provided by Apache [1] via the % {msec}t formatting . It gets difficult to correlate times across servers when you don’t have millisecond granularity. [1] http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats > Allow for millisecond resolution for access log entries via %t formatting > ------------------------------------------------------------------------- > > Key: WFLY-6266 > URL: https://issues.jboss.org/browse/WFLY-6266 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Travis Rogers > Assignee: Stuart Douglas > > Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the capabilities provided by Apache [1] via the formatting `%{msec}t`. > It gets difficult to correlate times across servers when you don’t have millisecond granularity. > [1] > http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (WFLY-6266) Allow for millisecond resolution for access log entries via %t formatting

by Travis Rogers (JIRA)

[ https://issues.jboss.org/browse/WFLY-6266?page=com.atlassian.jira.plugin.... ] Travis Rogers updated WFLY-6266: -------------------------------- Description: Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the capabilities provided by Apache [1] via the formatting: {{%{msec}t}} It gets difficult to correlate times across servers when you don’t have millisecond granularity. [1] http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats was: Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the capabilities provided by Apache [1] via the formatting `%{msec}t`. It gets difficult to correlate times across servers when you don’t have millisecond granularity. [1] http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats > Allow for millisecond resolution for access log entries via %t formatting > ------------------------------------------------------------------------- > > Key: WFLY-6266 > URL: https://issues.jboss.org/browse/WFLY-6266 > Project: WildFly > Issue Type: Feature Request > Components: Web (Undertow) > Affects Versions: 10.0.0.Final > Reporter: Travis Rogers > Assignee: Stuart Douglas > > Currently Undertow supports access logging where the common log format time is written with each log entry. It's desirable to be able to capture millisecond resolution on the time stamps for access log entries similar to the capabilities provided by Apache [1] via the formatting: > {{%{msec}t}} > It gets difficult to correlate times across servers when you don’t have millisecond granularity. > [1] > http://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira February 2016