Thanks Hardy!
I'm not sure what I'm "trying to do". Great question, though. I validated
the XML for my sitemap.xmap and it said it was o.k. but I may have to end
up compiling your pom change in just in hopes of seeing something that is
wrong. I'm assuming the intention is that it kills a 'maven update' if it
finds something wrong?
Here's more about the BSU/sitemap.xmap. Working from the bottom of the
error stack, the block of code that starts the processing is the "Primary
(non-caching) Pipeline".
<map:pipeline>
<!-- Never allow the browser to cache dynamic content -->
<map:parameter name="expires" value="now"/>
<map:match pattern="**"> *(Line 170)*
<!-- Step 1: Generate the DRI page -->
<!-- This line actually initiates the Aspect chain. The
Aspect chain will build
the DRI (XML) content based on which page the user is
accessing. -->
<map:generate type="file" src="cocoon://DRI/{1}"/> *(Line
174)*
<!-- Step 2: Transform the DRI page into XHTML -->
<!-- This line calls the resource named
'transform-to-xhtml' (included above).
That resource is in charge of tranforming this DRI
content into XHTML -->
<map:call resource="transform-to-xhtml"/>
<!-- Step 3: Serialize to the browser (sends final XHTML to
user's browser) -->
<map:serialize type="xhtml"/> *(Line 182 - The last line
mentioned in the themes/BSU/ stack)*
</map:match>
</map:pipeline>
The next part of the stack is lines 70, 80, and 84:
<map:transform type="IncludePageMeta"> *(Line 70)*
<map:parameter name="stylesheet.screen#1"
value="lib/css/reset.css"/>
<map:parameter name="stylesheet.screen#2"
value="lib/css/base.css"/>
<map:parameter name="stylesheet.screen#3"
value="lib/css/helper.css"/>
<map:parameter name="stylesheet.screen#4"
value="lib/css/jquery-ui-1.8.15.custom.css"/>
<map:parameter name="stylesheet.screen#5"
value="lib/css/style.css"/>
<map:parameter name="stylesheet.screen#6"
value="lib/css/authority-control.css"/>
<map:parameter name="stylesheet.screen#7"
value="lib/css/BSU.css"/>
<map:parameter name="stylesheet.screen#8"
value="lib/css/jquery.bxslider.css"/>
</map:transform>
<map:transform type="IncludePageMeta"> *(Line 80)*
<map:parameter name="stylesheet.handheld"
value="lib/css/handheld.css"/>
<map:parameter name="stylesheet.print"
value="lib/css/print.css"/>
</map:transform>
<map:transform type="IncludePageMeta"> *(Line 84)*
<map:parameter name="stylesheet.all"
value="lib/css/media.css"/>
<map:parameter name="javascript"
value="lib/js/jquery-ui-1.8.15.custom.min.js"/> *(For some reason I'm
seeing every other include but not this one - it is in the same folder as
BSU.js)*
<map:parameter name="javascript" value="lib/js/BSU.js"/>
<map:parameter name="theme.path"
value="{global:theme-path}"/>
<map:parameter name="theme.name"
value="{global:theme-path}"/> *(***A possible typo?***)*
<map:parameter name="curRequestURI" value="{1}"/>
</map:transform>
Line 100 is:
<map:transform src="{global:theme-path}.xsl"/>
<!-- Localize the XHTML page (by replacing i18n tags) -->
<map:act type="locale">
<map:transform type="i18n">* (Line 104)*
<map:parameter name="locale" value="{locale}"/>
</map:transform>
</map:act>
*As far as protodocument.xml is concerned*, I don't think I created that. I
found it also here in github:
https://github.com/DSpace/DSpace/blob/77e8c9a77c4951c86f194458a9d3c5105ebce753/dspace-xmlui/src/main/webapp/aspects/aspects.xmap
Is that give any clues? My src/main/webapp/aspects/aspects.xmap is
identical.
I also noticed that the error I posted about first is a lot longer and
continues like this:
at <map:match> -
file:///E:/dspace/webapps/xmlui/themes/BSU/sitemap.xmap:170:37 *(already
shown; hundreds of lines follow though)*
org.apache.cocoon.ProcessingException: Failed to process pipeline
at <map:serialize type="xml"> -
file:///E:/dspace/webapps/xmlui/aspects/aspects.xmap:96:31
at <map:generate type="file"> -
file:///E:/dspace/webapps/xmlui/aspects/aspects.xmap:95:55
at <map:serialize type="xml"> -
resource://aspects/ViewArtifacts/sitemap.xmap:359:32
at <map:transform type="Navigation"> -
resource://aspects/ViewArtifacts/sitemap.xmap:91:59
at <map:generate> - resource://aspects/ViewArtifacts/sitemap.xmap:79:40
at <map:serialize type="xml"> -
resource://aspects/BrowseArtifacts/sitemap.xmap:108:40
at <map:transform type="Navigation"> -
resource://aspects/BrowseArtifacts/sitemap.xmap:47:47
at <map:generate> - resource://aspects/BrowseArtifacts/sitemap.xmap:41:28
at <map:serialize type="xml"> -
resource://aspects/Discovery/sitemap.xmap:214:40
at <map:transform type="Navigation"> -
resource://aspects/Discovery/sitemap.xmap:78:47
at <map:generate> - resource://aspects/Discovery/sitemap.xmap:66:28
at <map:serialize type="xml"> -
resource://aspects/Administrative/sitemap.xmap:1074:31
...
Caused by: org.apache.cocoon.ResourceNotFoundException: Page cannot be found
at
org.dspace.app.xmlui.aspect.general.PageNotFoundTransformer.addBody(PageNotFoundTransformer.java:170)
at
org.dspace.app.xmlui.wing.AbstractWingTransformer.startElement(AbstractWingTransformer.java:223)
... 314 more
I'll post this now and see if the additional info has helped. I'm not sure
why there would be a "page not found" error when I've never seen it
navigating around. I should mention that this error log is from a server
that is only accessible to a select few people while we prepare to make it
production and nobody involved in testing has mentioned any "page not
found" navigation errors.
Thanks!
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
