Element type "devices" must be declared

[arouel]

Since device categorization is available beginning October 2013 all version lower or equal to version uadetector-core 0.9.9 and uadetector-resources 2013.09 print the following log message:

22:35:02 [update-operation] WARN  n.s.u.internal.data.XmlDataHandler - Error while reading UAS data: Element type "devices" must be declared. (line: 20917)
22:35:02 [update-operation] WARN  n.s.u.datareader.XmlDataReader - Element type "devices" must be declared.
Exception in thread "update-operation" net.sf.qualitycheck.exception.IllegalStateOfArgumentException: The passed arguments have caused an invalid state: Argument 'data' must not be empty.
    at net.sf.uadetector.datastore.AbstractRefreshableDataStore.checkData(AbstractRefreshableDataStore.java:61)
    at net.sf.uadetector.datastore.AbstractRefreshableDataStore.setData(AbstractRefreshableDataStore.java:229)
    at net.sf.uadetector.datastore.UpdateOperationTask.call(UpdateOperationTask.java:36)
    at net.sf.uadetector.datastore.AbstractUpdateOperation$1.run(AbstractUpdateOperation.java:197)
    at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
    at java.lang.Thread.run(Thread.java:695)

It means that UADetector cannot get the most recent version from http://user-agent-string.info, because the XML schema changed (and unsupported by this library). In this case the library falls back to the cached file or the delivered database within uadetector-resources.

Stay cool, the library continues to work normally but without updates.

Since October 2013 an update of UADetector support device categorization. Please update to uadetector-resources version 2013.10 or uadetector-core version 0.9.10.

[wormyourhonor]

Just to confirm (clarification on the the last line from issue description), is the new uas.xml schema expected to be supported and this issue "fixed" in the October 2013 update?

[arouel]

@wormyourhonor Exactly, we support the new format with the current state of our code base and end of this month we release it officially in the Central Repository. I close the ticket when the release is done. In a few days you can update uadetector-resources to version 2013.10 to get rid of these logging message.