You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Neil Griffin (Jira)" <ji...@apache.org> on 2023/12/08 16:32:00 UTC
[jira] [Created] (PLUTO-805) Pluto TCK test failure in V2AddlResponseTests_SPEC2_12_Resource_characterEncoding2 due to unsupported encoding iso-8859-16
Neil Griffin created PLUTO-805:
----------------------------------
Summary: Pluto TCK test failure in V2AddlResponseTests_SPEC2_12_Resource_characterEncoding2 due to unsupported encoding iso-8859-16
Key: PLUTO-805
URL: https://issues.apache.org/jira/browse/PLUTO-805
Project: Pluto
Issue Type: Bug
Components: tck
Affects Versions: 3.0.3-TCK
Environment: macOS Sonoma 14.1.1 (23B81)
Reporter: Neil Griffin
Assignee: Neil Griffin
Fix For: 3.0.4-TCK
h2. Problem Background:
This test is likely failing due to a lack of regional support for the iso-8859-16 character set in either the JVM from Oracle or the underlying operating system, which in this case is macOS Sonoma 14.1.1 (23B81). So the problem isn't with Pluto or the TCK really, it's more of an environment support problem. Switching to iso-8859-15 fixes the problem.
h2. Steps to Reproduce:
* Visit [http://localhost:8080/pluto/portal/V2AddlResponseTests]
* Click on the "V2AddlResponseTests_SPEC2_12_Resource_characterEncoding2" link
(/) Expected Results
The portlet displays the following:
{noformat}
Test Succeeded{noformat}
{noformat}
Details: The character encoding can be set via the setLocale method and a locale-encoding-mapping-list mapping in the web.xml deployment descriptor {noformat}
(x) Actual Results
The tomcat console log report the following stack trace:
{noformat}
Caused by: java.nio.charset.UnsupportedCharsetException: iso-8859-16
at java.nio.charset.Charset.forName(Charset.java:531)
at org.apache.tomcat.util.buf.CharsetCache.getCharset(CharsetCache.java:195)
at org.apache.tomcat.util.buf.B2CConverter.getCharset(B2CConverter.java:63)
at org.apache.coyote.Response.setCharacterEncoding(Response.java:498)
at org.apache.catalina.connector.Response.setCharacterEncoding(Response.java:796)
at org.apache.catalina.connector.ResponseFacade.setCharacterEncoding(ResponseFacade.java:460)
at javax.servlet.ServletResponseWrapper.setCharacterEncoding(ServletResponseWrapper.java:84)
at org.apache.pluto.driver.services.container.PortletResourceResponseContextImpl.setCharacterEncoding(PortletResourceResponseContextImpl.java:59)
at org.apache.pluto.container.impl.ResourceResponseImpl.setCharacterEncoding(ResourceResponseImpl.java:126)
at org.apache.pluto.container.impl.ResourceResponseImpl.setLocale(ResourceResponseImpl.java:164)
at javax.portlet.tck.portlets.AddlResponseTests_SPEC2_12_Resource.serveResource(AddlResponseTests_SPEC2_12_Resource.java:287)
... 64 more {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
unsubscribe
Posted by Mehmet Gunacti <me...@gmail.com>.
unsubscribe
RE: [jira] [Created] (PLUTO-805) Pluto TCK test failure in V2AddlResponseTests_SPEC2_12_Resource_characterEncoding2 due to unsupported encoding iso-8859-16
Posted by "Morgan, Algie" <mo...@iodp.tamu.edu>.
unsubscribe
Algie
Mobile: 979-571-8769
From: Neil Griffin (Jira) <ji...@apache.org>
Sent: Friday, December 8, 2023 10:32 AM
To: pluto-dev@portals.apache.org
Subject: [jira] [Created] (PLUTO-805) Pluto TCK test failure in V2AddlResponseTests_SPEC2_12_Resource_characterEncoding2 due to unsupported encoding iso-8859-16
Neil Griffin created PLUTO-805: ---------------------------------- Summary: Pluto TCK test failure in V2AddlResponseTests_SPEC2_12_Resource_characterEncoding2 due to unsupported encoding iso-8859-16 Key: PLUTO-805 URL: https: //urldefense. com/v3/__https: //issues. apache. org/jira/browse/PLUTO-805__;!!KwNVnqRv!E9osLAI8_1VPaesRhxRrh_yp9T2XBZwC616Wf8JbAW8Pbm829K7LFJ88ZpR6RGjWKt5KCeraf8q-ffaOZw$
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
Neil Griffin created PLUTO-805:
----------------------------------
Summary: Pluto TCK test failure in V2AddlResponseTests_SPEC2_12_Resource_characterEncoding2 due to unsupported encoding iso-8859-16
Key: PLUTO-805
URL: https://urldefense.com/v3/__https://issues.apache.org/jira/browse/PLUTO-805__;!!KwNVnqRv!E9osLAI8_1VPaesRhxRrh_yp9T2XBZwC616Wf8JbAW8Pbm829K7LFJ88ZpR6RGjWKt5KCeraf8q-ffaOZw$<https://urldefense.com/v3/__https:/issues.apache.org/jira/browse/PLUTO-805__;!!KwNVnqRv!E9osLAI8_1VPaesRhxRrh_yp9T2XBZwC616Wf8JbAW8Pbm829K7LFJ88ZpR6RGjWKt5KCeraf8q-ffaOZw$>
Project: Pluto
Issue Type: Bug
Components: tck
Affects Versions: 3.0.3-TCK
Environment: macOS Sonoma 14.1.1 (23B81)
Reporter: Neil Griffin
Assignee: Neil Griffin
Fix For: 3.0.4-TCK
h2. Problem Background:
This test is likely failing due to a lack of regional support for the iso-8859-16 character set in either the JVM from Oracle or the underlying operating system, which in this case is macOS Sonoma 14.1.1 (23B81). So the problem isn't with Pluto or the TCK really, it's more of an environment support problem. Switching to iso-8859-15 fixes the problem.
h2. Steps to Reproduce:
* Visit [https://urldefense.com/v3/__http://localhost:8080/pluto/portal/V2AddlResponseTests__;!!KwNVnqRv!E9osLAI8_1VPaesRhxRrh_yp9T2XBZwC616Wf8JbAW8Pbm829K7LFJ88ZpR6RGjWKt5KCeraf8pWJxJ5DQ$<https://urldefense.com/v3/__http:/localhost:8080/pluto/portal/V2AddlResponseTests__;!!KwNVnqRv!E9osLAI8_1VPaesRhxRrh_yp9T2XBZwC616Wf8JbAW8Pbm829K7LFJ88ZpR6RGjWKt5KCeraf8pWJxJ5DQ$>]
* Click on the "V2AddlResponseTests_SPEC2_12_Resource_characterEncoding2" link
(/) Expected Results
The portlet displays the following:
{noformat}
Test Succeeded{noformat}
{noformat}
Details: The character encoding can be set via the setLocale method and a locale-encoding-mapping-list mapping in the web.xml deployment descriptor {noformat}
(x) Actual Results
The tomcat console log report the following stack trace:
{noformat}
Caused by: java.nio.charset.UnsupportedCharsetException: iso-8859-16
at java.nio.charset.Charset.forName(Charset.java:531)
at org.apache.tomcat.util.buf.CharsetCache.getCharset(CharsetCache.java:195)
at org.apache.tomcat.util.buf.B2CConverter.getCharset(B2CConverter.java:63)
at org.apache.coyote.Response.setCharacterEncoding(Response.java:498)
at org.apache.catalina.connector.Response.setCharacterEncoding(Response.java:796)
at org.apache.catalina.connector.ResponseFacade.setCharacterEncoding(ResponseFacade.java:460)
at javax.servlet.ServletResponseWrapper.setCharacterEncoding(ServletResponseWrapper.java:84)
at org.apache.pluto.driver.services.container.PortletResourceResponseContextImpl.setCharacterEncoding(PortletResourceResponseContextImpl.java:59)
at org.apache.pluto.container.impl.ResourceResponseImpl.setCharacterEncoding(ResourceResponseImpl.java:126)
at org.apache.pluto.container.impl.ResourceResponseImpl.setLocale(ResourceResponseImpl.java:164)
at javax.portlet.tck.portlets.AddlResponseTests_SPEC2_12_Resource.serveResource(AddlResponseTests_SPEC2_12_Resource.java:287)
... 64 more {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)