RE: Xslt protect with password
This appears to boil down to the same problem countless people have been trying to solve using DRM, and so far have failed to do, as once you give the XSLT to a third party, they will need the clear-text in able to run it through an XSLT processor. You could wrap both the XSLT and a processor into compiled code, making this somewhat more complex, but certainly not impossible for a person intend on extracting determining the inner workings of your code.
The alternative would be to keep the XSLT on a server under your control, and provide the transformation as a service.
It appears the problem is "I do not trust the vendor to play nice with my code" and I suggest, instead of trying a technological solution (which might be unacceptable to your vendor for various reasons), the proper way to resolve this is a good contract with the vendor on what it can do with the code and what not. The terms of your contract will probably depend on the level of "general purposeness" versus "tailor made for vendor" of your code, as well as the level of "vendor lock-in" for future support on the code you want to achieve.
Quoting Praveen Chauhan <praveen.chauhan@xxxxxxxxxxxxxx>:
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format