JavaOne 
Moscone Center, San Francisco, California, U.S 
8-11 May, 2007

Four days packed with opportunities to meet with and learn more from innovators, thought leaders, industry players and creators, to attend sessions, hands-on labs, Camps, Java University, the Business Day, the TV Day... a key event for anyone in the industry.

find out more about JavaOne

Orange Partner at JavaOne

There were several opportunities to hear from and meet with Orange Partner at JavaOne...

... in the JavaOne Pavilion
The Orange Partner team pod was located in the Mobility Village, next to the Java ME Application Showcase.
Hopefully, you had time to come and see us there!

... in the BOF sessions

 How to Work with Java ME Carriers at JavaOne
8 May, 21:00-21:50, Session ID: BOF-5914

Speakers: Martin Wrigley, Head of Partner Technology, Orange Partner joined the panel for this BOF session.

The Java Platform, Micro Edition (Java ME) ecosystem has many different components, with carriers each having different Java ME policies, varying Mobile Information Device Profile (MIDP)/JS implementations on handsets, and different development tools/resources. This session covered the various carriers that support Java ME (Sprint, Cingular, T-Mobile) and gives developers an overview of the Java ME platform and the handset Java ME platform, the Java ME security policy, developer tools/resources support, and the Java ME distribution policy. This was meant to be an interactive BOF session that allowed developers to ask questions and provides feedback directly to people at the carriers that influence the Java ME ecosystem in the U.S.

... in the Java ME Track

 Tackling Java ME Device Fragmentation: Orange and Sun Collaboration
8 May, 18:00-19:00, Esplanade 303, Session ID: TS-5051

Speakers: Martin Wrigley, Head of Partner Technology, Orange Partner joined Nir Vazana and Rhian Sudgen of Sun Microsystems.  

When Java ME was first introduced, it promised WORA (write once, run anywhere). In reality, WORA has been very difficult to achieve, however, resulting in Java ME developers' writing separate or custom software for each device on which they want their application to execute. This device fragmentation costs time and money and can result in the creation of a different JAR file for each device. This is even more of an issue now that code needs to be verified. Together, Sun and Orange have worked to develop a set of guidelines for developers using the Java ME platform that will help reduce the cost and effort of covering a wider range of devices.

This session reviewed the design guidelines and provided developers with practical advice on how an application can be written to achieve the optimal balance of application performance and coverage of numerous devices. Code samples illustrated specific techniques for writing MIDlets that handle different device capabilities.

You may want to take a look at the design guidelines and the work Orange Partner are doing to encourage Java de-fragmentation

 Java Verified - A Description and Update to the Verification and Signing Process for the Java ME Application Developer
9 May, 13:30, Esplanade 301, Session ID: TS-5397

Speakers: Martin Wrigley, Head of Partner Technology, Orange Partner took part in this session.