ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » ActiveX API

Post new topic  Reply to topic
 ActiveX API « View previous topic :: View next topic » 
Author Message
Milesi
PostPosted: Wed May 15, 2002 9:58 pm    Post subject: ActiveX API Reply with quote

Apprentice

Joined: 15 Apr 2002
Posts: 37

In order to substitute the workflow logic (Probably for some kind of demo on a custom client), I am trying to regroup all workflow API calls in a single dll. This dll then being linked to the custom client that in the end doesn't even have to know that workflow is at a lower logic level.

My problem is, in an ActiveX dll components, the IBM API activeX cannot be inserted. I get the following error:

IBM MQSeries Workflow Controls 3.3 is a single-threaded component and cannot be used in multi-Threaded projects. Change the Threading model for "MyProject" or contact the component vendor for an updated version.

The message is quite clear, but I am wondering if the same problem occurs while using JAVA or C++ API. Indeed changing the project to a single-threaded component means building a standart exe which doesn't serve my purpose.


Any help would be welcome.
Back to top
View user's profile Send private message Yahoo Messenger
Milesi
PostPosted: Wed May 15, 2002 10:31 pm    Post subject: Reply with quote

Apprentice

Joined: 15 Apr 2002
Posts: 37

I have tried to further invistagate the matter discussed above. Stop me if I am mistaken. Instead of building a dll, I can go for a ActiveX exe that then is a single-threaded component that can be referenced by another project the same way dlls are. But then there is something I don't catch. Why did IBM locked the possibility to use API controls as part of a standard dll (Actually pretty much in the same way ocx are reusable components).

Again, any info would be most welcome.

Thank you in advance.

Milesi

(PS: Anyone knows how to build ocx in VB ?)
Back to top
View user's profile Send private message Yahoo Messenger
RJoubert
PostPosted: Wed Jun 12, 2002 4:58 am    Post subject: Reply with quote

Apprentice

Joined: 30 May 2002
Posts: 43
Location: Buffalo, NY

There is a COM API available from IBM that does what you are trying to do. It does not use the ActiveX controls, and the object model is straight-forward and relatively easy to use. As I understand it, it is not being used by a lot of customers right now, so help may be tough to come by.
_________________
Rich Joubert
Computer Systems Engineer
Univera HealthCare, an Excellus Company
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » ActiveX API
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.