[EMAIL PROTECTED] wrote:
>
> I finished the patch for making the resources service of Turbine
> pluggable.
>
> The files are located at:
> http://locus.apache.org/~raphael/turbine/
>
> This patch allows the resources service implementation to be selected
> by a startup servlet parameter.
> However, people wishing to implement new resources service implementation
> should carefully read the limitations described in ResourcesService.java
> because there a lot of Turbine functionalities are unavailable to this service
> since it's initialized in a bootstrap mode.
I am currently in the process of incorporating your patch. I'm going to
change a few details in the implementation but I like the overall
solution
a lot.
I have encountered a problem we need to overcome, so that we have a
complete
solution. The problem is extracting configuration entries related to one
specific service. Recently Magnús Torfason submited a patch to
org.apache.java.util.Configutrations class that allowed to do that
easily
in the system based on extended properties files. I would certainly like
to see this capability on our system that is abstracted from properties
files. Such an operation is easily imaginable in a system based on xml
(extracting a subtree) or a naming system (extracting a subcontext).
Right now I think that we should add a method with signature like
ResoucesService getResources(String prefix) to the ResourcesService
interface. Then, TurbineServices class will be able to pass an
intance of ResourcesService containg extracted configuration values
to each service.
If you are willing to work on this issue, please let me know. Otherwise
I'll work on it next week.
Rafal
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
