Community
Participate
Working Groups
We need to allow users to provide important application info, such as the application name, for instances where the logic in SDOHelperContext isn't sufficient. Specific case: When a thread is non-weblogic-managed thread, SDO code can't find out the caller's application name. It results in HeperContext loaded by application will not be used. It forces SDO users to setup the classloader/helpercontext mapping. In most of case, SDO users (e.g. ADF service) won't be able to map all classloaders in a App's classloader hierarchy to the right helper context. We will add an abstract class as opposed to an interface to allow additional methods to be added w/o breaking implementers. For now we will have a single abstract method: public String getApplicationName()
Created attachment 181537 [details] Proposed code changes for the 2.1.2 stream
Created attachment 181538 [details] Proposed code changes for the 2.2 stream
Fix checked into the 2.1.2 Stream. Reviewed by matt.macivor@oracle.com; blaise.doughan@oracle.com Tests: all SDO unit tests pass as expected; WebLogic server test passes as expected Revision: 8392
Fix checked into the 2.2 Stream. Reviewed by matt.macivor@oracle.com; blaise.doughan@oracle.com Tests: all SDO unit tests pass as expected; WebLogic server test passes as expected Revision: 8393
Fixed.
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink