This may be a question for the Web Start or the Jetty forum, but maybe some of you have experience with something like this or you may just find it interesting.
In the past, I have successfully taken an embedded Jetty application containing raw servlets and delivered it via Web Start by zipping the context files, sticking that in a signed jar and exploding it to disk on the client machine. All the Jetty and dependency jars are referenced via Web Start's cache and classpath. It works great. Now I have added an AppFuse Light war with an embedded H2 database. It works great from the command line. but when I run it under Web Start, it can't seem to find any of its own config files. It finds the war and unpacks it, but it then throws errors such as: org.springframework.beans.factory.BeanDefinitionStoreException: Could not resolve bean definition resource pattern [/WEB-INF/applicationContext*.xml]; nested exception is java.io.FileNotFoundException: ServletContext resource [/WEB-INF/] cannot be resolved to URL because it does not exist I'm wondering if it is some kind of relative path vs. Web Start temp folder issue. Maybe if I knew how to force all parts to use the same absolute paths it would work. Anyway, if I get it working I will write up the details of how to do this self contained, Web Start delivered AppFuse. It could be a good model for anyone needing to deliver a local web app to branch offices or customer locations. -Bron -- View this message in context: http://www.nabble.com/Embedded-Jetty-under-Java-Web-Start-tf4318480s2369.html#a12296732 Sent from the AppFuse - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
