ScientiaMobile

Hi all,
Im using WURFL in a Java web application and Im using the standard web.xml entry to allow Wurfl initialize itself using "net.sourceforge.wurfl.core.web.WURFLServletContextListener".
If for some reason the files specified (wurfl.zip and wurfl_patch.xml) in the web.xml dont exist on server startup, WURLF seems to get itself into a state.
When the app starts processing requests, I call
WURFLManager manager = wurfl.getWURFLManager();
for each request.
The first time this is called and exception is throw which is expected and I handle this. However, the second and future calls just seem to hang and wait.
There doesnt seem to be any way to see that Wurfl has not been initialized properly.
This will call all future thread to hang and bring down the server - is there something I am missing here?

Thanks,
Barry.

Hi barcon,

we've verified that this issue is actually causing the subsequent blocking threads you were observing.
We will apply a patch as soon as possible and proceed to ship a fixed version of WURFL.

Best Regards,
Andrea Galasso

Thanks Andrea,
any idea on a timeline for the next release?

thanks,
Barry.

Hi Barry,

We have contacted you at the email address you've registered with on this forum.

Thanks,

Hi Barry,

Our email sent to you has bounced. Can you PM me your email address please?

Thanks,