Hi, I would like to start using the resources package in stratum to start trying to unify resource location for Turbine applications.
Right now the mapper has been changed to accept an InputStream so that Turbine can decide on how the pipeline descriptors are found but it would be good if all our tools that work with resources apply the same pattern. We might want to use a Reader or add the option of using a Reader in the tools so that encoding can be dealt with. For now I added the use of an InputStream as we are dealing primarily with configurations, but definitely for other resources that are internationalized the InputStream might not be enough. So if we are going to deal with Readers than the resources package will probably need to be modified. So what I would like to start with is the use of some of the classes in resources package as a start to find the TRP and the pipeline descriptors. I would like to start simple using the FileResource and ClasspathResource directly. The logic for the searching will be decided in Turbine and than the tools (in this case the mapper for pipeline descriptors, and ExtendedProperties for config) can take the InputStreams/Readers. Eventually I would like to get a ResourceManager going with configurable policies for resource management (whether to poll for changes, or to allow update on demand) but I can make the changes outlined above today as a start and move us toward a unified resource management strategy and I can probably get a WAR file working. -- jvz. Jason van Zyl http://tambora.zenplex.org http://jakarta.apache.org/turbine http://jakarta.apache.org/velocity http://jakarta.apache.org/alexandria http://jakarta.apache.org/commons -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
