> The question is why would you need to get back a URL from a Resource? You need to get a URL from a resource if you want to use the resource as InputSource in XML processing. The URL is used to set the SystemId, in practice to be able to resolve includes, entities, ... which are to be found with a relative path.
But when you get a StringResource, or PropertyResource, which are ficticious Resource impls wrapping a string or the value of an Ant property, even if you wrap these into a custom URL, how would you resolve URLs relative to these??? This is the reason why I'm saying that a getURL only makes sense for true URLResources only. Pushing it down to Resource smells wrong to me. Even if I'm wrong, it's easier to push it down to Resource afterward, based on community experience, rather that putting it there in the first place IMHO. --DD --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
