At 16:35 07/02/2001 +0000, you wrote:
>On Wed, Feb 07, 2001 at 12:17:48PM +0100, Raphaël Luta wrote:
> > I don't understand why ResourceService should provide these methods.
> > It's supposed to give access to configuration information not context
> > information.
> > It's cleaner to create a specific service for providing URL->path
> > resolution, or
> > more generally context services.
>
>I can see what you're getting at, but a broader interpretation of
>ResourceService could be that it provides global resources to the
>application. Currently this is in the form of properties, but there is
>no reason not to extend that to file-based resources, keyed by path from
>the webapp root.
Except when you think of alternate service implementation.
Someone will probably want one day to write a ResourceService implementation
based on either a DBMS or JNDI connection for retrieving the Turbine
configuration
options without impacting the URL -> Path mapping behavior.
(And the reverse is true, someone may want to write a specific non-servlet
container
implementation of the URL -> path mappings without modifying the basic TR.p
properties behavior)
Configuration and URL -> path mapping are orthogonal issues.
--
Raphaël Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Services Manager / Paris
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
