L PROTECTED]
Subject: Re: Using native call to Xalan-C++ from Java
On short transforms, the processor can spend 50% if its time initializing,
so you should use the XalanTransformer class if at all possible. You could
also use the C API, but there must be some way to proxy C++ objects in Java
th
Subject: Re: Using native call to
Xalan-C++ from Java
06/06/2001 06:05
> [EMAIL PROTECTED]
>
> yahoo.com> cc:
> [EMAIL PROTECTED], pat Sherry <[EMAIL PROTECTED]>, (bcc:
>
> David
David N Bertoni/CAM/Lotus)
06/05/2001 05:35 Subject: Re: Using native call to
Xalan-C++ from Ja
Got it to work. We are now able to make native calls to
Xalan-C++ from Java with an over 850% performance improvement
with our xml/xslt files. The xml test file size I'm using is
18.6KB and the xslt file size is 12.2KB. We expect these to
grow substantially in production.
Our current usage i
We just tested 1.3.1 for Solaris in our environment and the crash is gone.
Evidently there is a bug in 1.3.02 on Solaris; perhaps on HP too...?
Paul
At 07:36 AM 6/4/01 -0700, Mike Garcia wrote:
>Hey Paul,
>Glad to hear someone else is working on this too. We are using
>Java1.3 on HP but I deve
Hey Paul,
Glad to hear someone else is working on this too. We are using
Java1.3 on HP but I develop on NT. Right now we use Xalan Java
for our transformer but after messing around with Xalan C++ it
would be great to be able to make a native call since the
performance increase would be substanti
Hi Mike,
Just out of curiosity, what JVM are you using?
We're running XalanJ under JNI, and we've found that it crashes with the
1.3.02 Solaris JVM from Sun.
We had to revert to 1.2.2.
I'd be interested to hear how your adaptation goes, since one of the
reasons we decided to use Xalan was the
