[xep-support] Using the COM interface

[Steven Caton]

I guess this means that full COM wrapper interfaces are provided for XEP in
the commercial release?  As my company is entirely an NT shop, this might
help me convince some that this is indeed a worthwhile purchase (though it
wouldn't be difficult, I suppose, to wrap the java classes myself).  We are
looking to automate the generation of perhaps 5,000 pdf documents a day,
both from the web and from back-office processes.  Do these objects run well
within a COM+/MTS environment?


Thanks,
Steven Caton
ConsumerInfo.Com

-----Original Message-----
From: Peter Drivas [mailto:peter.drivas at gexinc.com]
Sent: Friday, February 08, 2002 6:44 AM
To: xep-support at renderx.com
Subject: [xep-support] Using the COM interface


Hi,

I'm trying to run the C client provided with the XEP distribution. I set the
CLASSPATH as described in the readme (
C:\XEP\lib\xep.jar;C:\XEP\lib\JimiProClasses.zip;C:\XEP\lib\xerces-1.2.3.jar
 ) and successfully registered the driver. My base directory is C:\XEP. The
driver is located in C:\WINNT\JAVA\TRUSTLIB\COM\renderx\XEPCOM. I'm running
on Windows NT 4.0.

I run the xep.bat file, so the Root is set
to -Dcom.renderx.FO2PDF.ROOT=C:\XEP\. It appears that the object is created
and the root is set, but the call to 'render' fails. It looks like it can't
find the class definition.

I looked in the registry and found that the driver is registered as
"com.renderx.XEPCOM.COMDriver". It looks like it's trying to access
"com.renderx.FO2PDF.render". Is it possible that there's a naming mismatch?
Anybody have experience with this and know why it would fail?

Thanks,
Peter Drivas
GEX, Inc.


-------------------
By using the Service, you expressly agree to these Terms of Service
http://www.renderx.com/tos.html
-------------------
By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html