1

I got several build errors on my very new Codename One application:

The build complains on the FileNotfoundException class and the String split() method. Any idea why ?

xxx\Page.java:11: error: cannot find symbol
import java.io.FileNotFoundException;
  symbol:   class FileNotFoundException
  location: package java.io

and 

xxx\Page.java:97: error: cannot find symbol
            final String[] parts = number_label.split("-");
  symbol:   method split(String)
  location: variable number_label of type String

By the way, is that true that there is a restriction to use java 1.5 in CodenameOne ? I couldn't find where to say to compile with java 7.

Kind regards,

Shai Almog
  • 51,749
  • 5
  • 35
  • 65
lvr123
  • 524
  • 6
  • 24

1 Answers1

1

EDIT: This reply is somewhat out of date. Codename One supports a subset of Java 8 now although string.split() is still a problematic API call.

Codename One supports a subset of Java 5, you shouldn't try and change that since the server translation code relies on bytecode behaviors of the target Java 5 and only supports a very specific subset of the API.

The reasoning is simple, since Codename One has multiple VM implementations (iOS, Dalvik/ART, XMLVM/ParparVM, blackberry etc.) its really hard to test new stuff (e.g. newer bytecodes) and its really hard to add new API's in a way that will be totally cross platform. You can use StringUtils.split() to implement this functionality as well as StringTokenizer.

Limiting the API's also allows us to keep the executable efficient and small (relatively). Compared to a more full featured VM we are at least 5 times smaller in production. This is a big deal for mobile apps...

We are working on consolidating the various VM's on the server side which will allow us to add core VM API's more easily in the future as well as features like Java 8 support.

You can learn more in this answer: How does Codename One work?

Community
  • 1
  • 1
Shai Almog
  • 51,749
  • 5
  • 35
  • 65
  • For the most of the world, who's used to working with Java 7 most likely, this is quite a downer. When do you expect support for more recent versions of Java will be available? – ygesher Apr 30 '15 at 00:33
  • Java 7 isn't much of an improvement, we might support Java 8 (lambdas) in the future but don't have a concrete schedule. If you are referring to the full API I doubt that will ever happen... The full API is just too big and since we need to package the whole thing you will quickly hit the 100mb hard limit for OTA downloads in itunes. – Shai Almog Apr 30 '15 at 05:24
  • Updated the answer with newer details as Java 8 is supported now. – Shai Almog Feb 07 '16 at 05:06
  • The javadocs for the ShareButton class uses a try-with-resources. I couldn't get it to build, because it told me that it's not supported in -source 1.5. I tried setting the codename1.languageLevel property to 7, but that didn't work. Is there a way to use this? Or is the ShareButton sample code simply incorrect? – MiguelMunoz Apr 12 '16 at 18:34
  • We switched to Java 8 support a while back and since 3.3 have set it to the default. See the edit to this question. – Shai Almog Apr 13 '16 at 02:52