Most of us have no choice but to rely on our Palm or Pocket PC handheld devices, mobile phones, and laptops and desktop PCs to stay in touch with the rest of the world. If we could keep all of our contacts, appointments, tasks, and documents in progress isolated to one device, relying on multiple devices wouldn’t be a problem. But today’s business consumer usually juggles two or more devices, each of which must hold up-to-date phone numbers, addresses, schedules, and more.
There are many good reasons why phones capable of locally executable applications aren\'t in everyone\'s pocket today. For the purposes of this briefing, we are focusing on two key reasons. First, the industry needs a \"standard\" protocol for downloading executable applications (not messages) to mobile phones. To be acceptable to network operators, such a protocol must include a method for securing premium revenues and a method to certify the quality of applications in order to protect the network operator from liability.
Learn the basics about the ebXML Registry standard Summary This article is
the first of a series of short articles that will introduce readers to the
industry's various Web services standards. These articles will provide a
quick introduction to a standard, its background, underlying architecture,
benefits, status, and industry adoption. As some of the content might be a
depiction of the author's viewpoint, readers are encouraged to refer to the
links provided in Resources to gain a...
This JSR aims to define a new version of the Java Community Process to address some of the day-to-day issues of Spec Leads and Expert Groups through relatively minor, easy to implement changes to the process. None of the changes require modification to the participation agreements (the JSPA or IEPA). This JSR will not consider any issues that are difficult to implement or that require changes to the JSPA.
This report from Developnet provides an in-depth review of market-leading IDEs that provide facilities for J2ME development using MIDP/CLDC. Instead of providing a comprehensive review of all features each IDE offers, the report focuses on features specifically intended for the J2ME developer. After introducing J2ME and IDE concepts, the report has extensive product-specific sections detailing the J2ME facilities provided by each IDE. ...
J2ME has the promise of being the platform of choice for developing new killer wireless applications, may they be games, productivity tools or stay-in-touch applications. J2ME is the platform of choice for device manufacturers, wireless operators, content aggregators, applications and game developers. J2ME provides something for everyone or at least it promises something for everyone.
December 2002 Issue Until recently, developing J2ME applications meant putting Java on a cell phone or a pager using the mobile information device profile (MIDP). Personal Profile, a new Java 2 Platform, Micro Edition (J2ME) profile, however, opens up J2ME to a broad spectrum of devices and markets including Pocket PCs and communicator-class devices such as the Nokia 9290, as well as Internet appliances such as screen phones and TV set top boxes. Although Personal Profile has its origins in PersonalJava, its feet are firmly planted in the J2ME architecture.
At the heart of Java 2 Micro Edition (J2ME) are three core concepts: configurations, profiles, and optional packages. You can\'t write a J2ME application without understanding these concepts, because they determine the features of Java that you can use, which application programming interfaces (APIs) are available, and how your applications are packaged.
The Java 2 Platform, Micro Edition (J2ME) is aimed at the market for consumer and embedded electronic devices: cellular telephones, two-way pagers, Personal Digital Assistants (PDAs), set-top boxes, and other small devices. Since J2ME\'s release, hundreds of companies have joined the development effort, including large corporations such as Motorola, Nokia, Ericsson, Palm, Samsung, WindRiver, Sharp, Siemens, Sympian, and RIM. This vote of confidence is not surprising; J2ME provides a complete set of solutions for creating state-of-the-art networked applications for small devices.
This JSR will provide a solution to allow J2ME application developers to gain revenue at a finer grained basis controlled directly from within J2ME applications, i.e. pay per level, and pay per feature etc. rather than pay per application or pay per download. This JSR differs from JSR–182 (Payment API for the Java platform) in the following way: while JSR 229 will define an API between a mobile application and a payment facility, JSR-182 concentrates on handling of payment interactions with web-based services.
