Re: CDI Plugin example does not work in 2.5.14.1

2018-03-14 Thread fullmitten 
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 issue by using Log4j 2.8.x.  
I added a dependency for log4j-api and log4j-core, version 2.8.2.  The 
application appears to work fine, thought it does generate a spectacular 
error message covered by this WW-4920, which is apparently addressed in 
Struts 2.5.16.



On 2018-01-22 19:38, fullmit...@lycos.com wrote:


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. (27057030).


On 2018-01-22 18:11, fullmit...@lycos.com wrote:

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 CDI 
isn't at issue here.


The word from Oracle is that this problem appears to have been 
introduced into WLS 12.1.3 between the July 2016 and January 2018 
Critical Patch Updates (that is, Struts works with the earlier patch 
and does not work with the latter). I, of course, am running with the 
latest updates.

Thanks.

On 2018-01-21 14:32, Lukasz Lenart wrote:

...

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org


-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

Re: CDI Plugin example does not work in 2.5.14.1

2018-01-22 Thread fullmitten 

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. (27057030).


On 2018-01-22 18:11, fullmit...@lycos.com wrote:

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 CDI isn't at issue 
here.


The word from Oracle is that this problem appears to have been 
introduced into WLS 12.1.3 between the July 2016 and January 2018 
Critical Patch Updates (that is, Struts works with the earlier patch 
and does not work with the latter). I, of course, am running with the 
latest updates.

Thanks.

On 2018-01-21 14:32, Lukasz Lenart wrote:

...

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

Re: CDI Plugin example does not work in 2.5.14.1

2018-01-22 Thread fullmitten 
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 CDI isn't at issue 
here.


The word from Oracle is that this problem appears to have been 
introduced into WLS 12.1.3 between the July 2016 and January 2018 
Critical Patch Updates (that is, Struts works with the earlier patch and 
does not work with the latter). I, of course, am running with the latest 
updates.

Thanks.


On 2018-01-21 14:32, Lukasz Lenart wrote:


Ah, right :) We have moved this dependency directly under the
Convention Plugin, so if you do not use it, there be no ASM jar.

What version of Java do you use to compile the project and what
version is used to run the Weblogic?

Regards
--
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

2018-01-19 20:05 GMT+01:00  : 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 
say,

since it isn't in the Maven dependency chain, it does not appear in my
application.
I tried adding ASM 5.2 to my pom, added some instructions to try to get
Weblogic to prefer the packages in the web application over Weblogic's 
own
(don't know why that isn't the default behavior *shrug*) and got the 
same

failure.
I tried deploying the same application to Tomcat 9 and it worked fine, 
so it
looks like either I'm configuring something wrong in Weblogic or 
Weblogic
has a problem. I've opened a support request with Oracle to see what 
they

think.
Thanks!

On 2018-01-19 03:17, Lukasz Lenart wrote:

It's probably because we have switched to the latest ASM 5.2 version
[1] but looks like Weblogic uses (repackaged one -
"com.bea.objectweb.asm") an old version of ASM. I think you should
request Oracle support for a solution, maybe they have a patch for the
Weblogic or try to downgrade version used in Struts.

[1] https://issues.apache.org/jira/browse/WW-4826

2018-01-18 17:01 GMT+01:00  : 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

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org


-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

Re: CDI Plugin example does not work in 2.5.14.1

2018-01-21 Thread Lukasz Lenart 
Ah, right :) We have moved this dependency directly under the
Convention Plugin, so if you do not use it, there be no ASM jar.

What version of Java do you use to compile the project and what
version is used to run the Weblogic?


Regards
-- 
Łukasz
+ 48 606 323 122 http://www.lenart.org.pl/

2018-01-19 20:05 GMT+01:00  :
> 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 say,
> since it isn't in the Maven dependency chain, it does not appear in my
> application.
> I tried adding ASM 5.2 to my pom, added some instructions to try to get
> Weblogic to prefer the packages in the web application over Weblogic's own
> (don't know why that isn't the default behavior *shrug*) and got the same
> failure.
> I tried deploying the same application to Tomcat 9 and it worked fine, so it
> looks like either I'm configuring something wrong in Weblogic or Weblogic
> has a problem. I've opened a support request with Oracle to see what they
> think.
> Thanks!
>
> On 2018-01-19 03:17, Lukasz Lenart wrote:
>
>> It's probably because we have switched to the latest ASM 5.2 version
>> [1] but looks like Weblogic uses (repackaged one -
>> "com.bea.objectweb.asm") an old version of ASM. I think you should
>> request Oracle support for a solution, maybe they have a patch for the
>> Weblogic or try to downgrade version used in Struts.
>>
>> [1] https://issues.apache.org/jira/browse/WW-4826
>>
>> 2018-01-18 17:01 GMT+01:00  : 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
>>
>
>
> -
> To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
> For additional commands, e-mail: user-h...@struts.apache.org

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

Re: CDI Plugin example does not work in 2.5.14.1

2018-01-19 Thread fullmitten 
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 say, since it isn't in the Maven dependency 
chain, it does not appear in my application.
I tried adding ASM 5.2 to my pom, added some instructions to try to get 
Weblogic to prefer the packages in the web application over Weblogic's 
own (don't know why that isn't the default behavior *shrug*) and got the 
same failure.
I tried deploying the same application to Tomcat 9 and it worked fine, 
so it looks like either I'm configuring something wrong in Weblogic or 
Weblogic has a problem. I've opened a support request with Oracle to see 
what they think.

Thanks!

On 2018-01-19 03:17, Lukasz Lenart wrote:


It's probably because we have switched to the latest ASM 5.2 version
[1] but looks like Weblogic uses (repackaged one -
"com.bea.objectweb.asm") an old version of ASM. I think you should
request Oracle support for a solution, maybe they have a patch for the
Weblogic or try to downgrade version used in Struts.

[1] https://issues.apache.org/jira/browse/WW-4826

2018-01-18 17:01 GMT+01:00  : 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




-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org

Re: CDI Plugin example does not work in 2.5.14.1

2018-01-19 Thread Lukasz Lenart 
It's probably because we have switched to the latest ASM 5.2 version
[1] but looks like Weblogic uses (repackaged one -
"com.bea.objectweb.asm") an old version of ASM. I think you should
request Oracle support for a solution, maybe they have a patch for the
Weblogic or try to downgrade version used in Struts.

[1] https://issues.apache.org/jira/browse/WW-4826


2018-01-18 17:01 GMT+01:00  :
> 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
>>
>> weblogic.application.utils.annotation.ClassInfoImpl.(ClassInfoImpl.java:84)
>
>
>>
>> at
>>
>> weblogic.application.utils.annotation.ClassfinderClassInfos.getClassInfoFromSource(ClassfinderClassInfos.java
>
>
>>
>> :325)
>> Truncated. see log file for complete stacktrace
>
>
> Could you see log file for complete stacktrace and post here? Is it same
> as [1]?
>
> [1] https://issues-test.apache.org/jira/browse/LOG4J2-2124
>
> Hello,
> I apologize if this message does not get threaded correctly.  I subscribed
> to the forum in digest mode, so I did not get the previous message to reply
> to.
> The full stack trace I received is below.  It is similar, but not identical
> to the stack trace in the Jira issue.
> I tried changing the version of Log4J to 2.8.2 as suggested in the link
> above and still received the same stack exception.
> Thanks again for the help.
>
>    
>  <[STANDBY] ExecuteThread: '1' for queue: 'weblogic.kernel.Default
> (self-tuning)'> <> <> <> <1516287695350>   trace for message 149004
> weblogic.application.ModuleException: java.lang.IllegalArgumentException
>  at
> weblogic.application.internal.ExtensibleModuleWrapper.activate(ExtensibleModuleWrapper.java:123)
>  at
> weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:114)
>  at
> weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:195)
>  at
> weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:190)
>  at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
>  at
> weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:61)
>  at
> weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:145)
>  at
> weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
>  at
> weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
>  at
> weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
>  at
> weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48)
>  at
> weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
>  at
> weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
>  at
> weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:587)
>  at
> weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
>  at
> weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
>  at
> weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:339)
>  at
> weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:846)
>  at
> weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1275)
>  at
> weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:442)
>  at
> weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:176)
>  at
> weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
>  at
> weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
>  at
> weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
>  at
> weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:553)
>  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
>  at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
> 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
>

Re: CDI Plugin example does not work in 2.5.14.1

2018-01-18 Thread fullmitten 

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
weblogic.application.utils.annotation.ClassInfoImpl.(ClassInfoImpl.java:84)




at
weblogic.application.utils.annotation.ClassfinderClassInfos.getClassInfoFromSource(ClassfinderClassInfos.java




:325)
Truncated. see log file for complete stacktrace


Could you see log file for complete stacktrace and post here? Is it same
as [1]?

[1] https://issues-test.apache.org/jira/browse/LOG4J2-2124

Hello,
I apologize if this message does not get threaded correctly.  I 
subscribed to the forum in digest mode, so I did not get the previous 
message to reply to.
The full stack trace I received is below.  It is similar, but not 
identical to the stack trace in the Jira issue.
I tried changing the version of Log4J to 2.8.2 as suggested in the link 
above and still received the same stack exception.

Thanks again for the help.

   
  <[STANDBY] ExecuteThread: '1' for queue: 
'weblogic.kernel.Default (self-tuning)'> <> <> <> 
<1516287695350>  
weblogic.application.ModuleException: java.lang.IllegalArgumentException
 at 
weblogic.application.internal.ExtensibleModuleWrapper.activate(ExtensibleModuleWrapper.java:123)
 at 
weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:114)
 at 
weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:195)
 at 
weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:190)
 at 
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
 at 
weblogic.application.internal.flow.ModuleStateDriver.activate(ModuleStateDriver.java:61)
 at 
weblogic.application.internal.flow.DeploymentCallbackFlow.activate(DeploymentCallbackFlow.java:145)
 at 
weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:729)
 at 
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)
 at 
weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)
 at 
weblogic.application.internal.SingleModuleDeployment.activate(SingleModuleDeployment.java:48)
 at 
weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:165)
 at 
weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
 at 
weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:587)
 at 
weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:150)
 at 
weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:116)
 at 
weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:339)
 at 
weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:846)
 at 
weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1275)
 at 
weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:442)
 at 
weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:176)
 at 
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:195)
 at 
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:13)
 at 
weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:68)
 at 
weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:553)

 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:311)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:263)
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 
weblogic.application.utils.annotation.ClassInfoImpl.(ClassInfoImpl.java:84)
 at 
weblogic.application.utils.annotation.ClassfinderClassInfos.getClassInfoFromSource(ClassfinderClassInfos.java:325)
 at 
weblogic.application.utils.annotation.ClassfinderClassInfos.populateClassInfos(ClassfinderClassInfos.java:278)
 at 
weblogic.application.utils.annotation.ClassfinderClassInfos.(ClassfinderClassInfos.java:72)
 at 
weblogic.servlet.internal.War.initializeClassInfosIfNecessary(War.java:446)

 at weblogic.servlet.internal.War.getClassInfos(War.java:451)
 at

Re: CDI Plugin example does not work in 2.5.14.1

2018-01-17 Thread Yasser Zamani 


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 
> weblogic.application.utils.annotation.ClassInfoImpl.(ClassInfoImpl.java:84)
>  
> 
> at 
> weblogic.application.utils.annotation.ClassfinderClassInfos.getClassInfoFromSource(ClassfinderClassInfos.java
>  
> 
> :325)
> Truncated. see log file for complete stacktrace


Could you see log file for complete stacktrace and post here? Is it same 
as [1]?

[1] https://issues-test.apache.org/jira/browse/LOG4J2-2124

--

CDI Plugin example does not work in 2.5.14.1

2018-01-17 Thread fullmitten 

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 deployment request w
ith ID "1051870189008960" for task "10". Error is: 
"weblogic.application.ModuleException: java.lang.IllegalArgumentExcep

tion"
weblogic.application.ModuleException: java.lang.IllegalArgumentException
at 
weblogic.application.internal.ExtensibleModuleWrapper.activate(ExtensibleModuleWrapper.java:123)
at 
weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:114)
at 
weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:195)
at 
weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:190)
at 
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)

Truncated. see log file for complete stacktrace
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 
weblogic.application.utils.annotation.ClassInfoImpl.(ClassInfoImpl.java:84)
at 
weblogic.application.utils.annotation.ClassfinderClassInfos.getClassInfoFromSource(ClassfinderClassInfos.java

:325)
Truncated. see log file for complete stacktrace




task for the application "StrutsCDI".>


application "StrutsCDI".>
trace for message 149004

weblogic.application.ModuleException: java.lang.IllegalArgumentException
at 
weblogic.application.internal.ExtensibleModuleWrapper.activate(ExtensibleModuleWrapper.java:123)
at 
weblogic.application.internal.flow.ModuleListenerInvoker.activate(ModuleListenerInvoker.java:114)
at 
weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:195)
at 
weblogic.application.internal.flow.ModuleStateDriver$2.next(ModuleStateDriver.java:190)
at 
weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)

Truncated. see log file for complete stacktrace
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 
weblogic.application.utils.annotation.ClassInfoImpl.(ClassInfoImpl.java:84)
at 
weblogic.application.utils.annotation.ClassfinderClassInfos.getClassInfoFromSource(ClassfinderClassInfos.java

:325)
Truncated. see log file for complete stacktrace


My Maven pom.xml is as follows (i deploy by copying the WAR file from 
the build directory into the Weblogic domain's autodeploy directory):


http://maven.apache.org/POM/4.0.0; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
  xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
http://maven.apache.org/maven-v4_0_0.xsd;>

  4.0.0
  org.eclevelandclinic
  StrutsCDI
  war
  1.0
  Struts CDI Webapp
  http://maven.apache.org

  

  junit
  junit
  3.8.1
  test


  org.apache.struts
  struts2-core
  ${struts.version}
  

org.apache.struts
struts2-cdi-plugin
${struts.version}


javax.enterprise
cdi-api
1.0-SP1
provided


org.apache.logging.log4j
log4j-core
2.9.1

  


1.8

2.5.14.1


  
StrutsCDI
  



Thanks for looking at my problem.

-
To unsubscribe, e-mail: user-unsubscr...@struts.apache.org
For additional commands, e-mail: user-h...@struts.apache.org