Skip navigation
Bradykinin
Currently Being Moderated

Example of Cold Fusion 9 using a COM object?

Mar 7, 2012 12:53 PM

We're not able to get COM of .NET objects working with Cold Fusion 9 and a third-party application. The vendor for the 3rd-party app has done some testing with their COM objects, as well as unrelated COM objects and they can't get any of them to work. This also matches our experience. Their hypothesis is that Cold Fusion 9 won't work with any COM objects. This seems surprising to me and I suspect that we are all implementing them incorrectly.

 

Can somebody provide an example implementation of CF9 with a COM (or .NET) object that we can test (preferably an implementation that is already tested to work). That will help us troubleshoot the source of the problem.

 

Our systems is Window 2008 server 64-bit. I don't know if the vendor is on the same O/S.

 
Replies
  • Currently Being Moderated
    Mar 7, 2012 1:35 PM   in reply to Bradykinin
     
    |
    Mark as:
  • Currently Being Moderated
    Mar 9, 2012 1:24 PM   in reply to Bradykinin

    A brief search suggests ActivePDF offers a .net wrapper. You might try using that instead.

        http://www.activepdf.com/corporate/news/pressreleases/NetRelease.cfm

     

     

       NetRelease.cfm

     

    Hey.. the ActivePDF site runs CF. Nice ;-)

     

    Message was edited by: -==cfSearching==-

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 19, 2012 3:16 PM   in reply to Bradykinin

    We too are experiencing the same issue with COM on 64-bit ColdFusion install on Win 2008 R2 (64-bit).  We've even tried connecting to COM through a Java proxy generated by J-Integra's 'com2java' utility (mapped via 'neo-comobjmap.xml') and still no luck.  Can someone at Adobe please give us a viable solution or at least explain as to why this is not being supported/fixed?  Going back to a 32-bit OS just doesn't seem like a good option for us.  Any help/answers would be greatly appreciated!  Thanks!

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 19, 2012 5:47 PM   in reply to nickadel

    (These are user forums, so you will not get answers from adobe employees here.)

     

     

    From what I understand it is due to jvm limitations.

           http://forums.adobe.com/message/4268918

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 20, 2012 1:10 AM   in reply to -==cfSearching==-

    The solution is to do away with using COM objects; it's an old technology so no-one's bothering to put the hours into supporting it. In these days of not only .NET assemblies for Windows but also SOAP and webservices, there's not really much need for such a clunky old technology.

     

    If you really rely on a COM object, I'd suggest looking into alternatives if there are any.

     
    |
    Mark as:
  • Currently Being Moderated
    Mar 22, 2012 10:43 AM   in reply to Owain North

    Okay, got it.  Thanks for the reply guys.  In a perfect world, this particular COM object we're relying on would not exist, but unfortunately, I have to make it work.  I had no choice but to use CFEXECUTE which calls a VB shell (cscript), then wrapped it in a web service component.  This hack, I can confirm, works.

     
    |
    Mark as:

More Like This

  • Retrieving data ...

Bookmarked By (1)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points