[ 
https://jira.duraspace.org/browse/DS-675?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27813#comment-27813
 ] 

Hardy Pottinger commented on DS-675:
------------------------------------

this was the primary subject of discussion at the 3/6/2013 Developer's Meeting 
(I will attempt to paste a log of the discussion):

[2:43pm] <hpottinger> OK, dumb question time: what version of Cocoon are we 
running under the hood here?
[2:43pm] <jrgriffiniii>
I'm uncertain
[2:43pm] <jrgriffiniii>
One moment please
[2:43pm] <hpottinger>
sorry, meant that for the other developers :-)
[2:45pm] <mhwood>
I think it's been 2.2.0-hacked-by-DSpace for a long time now.
[2:45pm] <hpottinger>
http://mvnrepository.com/artifact/org.dspace.dependencies.cocoon/dspace-cocoon-servlet-service-impl
[2:45pm] <kompewter>
[ Maven Repository: org.dspace.dependencies.cocoon » 
dspace-cocoon-servlet-service-impl ] - 
http://mvnrepository.com/artifact/org.dspace.dependencies.cocoon/dspace-cocoon-servlet-service-impl
[2:47pm] <mhwood>
Right, every Cocoon artifact is stock except for 
org.dspace.dependencies.cocoon:dspace-cocoon-servlet-service-impl:1.0.3.  I 
don't think that's changed in years.
[2:47pm] <mhwood>
(Probably because Cocoon hasn't released in years.)
[2:49pm] <hpottinger>
here it is in github 
https://github.com/DSpace/dspace-cocoon-servlet-service-impl
[2:49pm] <kompewter>
[ DSpace/dspace-cocoon-servlet-service-impl · GitHub ] - 
https://github.com/DSpace/dspace-cocoon-servlet-service-impl
[2:50pm] <mhwood>
OK, 1.0.3 went to Central in October 2011.
[2:50pm] <mhwood>
http://search.maven.org/#search|gav|1|g%3A%22org.dspace.dependencies.cocoon%22%20AND%20a%3A%22dspace-cocoon-servlet-service-impl%22
[2:50pm] <kompewter>
[ The Central Repository Search Engine ] - 
http://search.maven.org/#search|gav|1|g%3A%22org.dspace.dependencies.cocoon%22%20AND%20a%3A%22dspace-cocoon-servlet-service-impl%22
[2:53pm] <hpottinger>
some comment headers in that source do seem to point towards 
dspace-cocoon-servlet-service-impl being based on Cocoon 2.2
[2:53pm] <mhwood>
Would it be much work to try moving to a more recent version of DSpace?  1.6.x 
has been out for so long that this may have been fixed and forgotten.
[2:54pm] <mhwood>
Yeah, hpottinger, dspace-xmlui/pom.xml pulls in cocoon-core:2.2.0 and some of 
its relatives (which have their own versions).
[2:54pm] <jrgriffiniii>
mhwood: I feel that this is best course of action.  I want to ensure that there 
aren't any quick work-arounds which will buy me time for a proper upgrade.
[2:55pm] <jrgriffiniii>
mhwood: We only have one server for DSpace, and requesting another server for 
the migration will consume time in itself
[2:55pm] <hpottinger>
mhwood: I do seem to remember that DS-768 may have made some changes that might 
apply to the issues being reported by jrgriffiniii
[2:55pm] <kompewter>
[ https://jira.duraspace.org/browse/DS-768 ] - [#DS-768] All XMLUI Error Pages 
respond with 200 OK, instead of 404 Not Found - DuraSpace JIRA
[2:56pm] <mhwood>
Fixed in 1.8.0, according to JIRA.
[2:56pm] <mhwood>
That is:  the response code was fixed then.  Dunno about this other issue.
[2:57pm] <hpottinger>
in theory, you might be able to just tweak your pom.xml to refer to the latest 
version of dspace-cocoon-servlet-service-impl, if I recall correctly, that's 
how we tested it before it was committed (on a 1.7.x code base)
[2:58pm] <mhwood>
jrgriffiniii, can you scrounge up any old PC with maybe 512MB memory, just to 
test on?  Would that be a good use of time?
[3:02pm] <jrgriffiniii>
mhwood: Sorry, one moment.  I've just discovered that a theme which was 
allegedly working may not in fact be functioning properly
[3:02pm] <hpottinger>
I just pasted this link to the ticket for 675: 
http://cocoon.apache.org/2.2/core-modules/core/2.2/1399_1_1.html
[3:02pm] <kompewter>
[ Cocoon Core - Logging configuration ] - 
http://cocoon.apache.org/2.2/core-modules/core/2.2/1399_1_1.html
[3:06pm]
KevinVdV left the chat room. (Quit:  HydraIRC -> http://www.hydrairc.com <- In 
tests, 0x09 out of 0x0A l33t h4x0rz prefer it :))
[3:07pm] <mhwood>
Well, *that's* different.  I wonder if Cocoon is doing its own log4j 
configuration, and then somehow we come along and confuse it.
[3:11pm] <hpottinger>
I suppose block-level debugging would be helpful...
[3:14pm] <hpottinger>
sorry, didn't mean to hijack the whole Developers meeting :-\ but 675 has been 
on the "to fix" list for a while.
                
> XMLUI doesn't start if the error level in the log4j.properties is set to DEBUG
> ------------------------------------------------------------------------------
>
>                 Key: DS-675
>                 URL: https://jira.duraspace.org/browse/DS-675
>             Project: DSpace
>          Issue Type: Bug
>          Components: XMLUI
>    Affects Versions: 1.6.2
>         Environment: Mac OS, Tomcat, Java 1.6
>            Reporter: Franck Borel
>            Assignee: Hardy Pottinger
>            Priority: Major
>
> Setting the log level in the log4j.properties from INFO to DEBUG following 
> error:
> 2010-09-16 10:57:11,892 ERROR cocoon.handled  - Sitemap: error when calling 
> sub-sitemap
>       at <map:mount> - 
> jndi:/localhost/dspace-xmlui/aspects/aspects.xmap:119:72
>       at <map:select type="parameter"> - 
> jndi:/localhost/dspace-xmlui/aspects/aspects.xmap:109:34
>       at <map:match type="AspectMatcher"> - 
> jndi:/localhost/dspace-xmlui/aspects/aspects.xmap:108:36
>       at <map:mount> - jndi:/localhost/dspace-xmlui/sitemap.xmap:430:108
>       at <map:match> - jndi:/localhost/dspace-xmlui/sitemap.xmap:429:53
> etc.
> Setting of the log4j.properties:
> # These lines sets the logging level for the cocoon log file.
> # Set these to DEBUG to see extra detailed logging.
> log4j.logger.org.apache.cocoon=DEBUG, A3
> log4j.logger.cocoon=DEBUG, A3
> log4j.logger.org.springframework=DEBUG, A3
> # Do not change these lines
> log4j.additivity.org.apache.cocoon=false
> log4j.additivity.cocoon=false
> log4j.additivity.org.springframework=false
> # The name of the file appender
> log4j.appender.A3=org.dspace.app.util.DailyFileAppender
> # The filename of the log file created. A date stamp is appended to this
> log4j.appender.A3.File=/myopt/dspace-hcc/log/cocoon.log
> # Set this to yyyy-MM-DD for daily log files, or yyyy-MM for monthly files
> log4j.appender.A3.DatePattern=yyyy-MM-dd
> # The number of log files to keep, or 0 to keep them all
> log4j.appender.A3.MaxLogs=0
> # A2 uses PatternLayout.
> log4j.appender.A3.layout=org.apache.log4j.PatternLayout
> log4j.appender.A3.layout.ConversionPattern=%d %-5p %c %x - %m%n

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

------------------------------------------------------------------------------
Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester  
Wave(TM): Endpoint Security, Q1 2013 and "remains a good choice" in the  
endpoint security space. For insight on selecting the right partner to 
tackle endpoint security challenges, access the full report. 
http://p.sf.net/sfu/symantec-dev2dev
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to