    catch (DocumentException e){ // here you are catching exception
       throw new DocumentException("some message");// now you are changing
       // exception message 
    }


That is a bad practice you have to throw originally thrown exception to upper level then you can handle the Exception there. 

This way is better

   catch (DocumentException e){
       throw new DocumentException("some message",e);
   }


Is catching DocumentException a good idea?
I have 100s of images to save out in a different format for a project that I am working on. And the problem is I have to do them one at a time, so I am wondering if there is some way to record the actions of me saving one of them out and then having the program repeat it by looking in a specific directory and doing it with all of the images. I am not sure how else to explain what I am trying to do, but I just need some way to make the program that I am using automate the saving task for each image. P.S I don't know if it helps but the program that I am using is called (Texture Packer)
