RE: MIF output from XT

[Kay Michael <Michael.Kay@xxxxxxx>]

> If it's appropriate to the list, could you give us a little 
> more detail on this please? Thanks.				...edN
> 
> > Registering the Java classes that form the interface to XT or
> > SAXON as a COM object, and then calling them from VB, should not be at
all 
> difficult.
> 
Install the Microsoft Java SDK and look in the help text for "javareg". This
command takes a Java class and installs it in the registry as a COM object,
allowing VB applications, ASP pages, etc, to call it just like any other
installed COM object. The actual COM interface is provided by a wrapper in
the Microsoft JVM, the Java class itself is not modified. The SDK
documentation includes full information on the type mappings, error
handling, etc, including a lot of detail on how to customise the mappings,
but I've never gone into the detail, because for simple Java interfaces I
haven't found it necessary: you just run javareg and Bob's your uncle. 

What I have done in the past is to write Java wrappers that deliberately
make the interface simple, e.g. by catching exceptions and turning them into
return codes: this is just laziness on my part to avoid having to understand
the more advanced features of the Microsoft technology.

Mike Kay


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list