Last updated on NOVEMBER 05, 2016
Applies to:Oracle Weblogic Server - Version 10.3.2 and later
Information in this document applies to any platform.
***Checked for relevance on 1-Aug-2013***
After upgrading the application server from WLS 8.1.4 to WLS 10.3.2, customer decided to migrate their application from EJB 2.1 to EJB 3.0 standard.
They identified few serious problems, one of them is related with local (@Local) interfaces for stateless session beans. As it was recommended in most migration tutorials, they transformed home interfaces for entity beans to local session beans with injected 'Entity Manager'. This resolution let them to keep all their code untouched, except the base mechanism which was responsible for delivering the old home interfaces.
How can they implement the same if WLS 10.3.2 doesn't support look up of local session beans? One of the resolutions provided is to transform all local interfaces to remote, but it has bad performance influence and seems quite strange when they access local bean through the stub. It also can cause some business errors because of difference between parameter passing (by value or by reference).
So how to obtain the reference to local Session Bean from POJO class when look up for local interfaces is not supported? Injection is not the resolution for two reasons: they need access to local session bean in POJO classes (not session beans) and they can't lift few thousand of classes to use injected beans. On the server side they need one base mechanism that will be able to deliver any local bean.
Upgrade from WLS 8.1 SP4 to WLS 10.3.2.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms