From Documentation

(Difference between revisions)
Jump to: navigation, search
m
m
Line 25: Line 25:
</source>
</source>
-
Notice that XUL components and all ZK features that accept a URL will invoke the <mp>encodeURL</mp> method automatically <ref>The reason not to
+
Notice that XUL components and all ZK features that accept a URL will invoke the <mp>encodeURL</mp> method automatically. The reason why we do not  
-
handle XHTML compoents is that we don't know which attribute requires URL.</ref>.
+
handle XHTML components is that we do not know which attribute requires a URL.
-
 
+
-
'''Notes'''
+
-
<references/>
+

Revision as of 03:42, 17 May 2010

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 don't 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.