Traps and Pitfalls in VisiBroker Application Development

Traps and Pitfalls in VisiBroker Application Development

[[VisiBroker - World class middleware - Wiki | Back]]

 

This series of articles talked about the traps and pitfalls commonly encountered in the VisiBroker application development world. We hope that these will empowered you the knowledge in avoiding pains and disruption in your upcoming projects plan in the development and maintenance.

VisiBroker for C++

[[Signal handling in VisiBroker for C++ application (Part One) |Unix/Linux signal handling issues in a multi-threaded application, Part One]] and [[Signal handling in VisiBroker for C++ application (Part Two) | Part Two]].

[[Issues in treating OMG IDL basic data types as native C++ types |The OMG IDL basic data types are not the same as the C++ native types]].

[[Issues of compiling VisiBroker C++ application in different operating platforms | The need in understanding the compiler directives and the shipped include headers]].

[[Memory management for common IDL types in VisiBroker for C++ | Memory management for common IDL types]].

VisiBroker for Java

[[Pitfall in creating multiple ORBs in VisiBroker for Java]].

 

[[VisiBroker - World class middleware - Wiki | Back]]

Labels (1)

DISCLAIMER:

Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
2 of 2
Last update:
‎2020-03-13 21:06
Updated by:
 
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.