I knew to use the "//" because I wrote some of that code. :) I did a
perphery glance in the documentation and didn't find anything so it
probably warrants a bug against the documentation. My preference would
be to put it in the Developers Guide.
As for commandNavigationItem, it's obviously not calling the correct api
to handle the leading "//". Go ahead and generate a bug on that one as
well. The patch should be pretty straight forward as it will simply
have to mimic what is being done in the tr:image's src attribute.
Scott
Richard Yee wrote:
Thanks Scott. Putting "//" before the resource partially fixed the
problem. It fixes the issue with tr:image and tr:tree, but in
tr:commandNavigationItem, the problem still remains with the icon
attribute.
Putting "// in the icon attribute of the tr:commandNavigationItem
resulted in <img
src="/appj/myApp//myApp/components/images/myImage.gif" being sent to
the browser. The desired output was
src="/myApp/components/images/myImage.gif"
How did you know about using "//"? Is it documented anywhere?
Thanks,
Richard
On 2/11/08, *Scott O'Bryan* <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>> wrote:
Try putting two slashes before the resource "//"
Richard Yee wrote:
> Hi,
> I'm using a tr:commandNavigationItem with the icon attribute. It
seems
> that the tag render code always prefixes the path to the image with
> the path of the web module. Is there a way to specify the path
so that
> it does not get prefixed with the module path?
>
> Ex. If my Root Context of my web application is "appj/myApp" and my
> jspx file contains this:
> <tr:commandNavigationItem
icon="/components/images/myImage.gif"...../>
>
> The image path gets rendered as
> <img src="/appj/myApp/components/images/myImage.gif".../>
>
> This does not work in my production environment because we split off
> the static content from the dynamic content so that it can be served
> from a web server. What I would like to do is to have the path
that is
> used for the icon be unmodified when it is rendered. The
tr:image tag
> also exhibits the same behavior. In that case I am able to use this
> instead
> <f:verbatim>
> <img src="/myApp/components/images/myImage.gif".../>
> </f:verbatim>
>
> Obviously, this does not work with the tr:commandNavigationItem.
>
> Thanks for any help in advance.
>
> Richard
>