Lastly, Mobility Pack 4.1 offers the means to deploy your project MIDlet Suite(s) to a server file system or device directly. Deployment has always been a little painful in J2ME development,for many reasonsproprietary vendor mechanisms, protocols, security, etc. While this new IDE feature will not solve all ills, it does offer the possibility that deploying a J2ME application may soon be more like deploying an enterprise application.
|Figure 11. The Deploying Option IS Selected: Deploying a project's MIDlet suite can now be accomplished from inside the IDE. Four methods of deployment are available. The method displayed here is FTP.|
Access the MIDP Suite Deployment feature by right clicking on the MIDP project and selecting "Properties" from the menu options. On the Properties dialog window, select the "Deploying" Category as shown in Figure 11. The deployment configuration dialog box allows you to pick the deployment method, destination, and required deployment information/settings such as authentication information.
Today, there are four deployment method options available through the Project Properties dialog. J2ME developers can deploy their J2ME MIDP suites using SCP, WebDAV, FTP, or a straight file copy.
As you can see, the new NetBeans IDE and Mobility Pack 4.1 have a lot to offer. The last couple of releases have really improved on the J2ME developer's ability to write, debug, and deploy MIDP apps. Is my laundry list of needs and wants for a J2ME IDE completely satisfied with this latest release of NetBeans and the Mobility Pack? Not yet, but it's are getting closer. The visual editing feature, in particular, has a ways to go. However, even the folks at Sun have indicated they realize this is a first step. But the future looks much brighter. I am almost ready to remove that text editor from my desktop.