By terrencebarr on Jun 13, 2013
The Oracle Java ME Embedded 3.3 and Java ME SDK 3.3 EA bits have been refreshed. Please see Terrence Barr's blog for full details.
The Oracle Java ME Embedded 3.3 and Java ME SDK 3.3 EA bits have been refreshed. Please see Terrence Barr's blog for full details.
Note that the Java ME SDK 3.3 is still in Early Access, so you may experience minor issues which are being resolved for the final release.
It has been a while since we released the last version. We have been very busy integrating new features and making lots of usability improvements into this new version.
Some of the new features in this version are described below.
|Embedded Application Support
Oracle Java ME SDK 3.2 now supports the new Oracle® Java ME Embedded. This includes support for JSR 228, the Information Module Profile-Next Generation API (IMP-NG). You can test and debug applications either on the built-in device emulators or on your device.
The Memory Monitor shows memory use as an application runs. It displays a dynamic detailed listing of the memory usage per object in table form, and a graphical representation of the memory use over time.
|Eclipse IDE support
Oracle Java ME SDK 3.2 now officially supports Eclipse IDE. Once you install the Java ME SDK plugins on Eclipse, you can start developing, debugging, and profiling your mobile or embedded application.
With the Custom Device Skin Creator, you can create your own skins. The appearance of the custom skins is generic, but the functionality can be tailored to your own specifications.
Here are the release highlights.
Implementation and support for the new Oracle® Java Wireless Client 3.2 runtime and the Oracle® Java ME Embedded runtime.
The AMS in the CLDC emulators has a new look and new functionality (Install Application, Manage Certificate Authorities and Output Console).
Support for JSR 228, the Information Module Profile-Next Generation API (IMP-NG).
The IMP-NG platform is implemented as a subset of CLDC. Support includes:
A new emulator for headless devices.
Javadocs for the following Oracle APIs: Device Access API, Logging API, AMS API, and AccessPoint API.
New demos for IMP-NG features can be run on the emulator or on a real device running the Oracle® Java ME Embedded runtime.
New Custom Device Skin Creator.
This tool provides a way to create and manage custom emulator skins. The skin appearance is generic, but the functionality, such as the JSRs supported or the device properties, are up to you. This utility only supported in NetBeans.
Eclipse plugin for CLDC/MIDP.
For the first time Oracle Java ME SDK is available as an Eclipse plugin.
The Eclipse version does not support CDC, the Memory Monitor, and the Custom Device Skin Creator in this release.
All Java ME tools are implemented as NetBeans plugins.
As of the plugin integrates Java ME utilities into the standard NetBeans menus.
Tools > Java ME menu is the place to launch Java ME utilities, including the new Skin Creator.
Profile > Java ME is the place to work with the Network Monitor and the Memory Monitor.
Use the standard NetBeans tools for debugging.
Profiling, Network monitoring, and Memory monitoring are integrated with the NetBeans profiling tools.
New network monitoring protocols are supported in this release: WMA, SIP, Bluetooth and OBEX, SATSA APDU and JCRMI, and server sockets.
Java ME SDK Update Center. Oracle Java ME SDK can be updated or extended by new components. The Update Center can download, install, and uninstall plugins specific to the Java ME SDK. A plugin consists of runtime components and skins.
Bug fixes and enhancements.
This version comes with a few known problems. All of them have workarounds, so I hope you don't get stuck in these issues when you are using the product.
It you cannot watch static variables during an Eclipse debugging session, and sometimes the Variable view cannot show data.
In the source code, move the mouse over the required variable to inspect the variable value.
A real device shown in the Device Selector is deleted from the Device Manager, yet it still appears.
Kill the device manager in the system tray, and relaunch it. Then you will see the device removed from the list.
On-device profiling does not work on a device.
CPU profiling, networking monitoring, and memory monitoring do not work on the device, since the device runtime does not yet support it. Please do the profiling with your emulator first, and then test your application on the device.
In the Device Selector, using Clean Database on real external device causes a null pointer exception.
External devices do not have a database recognized by the SDK, so you can disregard this exception message.
Suspending the Emulator during a Memory Monitor session hangs the emulator.
Do not use the Suspend option (F5) while the Memory Monitor is running. If the emulator is hung, open the Windows task manager and stop the emulator process (javaw).
To switch to another application while the Memory Monitor is running, choose Application > AMS Home (F4), and select a different application.
Please let us know how we can improve it even better, by sending us your feedback.
-Java ME SDK Team
Through usage data analysis, we see that users are all around the world. We would love to support all the languages you are using, but due to the resource constraint, we are supporting two languages other than English - Simplified Chinese and Japanese.
The new release comes with a new feature - update center on NetBeans, where you can download latest plug-ins. You can download Java ME SDK from Oracle Technology Network.
Through update center, you can download latest plug-ins for Java ME SDK.
||Chinese and Japanese Localization
We offer extensive localization for Chinese and Japanese. They are all in one package.
NetBeans vs. Eclipse. Which IDE are you using when you develop a Java ME application?
You know that Java ME SDK has been officially supporting only Eclipse platform. We wondered how many Java ME developers were using NetBeans versus Eclipse. So we did a quick poll. Here is the result.
120 people participated. 52% use NetBeans, while 34.5% use Eclipse as primary IDE. "Other" included IntelliJ. 34.5% is a significant number, so we are considering to add support for Eclipse in the future.
Do you agree with the result? What do you think?
Merry Christmas to everyone and especially to all Mac users. There's still few days remaining to Christmas but we are giving presents already. Thanks to great effort of software and quality engineering during last weeks we have managed to wrap up our Mac release before end of this year and make it public today. You can download Java ME SDK 3.0 for Mac OS and try out Java ME cldc/midp mobile development on Mac OS for the first time.
Java ME SDK 3.0 for Mac OS contains these key features:
On device deployment and debugging support
Integrated Lightweight UI Toolkit
CPU profiling support
New development environment based on Netbeans 6.7 platform
JDK 1.5 and JDK 1.6 support
Device search database
Java FX Mobile emulator
Merry Christmas and happy New Year
SiliconIndia, India’s professional networking portal, is organizing Mobile Application Conference India in Bangalore on this Saturday. Sun is a technology partner of the conference and it is an opportunity for you to see Sun's mobile technologies in action. I was told that there will be also a demonstration of Java ME SDK 3.0. Sun India team is looking forward to meeting you there if you have a chance to come.
Mac developers have often asked when Java ME SDK 3.0 will be available for their operating system. We always answered that we were working on it. Today is the day when it happened, we have released Java ME SDK 3.0 Early Access for Mac OS X. You can download it from http://java.sun.com/javame/downloads/sdk30.jsp.
Highlights of Java ME SDK 3.0 Early Access, Mac OS X:
Last week was very interesting for us. We spent two days in usability lab observing how people use Java ME SDK 3.0 and we collected a lot of useful information from this usability study.
We could see four usability study participants every day. Some of them were professional developers, some of them students with different level of Java ME knowledge. It was a really edifying experience to observe people with varied Java ME skills using a product which they haven't had seen before. Each participant got one and half hour to finish three tasks. The tasks were designed to cover general product functionality as well as specialized features, e.g. sensor emulation. Java ME SDK engineering team did a lot of notes and we are also looking forward to results from the user experience team who organized the study for us. We should get the results next week but we have already started to think how to improve the product usability.
Do you want to know how the usability lab looks like? It consists of two rooms, darkened and well-lid, separated by two-way mirror. It allows people in the darkened room to see into the lighted room but not vice versa. I'm sure you know this kind of room from criminal movies. In our case the rooms are equipped better than on police stations and usability study participants feel there more pleasantly than suspects in police interrogation room. We are also much more friendly than police officers :-)
The participant sits alone in the lighted room and working on usability study tasks. Participants are asked to think aloud to allow observers in the next room to follow their mind. User experience team is recording participant's voice, face and desktop to be able to analyze their work-flow later.
We'd like to thank to all participants for attending Java ME SDK usability study and to user experience team for organizing this study. It was very inspiring for us. Thank you!
Following pictures show participant and observers rooms.
This is what really didn't happen during the usability study ... at least not during our study :-))
Today I'm not going to write anything serious and even anything related to the mobile development. As every working day I came to the office, started to read emails and found one with a link to A Tribute to Sun Microsystems web page. It moved me back in time. Before I joined Java ME SDK team I was a member of NetBeans engineering team, working on different parts of NetBeans IDE. I spent eight years working on this great product and from this time are also pictures which want to show you. Trip to one cold February day eight years ago starts here :-)
Looking out from the window it seems that autumn weather came to Prague. Winter will be here in a few months and hopefully there will be good conditions for another snowball batlle, this time between Java ME SDK and JavaFX teams :-)
PS: I'm throwing the snowballs from the farther terrace.
That's a question we have got a lot of times. It was answered here and in different forums, describing why it take some time to release Mac version so I'm not going to write the reasons again. Today I'm going to show you something behind the scene. We are running Scrum process while developing Java ME SDK. Next two pictures were taken at the end of our latest sprint.
The first pictures shows our office board with table of stories and their tasks. As you can see we finished all tasks.
The second picture is more interesting. It shows burndown chart, which is a is graphical representation of work left to do versus time. The green line represents the ideal burndown. You can see that our progress was under the ideal line. It means that we worked faster and finished our tasks sooner than we expected when planning the sprint. Especially in the beginning the progress was quite rapid so in the middle of the sprint we added a few extra stories and we achieved all of them.
That's what is happening in our team and hopefully answers the title question. Java ME SDK for Mac is in progress and it goes well ... stay tuned – coming soon to a computer near you!
Three weeks ago has been released NetBeans 6.7. This release integrates Java ME SDK 3.0 so mobile developers can now use all advantages of NetBeans Mobility and Java ME SDK 3.0 together for their development.
For more information visit NetBeans 6.7 release information page.
I'm back from Java Mobile, Media & Embedded Developer Days - Latin America (M3DDLA) and I'm still full of impressions from this conference.
M3DDLA was hosted by Senac University, Faculdade de Tecnologia in Goiânia, Brazil and organized by GoJava, Java community of Goiás (state of Brazil). Java has a very big and very active community in Brazil and I could see it at the conference. A lot of people interested in mobile Java technologies registered and came to M3DDLA. Each session had a big audience and there were a lot of questions at the end of each presentation. It was very nice to see Brazilian passion for Java. I can't help myself I have to say that it was the best conference which I've ever been to!
The success of M3DDLA would not be possible without a great organization. I want to say here once more 'thank you' to Murilo, Raphael, Roger, Terrence, Mauricio, Flavia, Filipe, Marcos, Leonardo and all other who I don't know by their name and who worked hard to prepare this excellent conference. Also thanks to everyone who came to visit it because without your audience M3DDLA would have never succeed!
My special thanks go to Jose Luiz Uzeda de Oliveira, manager of Address West Side Hotel Residence where all conference speakers stayed. He and his team did the best for us to feel there as at home and we really enjoyed it.
Four days in Goiânia wasn't just a conference. It was also learning about Brazil. Now I know much more about Brazil than I knew one week ago. Great part of this learning was tasting Brazilian food and drinks. I still remember the taste of tucunaré, feijoada, brunch, cupuaçu, Guaraná Antarctica, caipirinha :-), etc. I can't also forget the trip to Pirenópolis which our new friends organized for us. It was a really nice day ended by swimming under waterfall. It was my first time in Brazil and I hope not last time because this visit still comes back to my mind. Thank you Murilo, Heloisa, small cute Lara, Raphael, Alice, Filipe, Marcos, Leonardo, Igor for spending your free time with us and making our Brazilian experience!
Java ME Platform SDK is a toolbox for developing mobile applications. Java ME SDK Download