xsl-list
[Top] [All Lists]

Re: problem matching attribute

2004-11-16 09:42:38
  this works:

  <xsl:template
  match="read-access/namespace-resource/security-role-mapping[attribute::name='
   consoleadmins']/user[attribute::name='guestadmin']">
     <xsl:copy> 
     <xsl:attribute name="name">foo</xsl:attribute>
     </xsl:copy>
  </xsl:template> 

since the xsl:copy in this case is always going to generate a user node
and the xsl:attribute is always going to generate a name attribute, you
don't really need either, it would be simpler, and equivalent to write:

<xsl:template
match="read-access/namespace-resource/security-role-mapping[attribute::name='consoleadmins']/user[attribute::name='guestadmin']">
     <user name="foo"/>
</xsl:template> 

also unless there are other security-role-mapping not under
namespace-resource you don't need to make the match pattern that long
either, something like

<xsl:template
match="security-role-mapping[(_at_)name='consoleadmins']/user[(_at_)name='guestadmin']">
     <user name="foo"/>
</xsl:template> 


David

________________________________________________________________________
This e-mail has been scanned for all viruses by Star. The
service is powered by MessageLabs. For more information on a proactive
anti-virus service working around the clock, around the globe, visit:
http://www.star.net.uk
________________________________________________________________________

--~------------------------------------------------------------------
XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--



<Prev in Thread] Current Thread [Next in Thread>