![]() ![]() |
|
Open Client Developer's Guide | |
Search | Index | Glossary | | |
![]() |
|
![]() |
![]() |
![]() |
Guidelines for Creating Process Open Client ASPX PagesIf you are developing a Process Open Client application, you will use JiGlue to provide the COM Bridge between the Data Providers and Process services (the JiGlue COM Bridge provides the ability to make VB.NET calls to the Java API with the effect of native Java statements for most Win32 programming tasks). Before developing a Process Open Client application using ASPX pages, refer to Guidelines for Creating ASPX page. In addition, there are a number of JiGlue and COM-related issues to keep in mind when creating your ASPX pages and User Controls, including:
Using JiGlue If you are not going to use the out-of-the-box Step Processor and the FnProcessStepProcDP Data Provider, you will need to specify a Data Provider that will provide the JiGlue interface. For example, to use JiGlue to help create and instantiate a Process VWSession object and logon, you might use VB.NET example code similar to:
where, strRouterURL is the URL of the router for the Process server. Declaring Integer Arrays If you are developing using both Java and VB.NET (for example, using JiGlue) and want to declare an integer array, be aware that in Visual Basic, an integer is a 16-bit value, whereas in Java (and for the Process API), an integer is a 32-bit value. For instance, if you specify a 2-byte integer array in Visual Basic, it might be mapped in JiGlue to java.lang.Short, causing the Java API to throw an exception. For example, the following call to setDataFields will fail:
For additional information on JiGlue (including guidelines and the JiGlue COM Bridge conversions between COM data types and Java data types), see the FileNet Process Developer's Guide. |
![]() |
|