forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Gardler (JIRA)" <>
Subject [jira] Commented: (FOR-764) Locationmap returns relative paths
Date Tue, 31 Jan 2006 09:42:32 GMT
    [ ] 

Ross Gardler commented on FOR-764:

"If a resource is used by more than one stylesheet why not just promote it to a common webapp\resource
anyway? "

Because a plugin developer has no way of knowing that a stylesheet is going to be re-used
at some point in the future. In addition the plugin author does not have access to the core.
Finally, if a plugin is released under a license other than the ASF then we cannot distirbute
it, thus compounding these problems.

"absolute paths in webapp mode"

Not a problem if the path is determined dynamically, thus the resolved path will be the current
location of the plugins.

"access permissions on a production machine"

If one plugin has the necessary access permission then Forrest itslef must have access, therefore
all plugins have access.

"no concept of formal dependencies between plugins yet"

No firm concept yet, that is true. This issue is part of firming up those concepts.

> Locationmap returns relative paths
> ----------------------------------
>          Key: FOR-764
>          URL:
>      Project: Forrest
>         Type: Bug
>   Components: Locationmap
>     Versions: 0.8-dev
>     Reporter: Ross Gardler

> It is intended (at least by me) to allow locationmaps to expose resources to other plugins.
For example, a stylesheet provided by one plugin may be used within another.
> Unfortunately, the location returned by a locationmap is relative, not absolute. Consequently,
when we try and access a resource from a sitemap other than the plugins sitemap the locations
are broken.
> What we need to do is provide an absolute location by pre-pending the path to the locationmap
file. For example:
> suppose /home/foo/locationmap.xml has:
> <match pattern="foo.xml">
>   <location src="bar/foo.xml"/>
> </match>
> The location returned for {lm:foo.xml} should be "/home/foo/bar/foo.xml" (at present
it is "bar/foo.xml")

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message