Would it be possible to make IResourceStreamLocator.locate take class
instead of class loader?
And is it all right that ResourceSettings.setResourceStreamLocator takes
class (ResourceStreamLocator) instead of an interface?
-Matej
---
I think i agree with Matej on this one(have already made some refactorings.)But just to make sure.Settings.getResourceLocator() should return an instance and not a implemenation.Then is it a bad thing that we change the interface from:
public IResourceStream locate(ClassLoader classLoader, String
On 1/19/06, Johan Compagner [EMAIL PROTECTED] wrote:
I think i agree with Matej on this one
(have already made some refactorings.)
But just to make sure.
Settings.getResourceLocator() should return an instance and not a
implemenation.
why? why do we the interface than?
Then is it a bad
Johan
there is one more: AbstractResourceStreamLoader and
ResourceStreamLoader seem to be redundant. Looks like I didn't
finished some refactoring. I guess ResourceStreamLoader seems to be
more or less obsolete/redundant
Juergen
On 1/19/06, Juergen Donnerstag [EMAIL PROTECTED] wrote:
On
Sorry i meant of course interface... :(so returning the interface in Settingsand making the Class param method the interface method?will do that refactor.Which can be removed? Because DefaultResourceStreamLocater extends ResourceStreamLocator
And the default is a list of IResourceLocators and some
