Rintu's Blog

Memory Management in Java - Stack and Heap  Memory management is a mechanism to allocate memory when new objects are created and free it when no longer needed. In Java, the memory is divided into 2 segments: STACK HEAP STACK The stack is the place where any local variables and methods are stored. The lifetime of variables on the stack is governed by the scope of the code . The scope is usually defined by an area of code in curly brackets, such as a method call, or for or while loop. Once the execution has left that scope, those variables declared in the scope are removed from the stack. When the stack memory fills up, and eventually any more method calls will not be able to allocate their necessary variables. This results in a StackOverflowError . HEAP The heap is the place where objects, instance variables and static variables are stored. The new keyword allocates memory on the Java heap. The heap is the main pool of memory, accessible to t

               

BOF                                                                                                        Business Object framework is the object oriented framework provided by Documentum to build, deploy, test and execute reusable business logic component known as Business Objects.   Types of BOF Modules:   TBO – Type Based Business Object SBO – Service Based Business Object Aspects Simple Module Steps to Create different type of Modules   TBO: As TBO depends on persistence object type, we can either modify the existing functionality of the persistence object or we can add new functionality. We will discuss below how to modify the default save functionality as well we add new functionality. For writing TBO we must have a persistence object type. It is always a good practice to create a sub type of existing documentum types without trying to modify the default one. So in our case we will create an object type my_document_tbo. We can create t