bodington-developers

[Bodington-developers] ResourceTree.addResource()

[Matthew B. <mat...@ou...>]

If ResourceTree.addResource() it is left up to the caller to fix things 
up (call ResourceTree.remove() and rollback the transaction). However 
ResourceTree.moveResource() does the cleanup itself. Is there a reason 
for the difference?

-- 
  -- Matthew Buckett, VLE Developer
  -- Learning Technologies Group, Oxford University Computing Services
  -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/

Re: [Bodington-developers] ResourceTree.addResource()

[Matthew B. <mat...@ou...>]

Matthew Buckett wrote:
> If ResourceTree.addResource() it is left up to the caller to fix things 

If ResourceTree.addResource() fails it..

-- 
  -- Matthew Buckett, VLE Developer
  -- Learning Technologies Group, Oxford University Computing Services
  -- Tel: +44 (0)1865 283660 http://www.oucs.ox.ac.uk/ltg/

Re: [Bodington-developers] ResourceTree.addResource()

[Alexis O'C. <ale...@ou...>]

Matthew Buckett wrote:
> Matthew Buckett wrote:
>> If ResourceTree.addResource() it is left up to the caller to fix things 
> 
> If ResourceTree.addResource() fails it..
> 

A nice little "surprise" for the unwary I guess ;-).

I imagine there probably isn't a "good" reason. In fact if 
moveResource()had been factored to use addResource() itself when adding 
the resource to it's new location, then this discrepancy would've 
already showed up.

Alexis

Re: [Bodington-developers] ResourceTree.addResource()

[Jon M. <jo...@te...>]

Matthew Buckett wrote:
> If ResourceTree.addResource() it is left up to the caller to fix 
> things up (call ResourceTree.remove() and rollback the transaction). 
> However ResourceTree.moveResource() does the cleanup itself. Is there 
> a reason for the difference?
>
Uhmmm........

Hard to remember that far back but I suspect that there isn't a good 
reason for the difference.

Jon