OK by me. Could deserve a 'known issue' note as well,
with the workaround to look on disk
directly. I think your initial fix would have still
worked with old jobs.
- Gordon
stack wrote:
> Gordon Mohr (Internet Archive) wrote:
>
>> Problem with this fix:
>>
>> Michael Stack wrote:
>>
>>> --- 49,64 ----
>>> }
>>> ! if(theJob != null) {
>>> settingsHandler =
theJob.getSettingsHandler();
>>> ! String logsPath =
(String)settingsHandler.getOrder().
>>> ! getAttribute(CrawlOrder.ATTR_LOGS_PATH);
>>> ! File f = new File(logsPath);
>>> ! if (f.isAbsolute()) {
>>> ! fileName = (new File(f,
fileName)).getAbsolutePath(); ! } else {
>>> ! f =
settingsHandler.getOrder().getController().
>>> !
getSettingsDir(CrawlOrder.ATTR_LOGS_PATH);
>>> ! fileName = (new File(f,
fileName)).getAbsolutePath();
>>> ! }
>>
>>
>>
>>
>> For old jobs, there's no controller attached, so
this getController().getSettingsDirectory()
>> will NPE. To trigger, choose the 'logs' link from
the list of old completed jobs.
>>
>> This makes fixing this for all situations a bit of a
mess unless some
>> of the path-knowledge in controller gets duplicated
elsewhere...
>>
> I think its a rare-enough case that, unless you think
otherwise, I'll leave it as is and make an issue for
this case.
> St.Ack
Nobody/Anonymous
Usability/UI
None
Public
|
Date: 2007-03-14 00:18
|
|
Date: 2004-11-05 21:37 Logged In: YES |
| Field | Old Value | Date | By |
|---|---|---|---|
| status_id | Open | 2004-11-05 21:37 | stack-sf |
| resolution_id | None | 2004-11-05 21:37 | stack-sf |
| close_date | - | 2004-11-05 21:37 | stack-sf |
Copyright © 2010 Geeknet, Inc. All rights reserved. Terms of Use