Making COM componts from java MSXML (Was: MS XML Parser on the Server)

[Dr. Zheng Min]

A few questions about making java MSXML COM aware:

1. Mike suggested using ActiveX Wizard for Java to create .IDL file. Has
anyone done it successfully? I tried it just now but a lot of method were
skipped because of non-translatible type (why is that? Does it mean those
methods can't be used in COM interface?).

2. Even worse, I can't re-compile MSXML in J++. I stuck in the first file --
com.ms.xml.dso.XMLDSO.java. The error messages are all in the same type:
        Value for argument 'parent' cannot be converted from 'int' in call
to 'Element ElementFactory.createElement(Element parent, int type, Name tag,
String text)'

The statement in XMLDSO.java is:
    e = factory.createElement(Element.ELEMENT,
XMLRowsetProvider.nameROWSET);
It doesn't look right but I don't know how MS can make *.class from it (or I
missed something?).

 Has anyone tried to recompile it and succeeded.

Thank,
Min




-----Original Message-----
From: Mike Dierken <mike at datachannel.com>
To: 'Jim Lears' <JimL at Alphag.net>; xml-dev at ic.ac.uk <xml-dev at ic.ac.uk>
Date: Sunday, February 22, 1998 8:03 AM
Subject: RE: MS XML Parser on the Server


>On the MS platform, you can expose all your Java classes and interfaces as
COM interfaces if you use the ActiveX Wizard for Java (JAVAIDL.EXE). It'll
create an .IDL file (and  .C and .H files if you want to call the interfaces
from C/C++).
>All Java classes are exposed asl dual interfaces, derived from IDispatch,
which allows them to be called from all COM aware scripting languages
(JavaScript, VB for Automation, etc).
>
>If the Java classes are registered with Javareg (using the CLSIDs from the
generated .IDL file) on the server, you can use the package name rather than
a CLSID.
>To create a Java object, you might try prepending 'java:' on the package
name.
> Server.CreateObject("java:com.ms.xml.om.Document")
>
>Hope this helps...
>
>Mike D
>DataChannel
>
>-----Original Message-----
>From: Jim Lears [SMTP:JimL at Alphag.net]
>Sent: Saturday, February 21, 1998 3:36 PM
>To: xml-dev at ic.ac.uk
>Subject: RE: MS XML Parser on the Server
>
>Server.CreateObject in VBScript is used for creating instances of COM
>objects. The Java XML Parser doesn't expose any COM interfaces...notably
>IClassFactory which is used to instantiate COM objects. The C++ version
>is what you need...its an ActiveX control. The source code for both
>parsers is available. If you insist on using the Java version, you could
>mod it up to sport a COM interface..
>
>
>Helping To Destroy The English Language
>
> -----Original Message-----
> From: Mike Wagner [SMTP:mwagner at ets.org]
> Sent: Friday, February 20, 1998 3:33 PM
> To: xml-dev at ic.ac.uk
> Subject: MS XML Parser on the Server
>
> Has anybody managed to get the Microsoft Java XML Parser running
>as a
> component accessible by ASP under IIS? I tried what seemed to me
>to be the
> obvious approach and that didn't work. I copied the java classes
>to the
> TrustLib directory, then registered them with javareg. (An
>excerpt of the
> BAT I used file is at the end of this message). However, when I
>try a
> simple Server.CreateObject("com.ms.xml.om.Document") call in an
>ASP page,
> it dies with the following error:
>
> Microsoft JScript runtime error '800a01ad'
>
> Automation server can't create object
>
> /xmltest.asp, line 14
>
> Any insights? Thanks.
>
> Mike Wagner
> Educational Testing Service
> mwagner at ets.org
>
> -----------------Javareg BAT file--------------------
> cd \winnt\java\trustlib\com\ms\xml\dso
> javareg /register /class:SchemaNode
>/progid:com.ms.xml.dso.SchemaNode
> cd \winnt\java\trustlib\com\ms\xml\dso
> javareg /register /class:XMLDSO /progid:com.ms.xml.dso.XMLDSO
> cd \winnt\java\trustlib\com\ms\xml\dso
> javareg /register /class:XMLParserThread
> /progid:com.ms.xml.dso.XMLParserThread
> cd \winnt\java\trustlib\com\ms\xml\dso
> javareg /register /class:XMLRowsetProvider
> /progid:com.ms.xml.dso.XMLRowsetProvider
> cd \winnt\java\trustlib\com\ms\xml\om
>
>
>
> xml-dev: A list for W3C XML Developers. To post,
>mailto:xml-dev at ic.ac.uk
> Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
> To (un)subscribe, mailto:majordomo at ic.ac.uk the following
>message;
> (un)subscribe xml-dev
> To subscribe to the digests, mailto:majordomo at ic.ac.uk the
>following message;
> subscribe xml-dev-digest
> List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
>
>xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
>Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
>To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
>(un)subscribe xml-dev
>To subscribe to the digests, mailto:majordomo at ic.ac.uk the following
message;
>subscribe xml-dev-digest
>List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
>
>
>xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
>Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
>To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
>(un)subscribe xml-dev
>To subscribe to the digests, mailto:majordomo at ic.ac.uk the following
message;
>subscribe xml-dev-digest
>List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)
>
>


xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)