This makes absolutely no sense whatsover. Here is the code of
XalanInitialize() that you say works:
XALAN_TRANSFORMER_EXPORT_FUNCTION(void)
XalanInitialize()
{
// Call the static initializer for Xerces.
XMLPlatformUtils::Initialize();
// Initialize Xalan.
XalanTransformer::initialize();
}
So how does it work from our API call, but not from your code? If you're
sure you're using the correct runtimes, then you should check the service
pack of Visual Studio you're using. Our documentation states clearly that
we use SP3. If you're using something different, then you should rebuild
both Xerces and Xalan with your compiler.
If you cannot initialize Xerces and Xalan properly through calling
XMLPlatformUtils::Initialize() and XalanTransformer::initialize(). then
intializing through the C API is only going delay the problem until you try
to do something with the library. Of course, you can use the C API
exclusively, which would also be a work-around, but you probably don't want
to do that.
Dave
"+Z5c- +W1CCrw-"
<[EMAIL PROTECTED] To:
[email protected]
mail.com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
Subject: Re: problems in
initalising DOMParser object within xalan-c for dom input/output
04/18/2002 10:14
AM
Hi Dave
the only reason why i use the xalan's C API is because it will not
initialise properly if i initialise the xalan and xerces through the c+-+-
API XMLPlatformUtils::Initialize() and xalanTransformer::initialize().(i
initialise xerces and xalan in the constructor of Myapp (the CWinapp class)
and terminates it in the deconstructor). in fact it will not perform
transformation at all under debug version (but it will in release version)
and i have check that the debug bulid uses Debug Multithreaded DLL and
releases uses Multithreaded DLL. and it still gives me the same
problem..... :(
do you have suggestion over this, please help....
Many thanks
regards
kit
>From: "David N Bertoni/Cambridge/IBM" <[EMAIL PROTECTED]>
>To: [email protected]
>Subject: Re: problems in initalising DOMParser object within xalan-c for
dom input/output
>Date: Thu, 18 Apr 2002 09:25:19 -0700
>
>
>I'm very confused by your description of the problem.
>
>If you're using C+--+--, there's no need to use Xalan's C API, so I don't
>understand why you're using it. In your program's main() function, before
>you make any Xerces or Xalan calls, you should call
>XMLPlatformUtils::Initialize() and XalanTransformer::initialize(). When
>your program is about to exit, you should call XMLPlatformUtils::Terminate
>() and XalanTransformer::terminate(), if you're interested in having
memory
>freed for the purposes of detecting memory leaks.
>
>Please make sure you're linking with the proper run-time libraries. You
>must use the Multithreaded DLL, or Debug Multithreaded DLL libraries.
>Often, a debug build will crash when linked using the wrong run-time, even
>though a release build will not.
>
>The Xerces binaries that come with Xalan are directly from their
>distribution. If they were corrupt, we certainly would have heard of it
by
>now and replaced the distribution.
>
>Dave
>
>
>
>
> "+-Z5c- +-W1CCrw-"
> <[EMAIL PROTECTED] To:
[email protected]
> mail.com> cc: (bcc: David N
Bertoni/Cambridge/IBM)
> Subject: Re: problems in
initalising DOMParser object within xalan-c for dom
> 04/18/2002 03:33 input/output
> AM
>
>
>
>
>
>Hi... just adding more information regarding this question, actually
xerces
>
>is initialised however i find there is one thing that is interesting....
on
>
>the release version everything works fine with no complaint whatsoever,
but
>
>in the debug version it complains abouts it (in fact i could not
initialise
>
>xerces properly without calling it through the xalanCAPI, whereas the
>release version works fine with both methods of initialising from
xalancAPI
>
>and XMLPlatformUtils::Initialize();)
>
>i might be totally wrong but i was wondering could it be problems with
>xerces1.6.0D.dll that comes with xalan?
>
>mank thanks
>Regards
>Kit
>
>P.S. sorry this question may lies within the xerces-c mailing list but
>since i am using the xerces parser from xalan i thought it is more
>appropiate to sent it through the xalan mail list, i am sorry if this has
>cause any inconvience
>
>
>_________________________________________________________________
>+-T391KA- MSN
Messenger+-/wyCB2cLU8tXKH3aTgqASlkp/xo-http://messenger.msn.com.hk
>
>
>
>
>
>
_________________________________________________________________
+Vyg- http://explorer.msn.com.hk/intl.asp +UU2Mu04Ljwk- MSN Explorer
