Policy Builder and XSLT
Novell Cool Solutions: Question & Answer
Reader Rating 
Q:
I have implemented a development system with an Identity Vault, a Workforce Tree, a regular Tree, an LDAP Tree, Groupwise, and Active Directory. Everything works fine, including password synchronization.
I did everything in Policy Builder. I wrote no XSL and no XPATH. I see so many posts regarding XSL or JAVA or XPATH that I am starting to think I did something wrong - yet everything works!
I do not know XSL or XPATH or JAVA, so I am just questioning whether I can
even put such a beast in production. But as I said, it actually works
flawlessly.
Am I crazy? Did I miss something? Why is everyone writing all this XSL or
XPATH or JAVA!!!!
A:
If you were able to do everything in Policy Builder, that validates the design for Policy Builder and for DirXML Script (the language that Policy Builder manipulates). The goal of Policy Builder is to eliminate the need for XSLT in most cases.
So, no, you didn't do anything wrong. You just didn't encounter (yet)
anything you wanted to do that couldn't be done. You will also find that the majority of posts that refer to XSLT are talking about DirXML 1.x, which doesn't have policy builder, or by people that have upgraded from DirXML 1.x.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com