Bugs and Updates List

The updates in the next release are posted here. If you encounter a problem and wish to send in a bug report or email, it will help to fix that problem.

Next Release Features and Fixes

Other Info

• The core licas package uses Java 1.8 and the GUI also uses JavaFX.
• If looking for a Service's values, check its 'sm' module first. The 'service' variable is typically the parent service.
• If looking at the FrequencyGrid, the same count is not shared, but the first category is currently selected.
• If writing your own service and adding it to the main GUI, you probably need to extend the DynamicJFrame instead of a JFrame, plus implement ServiceGuiDef. Then in 'initialiseAndOpen', you need to add 'setID(theServiceUuid)' to give the dynamic frame the service uuid name.
• If adding XML text to a List as a String, then if it gets lost during transmission, try adding it as an XML Element instead.
• Running scientific services with threading is computationally expensive, so start with a small number.
• For the mobile platform, you need to set some values at the start of your main activity, to allow the base licas classes to set file paths or other values. Even if you don't use it, make sure you set the LoggerFactory in your startup method, before using any of the licas classes. You also need to specify the Android operating system, so that linux file paths can be set. You therefore need to add the following two lines of code at the start of your main activity:
  LoggerFactory.setLoggerFactory(new CustomLoggerFactory());
  System.setProperty(“type.os”, Const.ANDROID);
• For the mobile platform, it is best to have a single jar file for the base classloader. So wrap licas jar with your own mobile jar file.
• See the Knowledge Base for an example of using the REST interface for mobile communication.
• To view a remote server in the default GUI, you need both the server password and admin key for the remote server, to access all information, but can access a lot with just the password.
• There might be a bug in the Java Reflection package, if overloaded methods have the same parameter number but slightly different parameter types. One fix is to give them different method names.
• The packet size only works from a blocking client to server request, so it is returned to the client as part of the call.