Sure, Essentially my code is targetting the is_wireless_device property via the device.getCapability("is_wireless_device") method. Below is a snippet example: WURFLHolder wurflHolder = (WURFLHolder)filterConfig.getServletContext().getAttribute("net.sourceforge.wurfl.core.WURFLHolder"); WURFLManager ...

I can also include the LG Quantum, Samsung Omnia 7, and a few yet-to-be-named Android devices by my client to this list

PS, I'm on the latest wurfl file and java implementation.

Thanks,

-j

Currently there is no is-mobile-device type attribute set for this hardware. Is there a different attribute that one should target when using the WURFL strictly for mobile device detection? My current approach was "if mobile device = true, redirect to mobile url", but it seems that more and more dev...

Right now the default setting for our website configuration is to listen to all site requests in order to pull any tracking querystring values (TrackingFilter) listed below. Our mobile listener also listens to all incoming requests currently, and for reasons unknown this is causing server errors on ...

Turns out my issue was that DeviceServlet was never checked into source control. Once we got it back, I'm able to program against tablet devices.... D'OH!

Sorry for the delay, I've had some progress and then a dead end. I've been able to isolate the Tomcat "welcome-file-list" is conflicting with the redirect in some way. When I remove the default file orders everything works, but when I put it back in the redirect never seems to occur. Seems like Tomc...

TrackingFilter.java is an existing code class set for some site features unrelated to our WURFL. I went ahead and verified it's not doing anything with the mobile filter, it only deals with our persistent cookie and querystring reads for tracking site users and search engines. Yup, it's a fine Unive...

I'm using the JAVA API with the following settings in my web.xml file. Let me know if I can provide more, and thanks for the help: <web-app> <display-name>www.XXXXXXXXXXX.edu</display-name> <context-param> <param-name>wurfl</param-name> <param-value>/WEB-INF/wurfl-latest.zip</param-value> </context-...

I get that, but the default configuration of the Java solution we have implemented is making that decision for me right now. I'd like to know where the setting(s) is/are that will allow me to specify the action to take for Tablets

I've found in testing that tablet devices (iPad, iPad2, Samsung Galaxy 10") are going to the mobile version of our sites rather than the standard site versions. Is there a central location that allows you to define what version to serve up to a tablet device? I've grabbed the latest wurfl xml and pa...