[jboss-as7-dev] Exploded Oddity with that Spring/Hibernate Example

[Jim Tyrrell]

Team,

See the attached screen shot:

I have an exploded war file (spring/hibernate) that I made changes to based on Marius (THANK YOU!!!!!!!!!) feedback.  The application deploys, but does not run when executed with the following  errors:
10:08:12,829 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[localhost].[/BRMSPoc].[brmsDispatcher]] (http--127.0.0.1-8080-1) Servlet.service() for servlet brmsDispatcher threw exception: java.lang.IllegalAccessException: Class org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer can not access a member of class org.jboss.stdio.StdioContext$DelegatingPrintStream with modifiers "public"
	at sun.reflect.Reflection.ensureMemberAccess(Reflection.java:65) [:1.6.0_24]
	at java.lang.reflect.Method.invoke(Method.java:588) [:1.6.0_24]
	at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:957) [mvel2-2.0.16.jar:]
	at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:314) [mvel2-2.0.16.jar:]
	at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:137) [mvel2-2.0.16.jar:]
	at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:137) [mvel2-2.0.16.jar:]
	at org.mvel2.MVELRuntime.execute(MVELRuntime.java:85) [mvel2-2.0.16.jar:]
	at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:104) [mvel2-2.0.16.jar:]
	at org.mvel2.MVEL.executeExpression(MVEL.java:1001) [mvel2-2.0.16.jar:]
	at org.drools.base.mvel.MVELConsequence.evaluate(MVELConsequence.java:103) [drools-core-5.1.1.jar:]
	at org.drools.common.DefaultAgenda.fireActivation(DefaultAgenda.java:917) [drools-core-5.1.1.jar:]
	at org.drools.common.DefaultAgenda.fireNextItem(DefaultAgenda.java:856) [drools-core-5.1.1.jar:]
	at org.drools.common.DefaultAgenda.fireAllRules(DefaultAgenda.java:1071) [drools-core-5.1.1.jar:]

Is the .failed from the screen shot on all the exploded jars in the war from when I had not made all of Marius changes?  
Is it expected behavior on an exploded war?
How would I clean these up?  Do I need to?
What effect/affect are these having on my current deployment?  Now that I mostly think I have my application in a state where I can run/deploy my application?

Does it make sense to mark all of these "embedded/included" jar files as failed?

I am not sure if this is expected behavior, bugs or what?  Some advice pretty please?




I guess you have to love lazy loading, and runtime exceptions. :S!!!!!

Jim Tyrrell
Senior JBoss Solutions Architect

Did you see RHT on Fox News around Cloud?
http://video.foxbusiness.com/v/1039347607001/red-hat-ceo-on-the-growth-of-cloud-computing/




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20110708/955bbd70/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen shot 2011-07-08 at 10.33.33 AM.png
Type: image/png
Size: 38010 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/jboss-as7-dev/attachments/20110708/955bbd70/attachment-0001.png