<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">it's a good point,<div><br></div><div>in the navigation controller framework it is possible to specify the kind of link that will be generated by the portal.<div><br></div><div>so creating an URL would be like</div><div><br></div><div>url.setMimeType(MimeType.XHTML);</div><div>url.toString();</div><div><br></div><div>or</div><div><br></div><div>url.setMimeType(MimeType.PLAIN);</div><div>url.toString();<br><div><br><div><div>On Oct 28, 2010, at 10:57 AM, Trong Tran wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">it says :<br><br><div style="margin-left: 40px;"><i>Note that replacing <strong class="html">&</strong> with
<strong class="html">&amp;</strong> is only done when
writing the <abbr class="initialism" title="Uniform Resource Locator">URL</abbr>
<strong>in
<abbr class="initialism" title="HyperText Markup Language">HTML</abbr></strong>,
where "&" is a special character (along with "<"
and ">"). When writing the same
<abbr class="initialism" title="Uniform Resource Locator">URL</abbr>
in a plain text email message or in the location bar of your browser,
you would use "&" and <em>not</em> "&amp;". With
<abbr class="initialism" title="HyperText Markup Language">HTML</abbr>,
the browser translates "&amp;" to "&" so the Web server would only see
"&" and not "&amp;" in the query string of the request.</i><br></div><br>I think this is a good example of reason why we have used '&' standalone before.<br><br>Anyway, I agree that the '&amp;' would be used to generate an ULR by default and we could provide an option to be able to retrieve the another in such cases<br>
<br><br><div class="gmail_quote">On 27 October 2010 21:23, Matt Wringe <span dir="ltr"><<a href="mailto:mwringe@redhat.com">mwringe@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
We are running into a bunch of problems with ajax requests when the<br>
portal is used to create the urls (this is especially seen when using<br>
wsrp as it needs to rewrite urls). The issue stems from the use of '&'<br>
instead of '&amp;', & alone is not allowed in xhtml/xml.<br>
<br>
I have already created a jira (with a patch) for this issue:<br>
<a href="https://jira.jboss.org/browse/GTNPORTAL-1597" target="_blank">https://jira.jboss.org/browse/GTNPORTAL-1597</a><br>
<br>
Is there any objection or reasons why we can't use the proper '&amp;'<br>
instead?<br>
<br>
_______________________________________________<br>
gatein-dev mailing list<br>
<a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/gatein-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/gatein-dev</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Tran The Trong<br>eXo Platform SEA<br>
_______________________________________________<br>gatein-dev mailing list<br><a href="mailto:gatein-dev@lists.jboss.org">gatein-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/gatein-dev<br></blockquote></div><br></div></div></div></body></html>