*0.1.0 (September, 16th, 2009)*
 
  * API CHANGED
  * there is no more dataType parameter for storing methods
  * introducing storeRecord definition:
    <storeRecord>
      <storeRecordIdentifier>...</storeRecordIdentifier>
      <storeObject datatype="URI|Data">...<storeObject>
    </storeRecord>
  * the input list of storing methods should contain now the list of storeRecords 
    instead o simple strings 
  * the client service can decide now about the object identifiers
    by defining them self in storeRecord structures; the store service sets own identifier
    in case if the objectIdentifier in storeRecords is not defined. 
  * bug #787 fixed - not correct order override properties
  * code re-factored and cleaned
  *bug in ListRecordsIterator fixed  
  
*0.1.1 (October, 8th, 2009)* 
 
  *service use now icm-commons libraries as a basis for blackboard handling
  *ResultSet EPR in the STORE notification message has to be now 64base encoded
  
*0.1.2 (November, 18th 2009)*
  
  * writing single record exceptions in to storing status profile fixed
  * API changed: deleteStore function returns boolean now
  
*0.1.3 (November, 2009)*
  
  * updating store data structure profile after objects deletion fixed
  * add missing properties in to the service bean file (DepotService bean)
  * updating status of number of stored objects in store data structure profile fixed
  * updating status of stored objects mime-types in store data structure fixed
  * replacing special characters in object record identifiers defined by the client
    (usage such characters in objects identifiers caused producing broken urls)
    
*0.1.4 (December, 2009)*

  * minor bug in storing objects without the identifiers, new identifier 
    was not correctly generated
  * handling parallel storing operations on the same store data structure
  * exceptions handling re-implemented - required for proper handling
    parallel storing operations  
  
*0.1.5 (September 22th, 2010)*

  * asynchronous downloading: store service sends now complete XML Store Records to
    download service and gets back the ResultSet with Store Records containing local paths 
    to the donloaded objects in place of urls. If Store Record doesn't contain url but just 
    a text object then download service ignores it and put the not changed XML in to the ResultSet.
  * ResultSetIterrator class rewritten 
  * Adding new element STORING_PROCESS_STATUS to the storing status profile, it should inform 
    if the storing process is still active or not.
  * yadda store is run now in the same container 

*0.1.6 (June 9th, 2011)*
    * minor ResultSet connection exception handling fixes
    * API changes: 
    	- deprecated method manageDASReplicas removed
    	- deprecated method deleteStoreObjectFromRS removed
    	- new method updateDASReplica implemented: method handles DAS 
    		repliacs entries in Depot Service profile.
		- storing methods extended about simple download flag parameter
		  which decides wheter storing method should use external download service 
		  for downloading objects (flag set on false) or just simple bulit-in 
		  dowloading mechanism (flag set on true). In case of simple downloading
		  objects are not temporary stored on disk but they are streemed directly 
		  to the storage.
	* storing status profile changed: tag IGNORED_OBJECTS has been replaced by 
	  IGNORED_OBJECTS_STORING and IGNORED_OBJECTS_DOWNLOADING in order to inform
	  how many records were ignored during the downloading process and how 
	  many during the storing process.