[
https://issues.apache.org/struts/browse/WW-3095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=46262#action_46262
]
Wes Wannemacher commented on WW-3095:
-------------------------------------
Martin, I'm not sure if you're allowed to use non-alphanumeric characters in an
URL... I'm looking through the URL spec -
http://www.w3.org/Addressing/URL/url-spec.txt and I don't see a part of the URL
where anything other than [a-zA-Z0-9+%/] is allowed. I could be wrong though...
> URL has no setEncoding
> ----------------------
>
> Key: WW-3095
> URL: https://issues.apache.org/struts/browse/WW-3095
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Tags
> Affects Versions: 2.1.6
> Environment: Struts 2.1.6
> TC 6.0.14
> JDK 1.6.0.10
> Reporter: Martin Gainty
>
> If I set encoding the encoding to UTF-8 in struts.properties as
> struts.i18n.encoding=UTF-8
> //If I implement the include tag I see all appropriate annotations e.g.
> @StrutsTag(name="include",
> tldTagClass="org.apache.struts2.views.jsp.IncludeTag", description="Include a
> servlet's output " +
> "(result of servlet or a JSP page)")
> public class Include extends Component {
>
> //more importantly the include will support the STRUTS_I18N_ENCODING
> DefaultEncoding with this inject //annotation
> @Inject(StrutsConstants.STRUTS_I18N_ENCODING)
> public void setDefaultEncoding(String encoding) {
> defaultEncoding = encoding;
> }
> //but viewing the URL code I see
> @StrutsTag(name="url", tldTagClass="org.apache.struts2.views.jsp.URLTag",
> description="This tag is used to create a URL")
> public class URL extends ContextBean
> //there is no setDefaultEncoding which means any new encodings in
> struts.properties will not be reflected here
> MCG 22 April 09
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
