|
This doesn’t make any sense from an API
perspective.
If the Resource object from the query
service isn’t ‘real’, then why is it a Resource object? And if I can’t use that Resource object
for removal via the Collection.removeResource( Resource), then why on earth does it exist? Thanks for your pointer Vanessa, I’ll
find that message and use the workaround until this is resolved. Kevin -----Original Message----- As far as I understand it (which isn’t very far!)
this is the expected behaviour. Why it is this way isn’t clear to me,
though. If you look in the archives a few days back I posted a question about
this behaviour, including a code snippet for how I got around it. It might help
you if you just need to get your problem solved quickly. Test Case: An xpath query is issued to retrieve
document resources that need to be removed. |
Title: Re: [Bug] Collection.removeResource( resource ) does not work when
resource is derived from XPathQueryService
- [Bug] Collection.removeResource( resource ) does not work... Kevin Ross
- Re: [Bug] Collection.removeResource( resource ) does... Vanessa Williams
- Kevin Ross
