You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Ryan Holmes (JIRA)" <ta...@jakarta.apache.org> on 2006/03/27 10:25:42 UTC

[jira] Commented: (TAPESTRY-897) Base tag with pages in subfolders

    [ http://issues.apache.org/jira/browse/TAPESTRY-897?page=comments#action_12371955 ] 

Ryan Holmes commented on TAPESTRY-897:
--------------------------------------

Absolutely, the base tag should be optional to support relative image paths. The simplest work-around for now is to provide a dummy BaseTagWriter:

public class NullBaseTagWriter implements IRender {

  public void render(IMarkupWriter writer, IRequestCycle cycle) {
    // Intentionally blank - supresses the BASE tag.
  }
}


The HiveMind configuration:
<implementation service-id="tapestry.url.BaseTagWriter">
	<create-instance class="NullBaseTagWriter" />
</implementation>


> Base tag with pages in subfolders
> ---------------------------------
>
>          Key: TAPESTRY-897
>          URL: http://issues.apache.org/jira/browse/TAPESTRY-897
>      Project: Tapestry
>         Type: Bug
>   Components: Framework
>     Versions: 4.0
>     Reporter: Henri Dupre
>     Priority: Minor

>
> when a page is located in a subfolder, tapestry Shell component renders a <base href=<site/subfolder>> tag.
> This realocates all the images on the page, but this should be optional. All my components point to relative resources and with a base href=... none of my images is showing.
> What about an optional base property?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org