Roy Teeuwen wrote > Hey Carsten, > > Thanks for the info! It seems by the way that the current implementation > actually even breaks Slin when still using the old ResourceProvider api. > > When you have for example a api.ResourceProvider mounted on path /content, it > will be added to the excludedPaths of the ProviderContext => These paths are > used in the BasicQueryLanguageProvider when doing a query in the resource > resolver and returning a JcrNodeResourceIterator, making it that no results > are returned anymore from /content. > > I don't know if I should register this as a bug? What is the policy of > deprecated classes? Shouldn't they still work as designed until they actually > get removed? > Hi,
yes, deprecated classes should work as designed, so this might be a bug. Regards Carsten -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
