Ah. Thanks Elliot. The wurfl.xml out is of date. This is easily fixed.
We have a build process that automatically downloads the latest wurfl.xml and builds it into a support library. So when we release every two weeks, the latest is built into the system. The library got changed out from under the build system. The build system is being updated and the problem will likely go away.
In the mean time, why is the Java API raising exceptions on device not found? Exception handling is much more expensive than just returning a null pointer or a Device object populated with an error code.
API Bean:
Code: Select all
<bean id="wurflEngine" class="net.sourceforge.wurfl.core.GeneralWURFLEngine">
<constructor-arg index="0" value="classpath:/com/rhino/deviceUtils/config/wurfl.zip" />
<property name="engineTarget" value="accuracy" />
<!-- Big ol' capabilityFilter cut for ease of reading -->
</bean>
API call:
Code: Select all
WURFLEngine wurflEngine = (WURFLEngine) DeviceUtilsSpringConfig.getApplicationContext().getBean("wurflEngine");
Device wurflDevice = wurflEngine.getDeviceForRequest(userAgent);
Thanks again and best regards,
Tom