Hi Jan, Jan Bartel schrieb: > Burkhard, > > First, as someone else mentioned, please post this on the > [EMAIL PROTECTED]
Because of the statement "jetty6 will not hot-deploy webapps after it has started. You must stop and then restart jetty6 to pick up the new webapp. If you are interested in using hot-deployment, take a look at the jetty6 maven2 plugin" on http://docs.codehaus.org/display/JETTY/Running I thought that this place would be the right one - but ok, I'll post this mail on [EMAIL PROTECTED] too... > However, while we're all here .... ;-) > What is going on inside the login jsp? Oh, nothing special. In the meantime I was able to create a very small web application producing the same exception when redeployed. > Looks like some instance of a > class that is loaded by the webapp class loader is being set on > a class that is loaded from the system classpath. This would mean > that the class that is loaded via the system classpath never changes > with a webapp reload, but the class from your webapp > will change with every restart (because the classloader is > different, so you'll get ClassCast exceptions). > > regards > Jan Yes, I think, that's the problem. But I suppose that it only occurs when using jakartas standard tag library 1.1 implementation under jetty6 - so here's my mini-webapp: [EMAIL PROTECTED]:~/tmp/my-webapp$ tree . |-- pom.xml `-- src `-- main |-- java | `-- test | `-- MyBean.java |-- resources `-- webapp |-- WEB-INF | |-- c.tld | `-- web.xml `-- index.jsp I'm not sure if it's possible to use attachments in this mailing list - but I'll give it a try - attached my-webapp.tar.gz... ;-) [EMAIL PROTECTED]:~/tmp/my-webapp$ mvn clean compile jetty6:run works fine - http://localhost:8080/my-webapp/index.jsp produces the output "Hello World! test". After changing and compiling MyBean.java the mini-webapp get's redeployed and (when surfed to) produces the following exception Caused by: javax.el.ELException: java.lang.IllegalArgumentException: object is not an instance of declaring class at javax.el.BeanELResolver.getValue(BeanELResolver.java:68) at javax.el.CompositeELResolver.getValue(CompositeELResolver.java:51) at org.apache.el.parser.AstValue.getValue(AstValue.java:97) at org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:185) at org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:944) at org.apache.jsp.index_jsp._jspx_meth_c_out_0(index_jsp.java:99) at org.apache.jsp.index_jsp._jspService(index_jsp.java:72) By the way: Repeatedly hot deployment of the war file produced by "mvn clean compile war:war" under tomcat (5.5.12) is absolutely trouble-free. But of course - a working jetty6-plugin would be much more comfortable! ;-) Regards Burkhard > Burkhard Graves wrote: >> Hi folks, >> >> I'm using the maven-jetty6-plugin (6.0.0beta14), usual Maven defaults. >> >> "mvn jetty6:run" works fine, but if my webapp is redeployed (due to some >> compiler run) I get the following exception(s): [...] >> Caused by: javax.el.ELException: java.lang.IllegalArgumentException: >> [EMAIL PROTECTED] >> at javax.el.BeanELResolver.getValue(BeanELResolver.java:68) >> at >> javax.el.CompositeELResolver.getValue(CompositeELResolver.java:51) >> at org.apache.el.parser.AstValue.getValue(AstValue.java:97) >> at >> org.apache.el.ValueExpressionImpl.getValue(ValueExpressionImpl.java:185) >> at >> org.apache.jasper.runtime.PageContextImpl.proprietaryEvaluate(PageContextImpl.java:944) >> >> at >> org.apache.jsp.pages.login_jsp._jspx_meth_c_out_0(login_jsp.java:247) >> at org.apache.jsp.pages.login_jsp._jspService(login_jsp.java:117) >> at >> org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:94) [...]
my-webapp.tar.gz
Description: application/gzip
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]