<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
        {font-family:"Segoe UI";
        panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:11.0pt;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
a:link, span.MsoHyperlink
        {mso-style-priority:99;
        color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {mso-style-priority:99;
        color:purple;
        text-decoration:underline;}
p
        {mso-style-priority:99;
        margin-top:12.0pt;
        margin-right:0in;
        margin-bottom:12.0pt;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";
        color:black;}
code
        {mso-style-priority:99;
        font-family:"Courier New";}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:10.0pt;
        font-family:"Courier New";
        color:windowtext;}
span.EmailStyle17
        {mso-style-type:personal-compose;
        font-family:"Calibri","sans-serif";
        color:windowtext;}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:"Courier New";}
.MsoChpDefault
        {mso-style-type:export-only;
        font-family:"Calibri","sans-serif";}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Hi Mailing List, <o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I have a question about a change in the CmsSolrDocumentXmlContent class.  The javadoc for the extract content method states that all XML nodes will be in the item map and the XML elements will be accessible using xpath.<o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>In 8.5.0 all XML nodes were in the content items map, in 8.5.1, not all XML nodes are available in in the content items map.  Looking at the code history, the following line was removed from the CmsSolrDocumentXmlContent class:<o:p></o:p></span></p><p class=MsoNormal style='line-height:12.0pt'><span style='color:#1F497D'>                    items.put(xpath, extracted);<o:p></o:p></span></p><p class=MsoNormal style='line-height:12.0pt'><span style='color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal style='line-height:12.0pt'><span style='color:#1F497D'>Here is the javadoc for the extract content method:<o:p></o:p></span></p><p style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Returns the raw text content of a given VFS resource of type </span><code><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>CmsResourceTypeXmlContent</span></code><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>. <o:p></o:p></span></p><p style='margin-left:.5in'><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>All XML nodes from the content for all locales will be stored separately in the item map which you can access using </span><code><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><a href="eclipse-javadoc:%E2%98%82=com.dispatch.framework/C:%5C/Users%5C/jvalentine%5C/.m2%5C/repository%5C/org%5C/opencms%5C/opencms-core%5C/8.5.1%5C/opencms-core-8.5.1.jar%3Corg.opencms.search.documents(CmsDocumentXmlContent.class%E2%98%83CmsDocumentXmlContent~extractContent~Lorg.opencms.file.CmsObject;~Lorg.opencms.file.CmsResource;~Lorg.opencms.search.CmsSearchIndex;%E2%98%82CmsExtractionResult%E2%98%82getContentItems%E2%98%82"><span style='color:#1F497D'>CmsExtractionResult.getContentItems()</span></a></span></code><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>. The XML elements will be accessible using their xpath. The xpath will have the form like for example </span><code><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Text[1]</span></code><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> or </span><code><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Nested[1]/Text[1]</span></code><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>.<o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Was this change by design?  If so, how may we access all the XML nodes in the content items map?<o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Let me know if anyone has any questions.<o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks,<o:p></o:p></span></p><p><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>~John<o:p></o:p></span></p></div></body></html>