--- Stephen McConnell <[EMAIL PROTECTED]> wrote: [SNIP] > > Some thoughts after digging though Resource and > associated classes ... > > Of particular interest to me is the ability to > declare resources that can be > used as arguments to a Path definition - however, as > things currently stand > the Path datatype explicitly excludes resource > collections that are not file > based (which seems to me to defeat the purpose of > Resource - but I'm hoping > this is resolvable). >
We could come back to this; in my opinion relaxing this restriction in the future would not hurt anything. However, in the ResourceCollection refactoring, Path's inheritance hierarchy was altered such that its immediate superclass is the new Union resource collection. So the only difference between the two is, for all practical purposes, the filesystem-only restriction. Path further supports its historical API e.g. <pathelement>, list(). But to get back to the point, in general a <union> can be used where a filesystem-agnostic <path> is desired. -Matt __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
