[TAPESTRY-2095] Incorrect optimization for requests that contain a colon but do not contain a slash

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.8, 5.0.9
• Fix Version/s: 5.0.10
• Component/s: Core Components
• Environment: MacOS X, Jetty, Eclipse
• Assignee: Howard Lewis Ship
• Reporter: Moritz Gmelin
• Created: 28/Jan/08 14:39
• Updated: 07/Feb/08 23:11
• Resolved: 07/Feb/08 23:11

Description

I have a dynamically created image from a service on my page.

The method to create the link is as follows
public Link getBPURL(){
return getResources().createActionLink("BPGraph", false, new Object[] { });
}

This is how the .tml part looks
<img id="bpimg" class="dia_img" src="${BPURL}" width="800" height="400"/>

And this is the resulting html code
<img class="dia_img" height="400" id="bpimg" src="databp:BPGraph" width="800">

The browser refuses to render an image since it considers the URL "databp:BPGraph" as invalid (which I can somehow understand).

If I add a dummy parameter in the method that creates the Link
public Link getBPURL(){
return getResources().createActionLink("BPGraph", false, new Object[]

{ 1 }

);
}
the rendered html looks like this
<img class="dia_img" height="400" id="bpimg" src="./databp:BPGraph/1" width="800">

This is OK for my browser. But I would consider it a but in the way tapestry (since 5.0.8) shortens the URLs.