Skip navigation FileNet logo
  Open Client Developer's Guide
  Search  |  Index  |  Glossary   |  
  
Close menu Overview
  About This Guide
  What's New in 3.3
  Open menu Introduction to the Toolkit
  Open menu Programming Considerations
Open menu Open Client Architecture
Open menu Developing for Process
Open menu Error and Exception Handling
Open menu Customizing the Framework
Globalization / Localization
Open menu General Information
   

Known Issues

Please note the following known issues:

Performance Impacts of Calling COM Objects from .NET

COM calls from .NET requires marshalling which impacts performance. Suggestion: minimize COM calls whenever possible.

Combining Multiple COM Calls

You cannot combine multiple COM calls in a single .NET statement, like this:

ComObj1.GetProp(ComObj2.getName())

This only occurs in some cases.

Type-Casting IDM Generic Object

You cannot type-cast an IDM generic object into other IDM objects such as document, folder or store search object. MS has a fix and will include in the .NET service release. As a work-around, use the IFn.. Hidden interface of the object in the type-cast statement. For example:

oGen = oLib.GetObject (…)

oDoc = Ctype (oGen, IDMObjects.IFnDocumentDual)

Performing Single Thread ADO Searches

When executing search using ADO, must set ASPCOMPAT = TRUE in aspx page. The rest of our IDM COM objects are running in STA (single thread model). In general, for STA objects you need to set the ASPCOMPAT flag and for MTA (multi thread model) objects you don't.

Calls to JiGlue

Calls to JiGlue cause the following known issues:

  • Multiple calls to Process Jiglue.dll seems to fail with Invalid Callee error. A solution can be obtained by NOT using ASPCOMPAT=true in any page that uses Jiglue.dll. The reason being is that Jiglue is the only COM object that runs as MTA (multi-threading model). The rest of our IDM COM objects are running in STA (single thread model). In general, for STA objects you need to set the ASPCOMPAT flag and for MTAs you don't.
  • Multiple calls to JiGlue can cause performance problems.
  • When retrieving data via calls to JiGlue, be aware that dates returned are in UTC-ISO date format