[JBoss JIRA] (WFLY-3767) Update tools/maven handling in 8.x to match master
by Emmanuel Hugonnet (JIRA)
[ https://issues.jboss.org/browse/WFLY-3767?page=com.atlassian.jira.plugin.... ]
Emmanuel Hugonnet reassigned WFLY-3767:
---------------------------------------
Assignee: Emmanuel Hugonnet
> Update tools/maven handling in 8.x to match master
> --------------------------------------------------
>
> Key: WFLY-3767
> URL: https://issues.jboss.org/browse/WFLY-3767
> Project: WildFly
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Brian Stansberry
> Assignee: Emmanuel Hugonnet
> Fix For: 8.2.0.CR1
>
>
> The master branch has had its handling of maven changed such that the maven jars are no longer part of the source repo. This results in hassles when the 8.x branch is checked out in a local git repo, as the maven jars pulled down by the master build are now treated as untracked files by git.
> Task is to make 8.x work like master so these files will be ignored by git.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (WFLY-3100) ClassCastException in JSPs where spring-web tags and jstl tags are used
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3100?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3100:
-----------------------------------------------
baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1075353|https://bugzilla.redhat.com/show_bug.cgi?id=1075353] from POST to MODIFIED
> ClassCastException in JSPs where spring-web tags and jstl tags are used
> -----------------------------------------------------------------------
>
> Key: WFLY-3100
> URL: https://issues.jboss.org/browse/WFLY-3100
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EE, Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: abhishek vijra
> Assignee: Shelly McGowan
> Labels: jsp, jstl
> Fix For: 8.1.0.CR1, 8.1.0.Final
>
> Attachments: spring-fun.war
>
>
> Following JSP with spring tags
> <%@ page contentType="text/html;charset=UTF-8" language="java" %>
> <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
> <%@ taglib prefix="spring" uri="http://www.springframework.org/tags" %>
> <html>
> <head><title>Simple jsp page</title></head>
> <body>
>
> <c:set var="hasError" value="${param.hasError}" />
> <c:set var="msg" value="${param.msg}" />
>
> <c:if test="${param.hasError=='true'}">
> Message: <spring:message text="${param.msg}"/>
> </c:if>
>
> </body>
> </html>
> breaks following error
> ERROR [org.springframework.web.servlet.tags.MessageTag] (default task-1) org.apache.taglibs.standard.lang.jstl.ImplicitObjects cannot be cast to javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects: java.lang.ClassCastException: org.apache.taglibs.standard.lang.jstl.ImplicitObjects cannot be cast to javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects
> at javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects.getImplicitObjects(ImplicitObjectELResolver.java:608) [jboss-jsp-api_2.3_spec-1.0.0.Final.jar:1.0.0.Final]
> at javax.servlet.jsp.el.ImplicitObjectELResolver.getValue(ImplicitObjectELResolver.java:169) [jboss-jsp-api_2.3_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.el.JasperELResolver.getValue(JasperELResolver.java:95) [jastow-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.el.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:32) [jastow-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.el.ELResolverImpl.getValue(ELResolverImpl.java:78) [jastow-1.0.0.Final.jar:1.0.0.Final]
> at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:116) [javax.el-3.0.0.jar:3.0.0]
> at com.sun.el.parser.AstValue.getBase(AstValue.java:151) [javax.el-3.0.0.jar:3.0.0]
> at com.sun.el.parser.AstValue.getValue(AstValue.java:200) [javax.el-3.0.0.jar:3.0.0]
> There are two jars (jboss-jsp-api_2.3_spec-1.0.0.Final.jar and jboss-jstl-api_1.2_spec-1.0.4.Final.jar) that are incompatible with each other due to a bug -- both are storing an object in the same place, but the objects are not compatible.
> The result is that a jsp page cannot contain both JSTL and Spring tags, or it will get that error.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (WFLY-3100) ClassCastException in JSPs where spring-web tags and jstl tags are used
by RH Bugzilla Integration (JIRA)
[ https://issues.jboss.org/browse/WFLY-3100?page=com.atlassian.jira.plugin.... ]
RH Bugzilla Integration commented on WFLY-3100:
-----------------------------------------------
baranowb <bbaranow(a)redhat.com> changed the Status of [bug 1075353|https://bugzilla.redhat.com/show_bug.cgi?id=1075353] from ASSIGNED to POST
> ClassCastException in JSPs where spring-web tags and jstl tags are used
> -----------------------------------------------------------------------
>
> Key: WFLY-3100
> URL: https://issues.jboss.org/browse/WFLY-3100
> Project: WildFly
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: EE, Web (Undertow)
> Affects Versions: 8.0.0.Final
> Reporter: abhishek vijra
> Assignee: Shelly McGowan
> Labels: jsp, jstl
> Fix For: 8.1.0.CR1, 8.1.0.Final
>
> Attachments: spring-fun.war
>
>
> Following JSP with spring tags
> <%@ page contentType="text/html;charset=UTF-8" language="java" %>
> <%@ taglib prefix="c" uri="http://java.sun.com/jstl/core" %>
> <%@ taglib prefix="spring" uri="http://www.springframework.org/tags" %>
> <html>
> <head><title>Simple jsp page</title></head>
> <body>
>
> <c:set var="hasError" value="${param.hasError}" />
> <c:set var="msg" value="${param.msg}" />
>
> <c:if test="${param.hasError=='true'}">
> Message: <spring:message text="${param.msg}"/>
> </c:if>
>
> </body>
> </html>
> breaks following error
> ERROR [org.springframework.web.servlet.tags.MessageTag] (default task-1) org.apache.taglibs.standard.lang.jstl.ImplicitObjects cannot be cast to javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects: java.lang.ClassCastException: org.apache.taglibs.standard.lang.jstl.ImplicitObjects cannot be cast to javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects
> at javax.servlet.jsp.el.ImplicitObjectELResolver$ImplicitObjects.getImplicitObjects(ImplicitObjectELResolver.java:608) [jboss-jsp-api_2.3_spec-1.0.0.Final.jar:1.0.0.Final]
> at javax.servlet.jsp.el.ImplicitObjectELResolver.getValue(ImplicitObjectELResolver.java:169) [jboss-jsp-api_2.3_spec-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.el.JasperELResolver.getValue(JasperELResolver.java:95) [jastow-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.el.VariableResolverImpl.resolveVariable(VariableResolverImpl.java:32) [jastow-1.0.0.Final.jar:1.0.0.Final]
> at org.apache.jasper.el.ELResolverImpl.getValue(ELResolverImpl.java:78) [jastow-1.0.0.Final.jar:1.0.0.Final]
> at com.sun.el.parser.AstIdentifier.getValue(AstIdentifier.java:116) [javax.el-3.0.0.jar:3.0.0]
> at com.sun.el.parser.AstValue.getBase(AstValue.java:151) [javax.el-3.0.0.jar:3.0.0]
> at com.sun.el.parser.AstValue.getValue(AstValue.java:200) [javax.el-3.0.0.jar:3.0.0]
> There are two jars (jboss-jsp-api_2.3_spec-1.0.0.Final.jar and jboss-jstl-api_1.2_spec-1.0.4.Final.jar) that are incompatible with each other due to a bug -- both are storing an object in the same place, but the objects are not compatible.
> The result is that a jsp page cannot contain both JSTL and Spring tags, or it will get that error.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (ELY-47) NFKC normalization in StringPrep is not in accordance with RFC
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-47?page=com.atlassian.jira.plugin.sys... ]
Jan Kalina updated ELY-47:
--------------------------
Description:
StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table:
http://tools.ietf.org/html/rfc3454#appendix-B.2
Relevant profile description:
http://tools.ietf.org/html/rfc3454#section-3.2
Full test is part of [pull request 13|https://github.com/wildfly-security/wildfly-sasl/pull/13], but for basic testing can be used this simple test:
{code:java}
@Test
public void testNormalizationWithNFKC(){
ByteStringBuilder b = new ByteStringBuilder();
String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047";
String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067";
StringPrep.encode(before, b, StringPrep.NORMALIZE_KC);
assertEquals(after, new String(b.toArray()));
}
{code}
was:
StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table:
http://tools.ietf.org/html/rfc3454#appendix-B.2
Relevant profile description:
http://tools.ietf.org/html/rfc3454#section-3.2
Full test is part of [pull request 13|https://github.com/wildfly-security/wildfly-sasl/pull/13], but for basic testing and for reference can be used this simple test:
{code:java}
@Test
public void testNormalizationWithNFKC(){
ByteStringBuilder b = new ByteStringBuilder();
String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047";
String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067";
StringPrep.encode(before, b, StringPrep.NORMALIZE_KC);
assertEquals(after, new String(b.toArray()));
}
{code}
> NFKC normalization in StringPrep is not in accordance with RFC
> --------------------------------------------------------------
>
> Key: ELY-47
> URL: https://issues.jboss.org/browse/ELY-47
> Project: WildFly Elytron
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Jan Kalina
> Assignee: Darran Lofthouse
>
> StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table:
> http://tools.ietf.org/html/rfc3454#appendix-B.2
> Relevant profile description:
> http://tools.ietf.org/html/rfc3454#section-3.2
> Full test is part of [pull request 13|https://github.com/wildfly-security/wildfly-sasl/pull/13], but for basic testing can be used this simple test:
> {code:java}
> @Test
> public void testNormalizationWithNFKC(){
> ByteStringBuilder b = new ByteStringBuilder();
> String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047";
> String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067";
> StringPrep.encode(before, b, StringPrep.NORMALIZE_KC);
> assertEquals(after, new String(b.toArray()));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (ELY-47) NFKC normalization in StringPrep is not in accordance with RFC
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-47?page=com.atlassian.jira.plugin.sys... ]
Jan Kalina updated ELY-47:
--------------------------
Description:
StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table:
http://tools.ietf.org/html/rfc3454#appendix-B.2
Relevant profile description:
http://tools.ietf.org/html/rfc3454#section-3.2
Full test is part of [pull request 13|https://github.com/wildfly-security/wildfly-sasl/pull/13], but for basic testing and for reference can be used this simple test:
{code:java}
@Test
public void testNormalizationWithNFKC(){
ByteStringBuilder b = new ByteStringBuilder();
String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047";
String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067";
StringPrep.encode(before, b, StringPrep.NORMALIZE_KC);
assertEquals(after, new String(b.toArray()));
}
{code}
was:
StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table:
http://tools.ietf.org/html/rfc3454#appendix-B.2
Relevant profile description:
http://tools.ietf.org/html/rfc3454#section-3.2
Full test is part of [pull request|https://github.com/wildfly-security/wildfly-sasl/pull/13], but for basic testing and for reference can be used this simple test:
{code:java}
@Test
public void testNormalizationWithNFKC(){
ByteStringBuilder b = new ByteStringBuilder();
String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047";
String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067";
StringPrep.encode(before, b, StringPrep.NORMALIZE_KC);
assertEquals(after, new String(b.toArray()));
}
{code}
> NFKC normalization in StringPrep is not in accordance with RFC
> --------------------------------------------------------------
>
> Key: ELY-47
> URL: https://issues.jboss.org/browse/ELY-47
> Project: WildFly Elytron
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Jan Kalina
> Assignee: Darran Lofthouse
>
> StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table:
> http://tools.ietf.org/html/rfc3454#appendix-B.2
> Relevant profile description:
> http://tools.ietf.org/html/rfc3454#section-3.2
> Full test is part of [pull request 13|https://github.com/wildfly-security/wildfly-sasl/pull/13], but for basic testing and for reference can be used this simple test:
> {code:java}
> @Test
> public void testNormalizationWithNFKC(){
> ByteStringBuilder b = new ByteStringBuilder();
> String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047";
> String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067";
> StringPrep.encode(before, b, StringPrep.NORMALIZE_KC);
> assertEquals(after, new String(b.toArray()));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (ELY-47) NFKC normalization in StringPrep is not in accordance with RFC
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-47?page=com.atlassian.jira.plugin.sys... ]
Jan Kalina updated ELY-47:
--------------------------
Description:
StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table:
http://tools.ietf.org/html/rfc3454#appendix-B.2
Relevant profile description:
http://tools.ietf.org/html/rfc3454#section-3.2
Full test is part of [pull request|https://github.com/wildfly-security/wildfly-sasl/pull/13], but for basic testing and for reference can be used this simple test:
{code:java}
@Test
public void testNormalizationWithNFKC(){
ByteStringBuilder b = new ByteStringBuilder();
String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047";
String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067";
StringPrep.encode(before, b, StringPrep.NORMALIZE_KC);
assertEquals(after, new String(b.toArray()));
}
{code}
was:
StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table:
http://tools.ietf.org/html/rfc3454#appendix-B.2
Relevant profile description:
http://tools.ietf.org/html/rfc3454#section-3.2
Full test is part of pull request https://github.com/wildfly-security/wildfly-sasl/pull/13, but for basic testing and for reference can be used this simple test:
{code:java}
@Test
public void testNormalizationWithNFKC(){
ByteStringBuilder b = new ByteStringBuilder();
String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047";
String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067";
StringPrep.encode(before, b, StringPrep.NORMALIZE_KC);
assertEquals(after, new String(b.toArray()));
}
{code}
> NFKC normalization in StringPrep is not in accordance with RFC
> --------------------------------------------------------------
>
> Key: ELY-47
> URL: https://issues.jboss.org/browse/ELY-47
> Project: WildFly Elytron
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Jan Kalina
> Assignee: Darran Lofthouse
>
> StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table:
> http://tools.ietf.org/html/rfc3454#appendix-B.2
> Relevant profile description:
> http://tools.ietf.org/html/rfc3454#section-3.2
> Full test is part of [pull request|https://github.com/wildfly-security/wildfly-sasl/pull/13], but for basic testing and for reference can be used this simple test:
> {code:java}
> @Test
> public void testNormalizationWithNFKC(){
> ByteStringBuilder b = new ByteStringBuilder();
> String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047";
> String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067";
> StringPrep.encode(before, b, StringPrep.NORMALIZE_KC);
> assertEquals(after, new String(b.toArray()));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months
[JBoss JIRA] (ELY-47) NFKC normalization in StringPrep is not in accordance with RFC
by Jan Kalina (JIRA)
[ https://issues.jboss.org/browse/ELY-47?page=com.atlassian.jira.plugin.sys... ]
Jan Kalina edited comment on ELY-47 at 8/26/14 4:34 AM:
--------------------------------------------------------
Here was misunderstand function of *NORMALIZE_KC* profile - this profile do only NFKC normalization, not case folding, which test expected.
Case folding is not implemented in StringPrep yet, so I keep full test of case folding ignored in [pull request|https://github.com/wildfly-security/wildfly-sasl/pull/13] for needs of implementing it.
was (Author: honza889):
Here was misunderstand function of *NORMALIZE_KC* profile - this profile do only NFKC normalization, not case folding, which test expected.
Case folding is not implemented in StringPrep yet, so I keep full test of case folding ignored in [[pull request|https://github.com/wildfly-security/wildfly-sasl/pull/13]] for needs of implementing it.
> NFKC normalization in StringPrep is not in accordance with RFC
> --------------------------------------------------------------
>
> Key: ELY-47
> URL: https://issues.jboss.org/browse/ELY-47
> Project: WildFly Elytron
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Reporter: Jan Kalina
> Assignee: Darran Lofthouse
>
> StringPrep from utils use java.text.Normalizer to NFKC normalization. But this normalization is not in accordance with RFC 3454 - see mapping table:
> http://tools.ietf.org/html/rfc3454#appendix-B.2
> Relevant profile description:
> http://tools.ietf.org/html/rfc3454#section-3.2
> Full test is part of pull request https://github.com/wildfly-security/wildfly-sasl/pull/13, but for basic testing and for reference can be used this simple test:
> {code:java}
> @Test
> public void testNormalizationWithNFKC(){
> ByteStringBuilder b = new ByteStringBuilder();
> String before = "\u0041\u0042\u0043\u0044\u0045\u0046\u0047";
> String after = "\u0061\u0062\u0063\u0064\u0065\u0066\u0067";
> StringPrep.encode(before, b, StringPrep.NORMALIZE_KC);
> assertEquals(after, new String(b.toArray()));
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 2 months