Sure, no problem.
Stephen E. Schuster
PeopleSoft Administrator
2000 Ashland Drive
Ashland, KY 41101
Office Phone 606.920.7447
Cell Phone 606.831.4590
_
From: Andrew Scott [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 06, 2004 6:45 PM
To: CF-Talk
Subject: RE: CF MX 6.1 and com objects
: RE: CF MX 6.1 and com objects
You probably do indeed have it working but not natively. .NET is the
replacement for COM. COM has a different internal architecture from .NET and
thus they are not compatibility natively. That is why you have to use the
RCW which translates specific calls from managed
Stephen E. Schuster
PeopleSoft Administrator
2000 Ashland Drive
Ashland, KY 41101
Office Phone 606.920.7447
Cell Phone 606.831.4590
-Original Message-
From: Andrew Scott [mailto:[EMAIL PROTECTED]
Sent: Monday, January 05, 2004 7:49 PM
To: CF-Talk
Subject: RE: CF MX 6.1 and com objects
, Steven [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 06, 2004 8:53 AM
To: CF-Talk
Subject: RE: CF MX 6.1 and com objects
You probably do indeed have it working but not natively. .NET is the
replacement for COM. COM has a different internal architecture from .NET and
thus
Bank Street
South Melbourne, Victoria, 3205
Phone: 03 9686 0485-Fax: 03 9699 7976
_
From: Schuster, Steven [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 7 January 2004 12:53 AM
To: CF-Talk
Subject: RE: CF MX 6.1 and com objects
You probably do indeed have it working but not natively. .NET
Sorry I should have also said that this is the error that I am getting as
well
The cause of this exception was that:
coldfusion.runtime.com.ComObjectInstantiationException: An exception
occurred when instantiating a Com object..
Regards
Andrew Scott
Technical Consultant
NuSphere Pty Ltd
Can't give you a complete answer but a part of one.
It has something to do with interfaces.CFMX requires the IDispatch
interface and something I read in a forum from a tech support person is that
.NET components don't expose this by default.The .NET docs indicate that
.NET COM wrappers are in
Are you trying to use a COM wrapper for a .NET object? If so, I would
recommend skipping the pain that is the Java-COM bridge and instead use
Black Knight
(http://montarasoftware.com/go/9d58a59e-df02-1157-affb-e87c411e1c8f).
Matt Liotta
Montara Software, Inc.
http://www.MontaraSoftware.com
On
: 03 9699 7976
_
From: Samuel R. Neff [mailto:[EMAIL PROTECTED]
Sent: Tuesday, 6 January 2004 10:42 AM
To: CF-Talk
Subject: RE: CF MX 6.1 and com objects
Can't give you a complete answer but a part of one.
It has something to do with interfaces.CFMX requires the IDispatch
interface
January 2004 10:51 AM
To: CF-Talk
Subject: Re: CF MX 6.1 and com objects
Are you trying to use a COM wrapper for a .NET object? If so, I would
recommend skipping the pain that is the Java-COM bridge and instead use
Black Knight
(http://montarasoftware.com/go/9d58a59e-df02-1157-affb-e87c411e1c8f
, January 05, 2004 7:04 PM
To: CF-Talk
Subject: RE: CF MX 6.1 and com objects
Matt,
How the hell do you think you know what I am doing...
Were did I say I was creating a wrapper, I am developing a
com object nothing more nothing less. The object has business
logic that will be widley used
.Net does support com, I have it working here now. Secondly I am creating
code that can be used by Windows Applications as well as ASP applications
and coldfusion applications that will share common business logic.
Blacknight does not support what I am trying to achive, so I am correct when
I say
12 matches
Mail list logo
