xml - XSL1.0 - Apply-templates only takes the first child node -


i'm working on new addition report dip-sensor data. i'm running problem apply-templates checks first <filter> node , not rest.

i have tried changing code use for-each instead of apply-templates, still no luck.

xml file:

... </dlp-sensor> <dlp-sensor>   <name>dlpsensor.1</name>   <description/>   <property>0</property>   <filter-list>     <filter>       <enabled>true</enabled>       <source>         <type>6</type>         <any/>       </source>       <destination>         <type>6</type>         <any/>       </destination>       <dlp-action>         <smtp-action>lock</smtp-action>         <action>drop</action>         <log>1</log>         <alarm>0</alarm>       </dlp-action>     </filter>     <filter>       <enabled>true</enabled>       <source>         <type>3</type>         <email-addr>blah@uneducated.edu</email-addr>       </source>       <destination>         <type>1</type>         <host-ip-addr>192.1.1.1</host-ip-addr>       </destination>       <dlp-action>         <smtp-action>block</smtp-action>         <action>drop</action>         <log>1</log>         <alarm>dlp</alarm>       </dlp-action>     </filter>     <filter>       <enabled>true</enabled>       <source>         <type>4</type>         <auth-user>ninja-hacker</auth-user>       </source>       <destination>         <type>3</type>         <email-addr>ceo@companyowner.edu</email-addr>       </destination>       <dlp-action>         <smtp-action>strip</smtp-action>         <action>block</action>         <log>0</log>         <alarm>0</alarm>       </dlp-action>     </filter>   </filter-list> </dlp-sensor> <dlp-sensor> ...

xsl v1.0:

<xsl:template match="dlp-sensor" mode="dlpdetails">     <table>         <tr>             <th class="second_head"><xsl:call-template name="getresource"><xsl:with-param name="resid" select="'source'"/></xsl:call-template></th>             <th class="second_head"><xsl:call-template name="getresource"><xsl:with-param name="resid" select="'destination'"/></xsl:call-template></th>         </tr>         <xsl:apply-templates select="filter-list/filter" mode="filtering"/>      </table> </xsl:template>  <xsl:template match="filter" mode="filtering">     <tr>         <td>             <xsl:value-of select="source/type"/>         </td>         <td>             <xsl:value-of select="destination/type"/>         </td>     </tr> </xsl:template>

result: 66

desired: 663143

the results show 66 should show 663143 because should have captured source/type , destination/type 3 <filter> nodes in <filter-list>.

there can amount of <dlp-sensor> , each might have different amount of <filter>. doing wrong?

you have spelling error:

<xsl:apply-templates select="filter-list/filter" mode="filtering"/>

also perhaps try <xsl:for-each select="dlp-sensor/filter-list"> followed <**xsl:apply-templates** select="filter">


Comments

Post a Comment

Popular posts from this blog

javascript - jquery or ashx not working -

i using ajax file upload control. it creating html: <form action="/pages/handlers/asyncfileuploadhandler.ashx" method="post" enctype="multipart/form-data" target="ajaxuploader-iframe-1397144545"> <input type="hidden" name="type" value="mindvoice"> <input type="file" id="imagefile" style="display: block; width: 80%; margin-right: auto; margin-left: auto;"> </form> and target is: <iframe width="0" height="0" style="display:none;" name="ajaxuploader-iframe-1397144545" id="ajaxuploader-iframe-1397144545"></iframe> the form submitted using .submit() . my ashx handler: <%@ webhandler language="c#" class="asyncfileuploadhandler" %> using system; using system.web; using nettpals.core; public class asyncfileuploadhandler : ihttphandler { public void processre...
Read more

opencv - DataType<cv::detail::deriv_type>::depth what is it used for -

i wondering why line used in lucas kanade tracker in opencv: datatype<cv::detail::deriv_type>::depth can explain me? in opencv, depth of mat refers type of data contained in mat 's data buffer. represented integer values correspond given data type. these integers commonly abstracted appropriate macro definition (e.g. uchar data represented macro cv_8u ). cv::datatype type-traits class provides method obtain corresponding integer value without having memorize macro means data type. there few cases user code needs use datatype::depth . more common datatype::type . a simple example shows 1 possible use of datatype::depth : cv::mat uchar_data = cv::mat::ones(3, 3, cv_8uc1); cv::mat float_data; uchar_data.convertto(float_data, cv::datatype<float>::depth); // ^^ equivalently replaced // cv_32f macro float_data.at<float>(0,1) += 0.5f; std::cout << float_data << std::endl;...
Read more

python 3.x - Mapping specific letters onto a list of words -

can please suggest approach write piece of codes automatically maps letter in letter_str onto dic_key (a dict key string type contains dashes match length of words in word_lst)? so, mapping occurs if letter appears in every words in list @ same position no matter how many words in list. if no letter appears @ position words in word list new_dic_key '----'. please see examples below thanks word_lst = ['ague', 'bute', 'byre', 'came', 'case', 'doze'] dic_key = '----' letters_str ='abcdefghijklmnopqrstuvwxyz' new_dic_key = '---e' if word_list = ['bute', 'byre'] new_dic_key = 'b--e' or word_list = ['drek', 'drew', 'dyes'] new_dic_key = 'd-e-' if words in word_list of same length code give want: word_list = ['drek', 'drew', 'dyes'] cols = [] in range(len(word_list[0])): cols.append([]) word in ...
Read more