Am 07.05.2015 um 14:38 schrieb Joakim Erdfelt: > Yow ... web-app_2_3.dtd > > That was part of J2EE 1.3, back in Sept 2001 > <http://en.wikipedia.org/wiki/Java_EE_version_history#J2EE_1.3_.28September_24.2C_2001.29>.
I know. That was the status when the first version of our app was published ;-) > Ok, this old of a web dtd isn't tested by our own tests it seems. > But we do have that dtd in our jetty-schemas.jar > <https://github.com/eclipse/jetty.toolchain/blob/master/jetty-schemas/src/main/resources/javax/servlet/resources/web-app_2_3.dtd> > Which the jetty-webapp.jar and its > org.eclipse.jetty.webapp.WebDescriptor.class knows about > <https://github.com/eclipse/jetty.project/blob/jetty-9.2.10.v20150310/jetty-webapp/src/main/java/org/eclipse/jetty/webapp/WebDescriptor.java#L93> > and sets up for internal redirect > <https://github.com/eclipse/jetty.project/blob/jetty-9.2.10.v20150310/jetty-webapp/src/main/java/org/eclipse/jetty/webapp/WebDescriptor.java#L145-L147>. I've seen that part in the source of WebDescriptor-class before asking the question since I haven't seen a way to add my own redirections (and I already have these files residing in my installation - just in another directory than javax/servlet/) > So I gotta ask, how are you using jetty? Embedded into an application to provide HTTP-functionalities using the jetty-all.jar and additional jars for servlets and JSP. First version was AFAIR version 4. > If embedded, or maven plugin, or just about anything that isn't the > jetty-distribution, then what are the dependencies you use? We're not using Maven so we replace the old jars residing in lib/jetty by new ones. After that we start our testcases and check, what's failing. Since all major version changes came with completely new APIs, we end up with compile-errors most of the time anyway, so it's expected to be a manual process and there is no real advantage to use Maven for that. > Or ... can you upgrade the WEB-INF/web.xml to say servlet spec 2.5 > at least? (this error will go away) I can do that for the set of config-files that we include with new installations but I try to avoid to be forced to change them with existing ones since they might have been changed by their corresponding users and I don't want to create a "know-it-all"- parser that is able to change these files in all circumstances. I already had this kind of "fun" with the changed syntax of the jetty-configuration-files between Jetty 7 and Jetty 9.0 and - now again - between 9.0 and 9.2 The Jar solved my immediate problem but I still would like to know how I can add my own redirections as part of Jetty being embedded that is something more standard than try{ WebDescriptor wd = new WebDescriptor(Resource.newResource("")){ @Override public void ensureParser() throws ClassNotFoundException { super.ensureParser(); _parserSingleton.redirectEntity("mywebdtd1.dtd",dtd1); _parserSingleton.redirectEntity("mywebdtd2.dtd",dtd1); _parserSingleton.redirectEntity("mywebdtd3.dtd",dtd1); _parserSingleton.redirectEntity("mywebdtd4.dtd",dtd1); _parserSingleton.redirectEntity("mywebdtd5.dtd",dtd1); } }; wd.ensureParser(); } catch(Exception e){ e.printStackTrace(); } ... which doesn't work in all circumstances. Cheers, Lothar _______________________________________________ jetty-users mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/jetty-users
