Over the weekend I had a go at setting up DSpace on my debian system and I
have to say it would not as smooth as when I set it up on Windoze. Part of
the problem was in getting it to be invoked ok from tomcat. Eventually I
found why I was getting 404. It was due to a failure to initialise the
logging system. logging.properties is not copied into the expected area
during the dspace build. For some strange reason this seems not to cause a
problem on windoze (although you do get a warning about it). This problem
made me look at how logging is done in dspace, where I notice that it uses
log4j.
I suggest that it would be better for DSpace to use sl4j instead. The API is
very very close so the code could be fixed with a few global search-replace
commands. sl4j is much more forgiving with initialization and thus, IMO much
easier to use. It is already replacing apache commons logging as the
preferred logging API. In the meantime I think the setup of
logging.properties needs to be fixed. How shall these issues be addressed?
Would a bug report and enhancement request be appropriate? I like to raise
these issues on this ML before raising these things officially, it gives
them a chance to be discussed first.
--
Regards,
Andrew M.
http://www.andrewpetermarlow.co.uk
------------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It is the best place to buy or sell services for
just about anything Open Source.
http://p.sf.net/sfu/Xq1LFB
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
