Hmm,
There may be an easier answer than this, but you can always put any jar in:
custom\classes
Alternately, you can specify a separate JVM by putting a directive in an acl
file in custom\init that reads:
set javavmpath="C:\JVMDIR\jvm.dll"
Though I'd be cautious about the second one, since I'm not sure how well
newer JVM's would play with the built-in Arbortext libraries.
keith
On Wed, Aug 20, 2008 at 11:24 AM, Hicks, Todd
<todd.hicks@wolterskluwer.com>wrote:
> I see where the JRE for 5.3M020 is 1.5.0_11. We want to start using
> javax.xml goodies. I'm not sure what JRE is on the Citrix boxes we have
> Arbortext Editor running on.
>
> I have the impression that it doesn't actually matter – that Java called
> from ACL is running in Arbortext Editor's memory space, and is using the
> Java engine that ships with Arbortext Editor. But I admit it, I am pretty
> green when it comes to Java, and I have this feeling like I don't really get
> it. Are we concerned more with the JRE, or the JVM?
>
> Q: Can we fire off Java code that imports javax.xml? Or to put it another
> way, what do we need to do in order to make that possible besides actually
> having the javax.xml jar in our classpath?
>
> Todd Hicks
> *Manager, Editorial Desktop - Content Technology **
> Wolters Kluwer Global Platform Organization*
> (415) 785-4546 (Office)
> todd.hicks@wolterskluwer.com
>
>
>
>
