As far as I know, there are no dependencies on the names of the libraries, etc. However, we do not test for such problems, so you'll be on your own.
There is an issue with renaming the Xerces DLL, since it looks for the file
name to load resource strings. I believe this was fixed fairly recently,
but you'll need to investigate. Try the Xerces mailing list, or search in
Bugzilla.
Dave
Samar Abbas
Lotia To: "'[EMAIL PROTECTED]'"
<slotia@nQuir <[EMAIL PROTECTED]>
e.com> cc: (bcc: David N Bertoni/CAM/Lotus)
Subject: Renaming Xalan DLLs (Win32)
11/14/2001
07:35 PM
Please
respond to
xalan-dev
We foresee a need to ship our product with a privately named version of the
Xalan libraries and I'm wondering if people have tried to do this before.
For those/any of you that have tried this, are there any specific things we
should be watching out for?
More specifically, to the Xalan developers, do the individual libraries
rely on the names of the other libraries being the same as the shipping
configuration?
Thanks,
Samar Lotia
