Oracle has responded to my service request. It appears that changes to
Log4j to support Java 9 break Weblogic's classloader. There is a new
bug for this issue: Bug 27098427 : JAVA.LANG.ILLEGALARGUMENTEXCEPTION
DEPLOYING APP ON WLS 12.1.3 WITH PSU
For now, it is possible to work around this i
Oracle support has created a bug for this issue:
BUG 27424564 - STRUTS 2.5.14.1 APP BROKEN AT SOME POINT AFTER PSU
12.1.3.0.160719
I tried downgrading the Weblogic PSU and that appears to work. One can
also downgrade the Struts version. Struts 2.5.12 works for me with the
latest Weblogic PSU.
I am using Java 1.8.0_131-b11 on Windows 7, 64-bit for both building the
app and running Weblogic.
I did some more experimenting. I tried removing CDI from my source code
and the Maven pom. I still get the error with a complete stripped down
application (the only dependency being Struts), so
Interesting. I looked at the dependencies included with the
struts2-core Maven artifact and it appears that ASM 5.2 is not there. Is
this on purpose? I see ASM is included in the lib file of the
downloadable distribution and in the WEB-INF/lib directory of the sample
applications. Needless to
On 1/18/2018 12:26 AM, fullmit...@lycos.com wrote:
Caused By: java.lang.IllegalArgumentException
at com.bea.objectweb.asm.ClassReader.(Unknown Source)
at com.bea.objectweb.asm.ClassReader.(Unknown Source)
at
weblogic.application.utils.annotation.ClassInfoImpl.(ClassInfoImpl.java:92)
at
weblog
Hello!
I am attempting to deploy the CDI Plugin example found here:
http://struts.apache.org/plugins/cdi/
on Weblogic 12.1.3. When I use Struts 2.5.12, the application deploys
fine. When I deploy using Struts 2.5.14.1, I receive the following
error:
occurred in the execution of deploym
6 matches
Mail list logo
