2010/4/8 Christian Stone <[email protected]>: > You should be able to reproduce by using the Struts showcase example, and > remove Javaassist.jar from your classpath. > > The problem is that javaassist is not marked as a runtime dependency AND is a > new requirement AND does not generate an error to inform the user what is > actually an issue. There is no missing class error, or any error that is of > use to diagnose that in fact you need to include javaassist.jar. I believe > you will see a lot of traffic with deployment issues because people will not > be aware of the new dependency, and their application will fail to deploy > with the new builds without any proper error reporting for the fatal error.
It's a bit strange, I'm using maven to build war and with Javassist marked as provided in OGNL I still got it in that war!?! Can someone explain to me why is it happen that way? I also made a test on WebLobic 10, manually removed javassist from war and started the server - everything went smoothly :P Does WL has javassist ??? I will try other way, but I'm still not able to reproduce that problem :-( Best regards -- Łukasz http://www.lenart.org.pl/ Kapituła Javarsovia 2010 http://javarsovia.pl --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
