How to Apply WebLogic Patches. Oracle has released a patch for the latest CVE. Version 3.3.0 is the latest version and is included with WebLogic 10.3.5 and later. Dec 24, 2013 Weblogic 10.3.5 to 10.3.6 in-place upgrade Action: Download and apply the upgrade patch Steps 1. Download the upgrade patch from metalink.

OPTION1: Deploy your Spring 3.x app to a wls server in a domain that does not have JRF installed. That works for me. OPTION2: use prefer-web-inf-classes in weblogic.xml and deploy as a war.

This worked for me with wls 10.3.6, JRF domain, Spring 3.2.2. I couldn't get prefer-application-packages to work, but prefer-web-inf-classes did. Flying Lotus 38 Cartoons Zip. NOTES: With a domain that does have JRF installed, I've tried both the war/weblogic.xml/prefer-application-packages and ear/weblogic-application.xml/prefer-application-packages approaches and neither seems effective.

I have a test jsp that outputs org.springframework.core.SpringVersion.getVersion() and it persists in reporting 2.5.6.SEC01 despite my efforts (this is the version of Spring bundled in the oracle_common/modules folder). Deploy the same app in a non-JRF domain though, and org.springframework.core.SpringVersion.getVersion() will report whatever version of spring you bundled with your app. I had the same problem. The solution was to create weblogic-application.xml into the META-INF folder of EAR project. Here is the code.

Org.apache.* org.springframework.* Maybe your problem is that you're using weblogic.xml into WAR project instead of weblogic-application.xml into EAR project. Hope it helps. If you are using Spring Framework, you'll most likely deploy your Spring beans in a WAR and not an EAR, even in case of a Spring Integration project. Up to 12c (incl. 12.2.1) without any specific configuration you'll be stuck at Spring framework 3.0.5 and Spring Integration 2.2.6 at best. Any attempt to use a higher Spring Version will likely yield at deployment: weblogic.application.ModuleException: java.lang.NoSuchMethodError: org.springframework.core.MethodParameter.getNestedParameterType()Ljava/lang/Class; because the Oracle-JRF-embedded Spring Framework is picked by the class loader. In a multi-server Domain, not deploying JRF to a given server instance will not solve the issue but a whole Domain without JRF will do.

The trick instead is to use the prefer-web-inf-classes parameter in a WEB-INF/weblogic.xml deployment descriptor, as follows: true and you can enjoy the benefits of Spring Framework 4.2 in a WebLogic Domain with JRF instrumentation. Do not forget, of course, to include Spring core 4.2 and related dependencies into the WAR file assembly (i.e.