SOA 11g - WSIF That Calls a Java Class Has a Different Behavior on 11g Than It Did on 10g
(Doc ID 1585197.1)
Last updated on SEPTEMBER 25, 2013
Applies to:Oracle SOA Suite - Version 18.104.22.168.0 and later
Information in this document applies to any platform.
When calling a BPEL process that in turn makes a call to a Java partnerlink via a WSIF Binding, the Java class constructor is called every time the BPEL instance is initialized.
However, the constructor is called only one time in 10g and every subsequent BPEL initialization calls the methods from the same Java instance. (One to Many)
Therefore when porting 10g Java code, the behavior in 11g for handling global connections/resources are initialized in the constructor and are no longer efficient, as the constructor is called everytime when creating a new instance of the Java class, every time the BPEL is initialized. (One to One)
This document explains how to have the same behavior in 11g as it did in 10g.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document