Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
3.8
-
None
Description
In the logs of the GUIApplication you can see multiple examples of logentries like this:
May 5 2009 5:37:45 PM dk.netarkivet.harvester.harvesting.distribute.HarvestControllerClient doOneCrawl
FINE: Send crawl request: NO ID: To TEST7_COMMON_ANY_LOWPRIORITY_HACO ReplyTo TEST7_COMMON_ERROR OK Job: Job 48886 (state = SUBMITTED HD = 91 priority = LOWPRIORITY forcemaxcount = -1 forcemaxbytes = 1000000000 orderxml = default_orderxml numconfigs = 760) metadata: [dk.netarkivet.harvester.harvesting.distribute.MetadataEntry@b1ebb2]
or like this:
May 5 2009 5:38:32 PM dk.netarkivet.harvester.harvesting.distribute.HarvestControllerClient doOneCrawl
FINE: Send crawl request: NO ID: To TEST7_COMMON_ANY_LOWPRIORITY_HACO ReplyTo TEST7_COMMON_ERROR OK Job: Job 49040 (state = SUBMITTED HD = 91 priority = LOWPRIORITY forcemaxcount = -1 forcemaxbytes = 1000000000 orderxml = default_orderxml numconfigs = 222) metadata: [dk.netarkivet.harvester.harvesting.distribute.MetadataEntry@1e6d43a dk.netarkivet.harvester.harvesting.distribute.MetadataEntry@17755d8]
Each logentry tries to print out the metadata associated with this job but
only prints out references to instances of the dk.netarkivet.harvester.harvesting.distribute.MetadataEntry class.
A toString method for MetadataEntry could look like this:
public String toString() {
return "URL=" + getUrl + "; mimetype=" + getMimetype + "; data= " + getData();
}