Hi Steinar,
uri parameter points to the following pipeline (it's in coplets/html/sitemap.xmap):
<map:pipeline>
<map:match pattern="application">
<map:generate src="{coplet:temporaryAttributes/application-uri}?copletid={coplet:#}"/>
<map:transform type="portal-html-eventlink">
<map:parameter name="attribute-name" value="application-uri"/>
</map:transform>
<map:serialize type="xml"/>
</map:match>
</map:pipeline>
What it does, it takes XML produced by the pipeline referenced in temporary:application-uri, and applies the portal-html-eventlink transformer. This translates internal portal events to the html links.
If you want to have resources to be available to the browser - add resource forwarding pipelines to the sitemap where you need it:
For example, use this for jpeg's\
<map:match pattern="images/*">
<map:read mime-type="image/jpeg" type="image" src="editor/images/{1}"/>
</map:match>
and this for JavaScript files.
<map:match pattern="*.js">
<map:read mime-type="text/javascript" src="editor/{1}.js"/>
</map:match>Make sure that this pipeplines are in the correct sitemaps.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
