Hi all, I've run into a minor problem with the el-api.jar and deployment. It looks like Tomcat 6 now includes the el-api.jar as part of the deployment. If I have an el-api.jar (which I link against for development) into my web application's WEB-INF/lib directory, or will the clash annoy it? I seem to get "java.lang.LinkageError: loader constraints violated when linking javax/el/ExpressionFactory class" when I try to do this. In there any way to have the two co-exist peacefully? Reason is my deployments also get used for development of sub-products/projects which need the el-api classes and I don't really want to have to do two separate deployments, one with the el-api and one without. Can I build the api and/or ri from the Tomcat source to resolve the problem? Any suggestions appreciated. Cheers. Mike.
This e-mail is bound by the terms and conditions described at http://www.subexazure.com/mail-disclaimer.html
