This is great -- thanks!!

Hi again, I see 1.4 is released, which is great! I am in the process of upgrading now. Does the tutorial you referred to exist yet, or if not, can you paraphrase the steps here? Anyway, according to your detailed question, you don't need such a feature, but you are asking for a shared wurfl <INSTANC...

> This is something which has to do with Java and Tomcat, and does not depend on Wurfl version. > Obviously, anyway, the tutorial will be focused on Wurfl 1.4, and ready to be deployed with such > version, but if you need it you can customize it to work with previous versions of Wurfl. I understand ...

Hi Fulvio, Thanks again for the quick and detailed response. Looking forward to 1.4! > For the time being, anyway, you can take a look at this document, which explains how to > implement a shared wurfl instance, according to your specific visibility and security requirements. Is this something that ...

Hi Fulvio, Thanks for your quick response! However, this is not working for me, partially because the resource gets loaded via ServletContextWURFLHolder as follows: 93: private URI toURI(ServletContext servletContext, String mainPath) { 94: URI uri = null; 95: try { 96: uri = servletContext.getResou...

Hi, I am currently using WURFL via the Java API configured through WEB-INF/web.xml. The app server stack consists of apache 2.2.9, tomcat 5.5, and java 1.5. I have a number of contexts that each use WURFL, and while the code library dependencies are shared, the WURFL device file and patch files are ...