Encoding URLs"
From Documentation
Tmillsclare (talk | contribs) m |
|||
| Line 1: | Line 1: | ||
{{ZKComponentReferencePageHeader}} | {{ZKComponentReferencePageHeader}} | ||
| − | A XHTML component generates attributes directly to native HTML tags. It means, unlike XUL, it doesn't prefix the servlet context path to attributes for specifying URL. For example, the following codes | + | A XHTML component generates attributes directly to native HTML tags. It means, unlike XUL, it doesn't prefix the servlet context path to attributes for specifying URL. For example, the following codes will not work (unless the servlet context is ""). |
<source lang="xml" > | <source lang="xml" > | ||
Revision as of 02:33, 1 August 2011
A XHTML component generates attributes directly to native HTML tags. It means, unlike XUL, it doesn't prefix the servlet context path to attributes for specifying URL. For example, the following codes will not work (unless the servlet context is "").
<img href="/my/good.png"/>
Instead, you should use the encodeURL function in EL expressions as follows.
<?taglib uri="http://www.zkoss.org/dsp/web/core.dsp.tld" prefix="p"?>
...
<img href="${p:encodeURL('/my/good.png')}"/>
In Java, you should use the method, Execution.encodeURL(String).
<img id="another"/>
<zscript>
another.setDynamicAttribute("href",
Executions.getCurrent().encodeURL("/my/good.png"));
</zscript>
Notice that XUL components and all ZK features that accept a URL will invoke the encodeURL method automatically. The reason why we do not handle XHTML components is that we do not know which attribute requires a URL.