Community
Participate
Working Groups
The differences between WebLogic 10.0 and WebLogic 10.3 (and more specifically WebLogic 10.3.3.1 - after Aug 2008) are becoming large enough to recommend subclassing the existing WebLogic_10 platform into WebLogic_10_3. Differences: -------------- The start of a list... Changes to the 10.3 classloader infrastructure between April 2008 and Aug 2008 Addition of new ExecuteThreadRuntime API that is used in bug# 248746 that is not in 10.0. If it is decided that we require support for 10.0 as well as 10.3 then this design changes should go ahead, otherwise if we are just supporting 10.3 as the 10.x platform then disregard this change request.
Implementation: --------------- 1) Take everything that is currently in WebLogic_10_Platform that was introduced as part of bug# 248748 in the new [MBeanWebLogicRuntimeServices] and specifically bug# 248746 where we added 2 more reflective calls getModuleName() and getApplicationName() available only on 10.3.3.1 - and move this to the 10_3 platform. 2) verify and keep all MBean registration/deregistration that currently exists in the 10 platform but use the generic MBean implementation [MBeanRuntimeServices] - see lines 114-126 of attachement https://bugs.eclipse.org/bugs/attachment.cgi?id=116658&action=diff 3) Add a new WebLogic_10_3_Platform to config.TargetServer 3) Communicate the new 10_3 platform via ELUG, newsgroup and tutorial wiki.
We will also need to update the WorkBench design time code to add a weblogic-10-3-platform to the dropdown for sessions.xml creation. see related weblogic-10-platform request http://bugs.eclipse.org/241261
Moving past 1.1
In a design review with product management it was decided that WebLogic_10 is good as-is.
This enhancement is not required at this point
Moving bugs previously targeted for 1.1.X that are resolved to 1.1.3
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink
