COM/MTS Guide - Prolifics

More documents

Recommendations

Info

Implementing Methodson the screen, to JPL global variables, or to JPL variables declared in the screen'sunnamed JPL. Since any valid JPL syntax can be used, you could copy an incomingparameter into a property by using the property API.The client that made the request for a method is expecting values passed back to it inthe in/out and out parameters. It also expects a return value for the method as awhole, and it might also be checking for error codes, to determine whether some errorhas occurred while attempting to perform the method. To send these values back to theclients code like the following would be used:proc my_method(){. . .return_args (id, name)raise_exception -2return 0}For information on calling methods from a client screen, refer to page 4-3, “Accessingthe Component's Methods.”The return_args command works similarly to the receive_args command. Thevalues of the JPL variables in the list will be written to the in/out and out parametersof the method, based on the order of the parameters in the method's definition.The raise_exception command is used to send an error code back to the client. Theclient's error handler can then decide what to do based on the value sent. Microsoft hasdefined a set of exception codes for use in COM programming.The JPL return command is used to provide the return value for the method.3-14 Building COM Components
Implementing MethodsJPL VariablesFigure 3-6 This sample screen-level JPL module implements the component'smethods.JPL variables declared in the component's unnamed procedure are only available in thecomponent-level JPL; they will not be in scope for widget-level JPL or for calls fromthe client. To increase the scope of the variables, use the JPL global command.Implementing Methods in CIn C, rather than the JPL commands receive_args, return_args, andraise_exception, you would use the following functions:! sm_receive_args (char *)! sm_return_args (char *)! sm_raise_exception (int, char *)COM/MTS Guide 3-15
Page 1 and 2: TABLE OFCONTENTSContents:About This
Page 3 and 4: PantherCOM/MTS GuideRelease 5.4Docu
Page 5 and 6: TABLE OFCONTENTSContents:About This
Page 8 and 9: C. New Windows ExecutablesClient an
Page 10: Related InformationRelated Informat
Page 13 and 14: Contact Us!! Prolifics web site at
Page 15 and 16: CHAPTER1 OverviewPanther's COM supp
Page 17 and 18: COM Features! Security for componen
Page 20 and 21: COM/MTS Applications1-6 Overview
Page 22 and 23: Preparing for Application Developme
Page 24 and 25: Accessing Databases2-4 Starting Dev
Page 26 and 27: Creating Service ComponentsFigure 3
Page 29 and 30: Defining the Component's Interface!
Page 31 and 32: Defining the Component's InterfaceC
Page 33 and 34: Defining the Component's Interface!
Page 35 and 36: Defining the Component's InterfaceA
Page 37: Implementing MethodsImplementing Me
Page 41 and 42: Logging Server Messagesthe last tim
Page 43 and 44: Sample COM ComponentsProgramming fo
Page 45 and 46: Sample COM ComponentsFor informatio
Page 47 and 48: CHAPTER4 Building ClientScreensIn P
Page 49 and 50: Working with COM ComponentsIf a com
Page 51 and 52: Working with COM Componentsvars wsi
Page 53 and 54: Sample Client ScreensSample Client
Page 55 and 56: Sample Client Screens(Constants.PR_
Page 57 and 58: CHAPTER5 Deploying COMComponentsA C
Page 59 and 60: Steps for DeploymentThe default loc
Page 61 and 62: Registering Components for MTSCreat
Page 63 and 64: Registering Components for MTS4. Ch
Page 65 and 66: Using Database Transactions! sm_mts
Page 67 and 68: APPENDIXACOM/MTS UtilitiesThis chap
Page 69 and 70: APPENDIXBCOM SamplesThe Panther dis
Page 71 and 72: Description of the COM SamplesCalli
Page 76 and 77: Client and Web Application Broker E
Page 78 and 79: # Register the COM component using
Page 81: INDEXIndexAApplication directoryfor
Page 84: IndexI-4 COM/MTS Guide

COM/MTS Guide - Prolifics

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?