[ 
http://jira.dspace.org/jira/browse/DS-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=10515#action_10515
 ] 

Pongtawat edited comment on DS-239 at 8/31/09 7:10 AM:
-------------------------------------------------------

In our case, finally we have discover that adding the following line to the 
dspace.cfg fix the problem:

log.init.config = ${dspace.dir}/config/log4j.properties

I think this line should be added to "minimum set of parameters that need to be 
added to an old DSpace 1.4.2 configuration"

In addition, org.dspace.content.crosswalk.XHTMLHeadDisseminationCrosswalk 
should be added to 
plugin.selfnamed.org.dspace.content.crosswalk.DisseminationCrosswalk or the 
item won't show up:

plugin.selfnamed.org.dspace.content.crosswalk.DisseminationCrosswalk = \
  org.dspace.content.crosswalk.MODSDisseminationCrosswalk , \
  org.dspace.content.crosswalk.XSLTDisseminationCrosswalk, \
  org.dspace.content.crosswalk.QDCCrosswalk, \
  org.dspace.content.crosswalk.XHTMLHeadDisseminationCrosswalk

      was (Author: pongtawat):
    In our case, finally we have discover that adding the following line to the 
dspace.cfg fix the problem:

log.init.config = ${dspace.dir}/config/log4j.properties

I think this line should be added to "minimum set of parameters that need to be 
added to an old DSpace 1.4.2 configuration"
  
>  java.net.MalformedURLException: unknown protocol: resource
> -----------------------------------------------------------
>
>                 Key: DS-239
>                 URL: http://jira.dspace.org/jira/browse/DS-239
>             Project: DSpace 1.x
>          Issue Type: Bug
>          Components: XMLUI
>    Affects Versions: 1.5.2
>         Environment: Solaris 10, Fedora 9
>            Reporter: Mark Diggory
>             Fix For: 1.6.0
>
>         Attachments: Live.zip, stack.txt, Test.zip
>
>
> We currently have two instances of dspace that we use, a live dspace and 
> dspacetest.
>  
> Dspacetest was recently (about a month or two ago), upgraded from 1.5.1 to 
> 1.5.2, with no problems. You can see it in all it's glory here: 
> dspacetest.nt.gov.au
>  
>  
> Today, we attempted to upgrade our live dspace instance to 1.5.2. After 
> restarting tomcat though, we got a java.net.MalformedURLException: unknown 
> protocol: resource error (full stack trace included).
>  
> After looking around I found that in 1.5.1 there was a cocoon.xconf which 
> included
>  
>     <component-instance 
> class="org.apache.excalibur.source.impl.ResourceSourceFactory" 
> name="resource"/>
> which I assume is pointing to the resource. Looking around I couldn't find 
> cocoon.xconf anywhere in 1.5.2 and thought it must have been removed. But 
> still needing the site to work I included it back in webapps/xmlui/WEB-INF, 
> which still did nothing at the time.
>  
> Looking in webapps/xmlui/WEB-INF/web.xml shows that 1.5.1 included
>  
>     <servlet>
>         <servlet-name>Cocoon</servlet-name>
>         <display-name>Cocoon</display-name>
>         <description>Cocoon</description>
>         <servlet-class>
>             org.dspace.app.xmlui.cocoon.DSpaceCocoonServlet
>         </servlet-class>
>         <init-param>
>             <param-name>configurations</param-name>
>             <param-value>/WEB-INF/cocoon.xconf</param-value>
>         </init-param>
>  
> but that 1.5.2 doesn't and seems to use DSpaceCocoonServletFilter instead(?)
>  
> After playing around a bit more, moving files here and there, finally I 
> received no more errors and could view the webpage. However it turns out that 
> all I did was return the xmlui/WEB-INF folder to its exact state before 
> upgrading to 1.5.2, so that technically the site was still running on 1.5.1 
> code.
>  
>  
> What I would like is any assistance if possible, as to why I would get this 
> error on one instance of dspace, after another instance had been upgraded 
> properly.
>  
> To go through my processes for upgrading:
>  
> ran mvn package in src/dspace-1.5.2-src-release
> turned off tomcat (which by the way, both instances of dspace are using the 
> same instance of tomcat)
> ran ant update in 
> src/dspace-1.5.2-src-release/dspace/target/dspace-1.5.2-build.dir
> ran ant update_configs in 
> src/dspace-1.5.2-src-release/dspace/target/dspace-1.5.2-build.dir (which is 
> redudant?)
> restarted tomcat
>  
> If it helps the live site is www.territorystories.nt.gov.au, and though looks 
> good is using 1.5.1 code.
>  
>  
>  
> Thanks
> Jennifer Whalan

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.dspace.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Dspace-devel mailing list
Dspace-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to