The current Google App Engine plugin for NetBeans does not have a UI interface to change the username and password that it has saved. It also does not display its properties in Preferences tab. The only way to change the stored username and password is to modify the deployment.properties file located in .netbeans/6.9/config/Preferences/org/netbeans/modules/j2ee/appengine
You simply need to change the email address and password in this file. Hopefully, the development will continue on this plugin to add this functionality in the future.
Saturday, March 26, 2011
NetBeans Google App Engine Plugin - Changing Deployment Settings
Labels:
App Engine
,
GAE
,
Google
,
Java
,
Netbeans
NetBeans 6.9.1 and Google App Engine
A couple of weeks ago David Chandler from Google gave a talk at the Greenville Java Users Group (GreenJUG) about Google App Engine. I was very impressed with the presentation and demo. I decided to explore a little with NetBeans and a plugin for GAE.
The NetBeans support for Google App Engine Plugin is a quick install and works on NetBeans 6.9.1. Once it is installed create a sample Guestbook application to enable the App Engine features. The complete functionality is not enabled until you use it like a number of other NetBeans plugins.
After you create the project you must modify the appengine-web.xml to point to a registered project on appengine for example guestbook and set the version.
Finally we deploy it by selecting the project and deploying it using the context menu. The first time you deploy an application it will prompt you for your login and password. It retains the values for future deployments.
That was easy! Once you get your first application deployed, you have opened the way for future development.
The NetBeans support for Google App Engine Plugin is a quick install and works on NetBeans 6.9.1. Once it is installed create a sample Guestbook application to enable the App Engine features. The complete functionality is not enabled until you use it like a number of other NetBeans plugins.
After you create the project you must modify the appengine-web.xml to point to a registered project on appengine for example guestbook and set the version.
Finally we deploy it by selecting the project and deploying it using the context menu. The first time you deploy an application it will prompt you for your login and password. It retains the values for future deployments.
That was easy! Once you get your first application deployed, you have opened the way for future development.
Labels:
App Engine
,
GAE
,
Google
,
Java
,
Netbeans
Subscribe to:
Posts
(
Atom
)
Popular Posts
-
Introduction This article is not another diatribe to tell you the importance of unit testing. I think we can all agree that it is important...
-
A friend of mine asked me if there was a list of reserved words in EL and JSF. He had previously looked for it, and after some Google search...
-
I saw a question posed on stackoverflow called Trouble with Primefaces 3.0.M2 SelectOneMenu Ajax behavior and I had just done an example a...
-
I was working on a couple of SSL based issues when I made a couple of observations. The default self-signed key generation in Java does not ...
-
This is an example on how to make a system call to the local operating system to execute external programs. This example was written to work...
-
We have been doing a lot of work lately with PrimeFaces. A common set of questions comes up about displaying <p:dialog/> boxes on a pa...
-
I was asked earlier today how to reset fields in a JSF application, if the validation fails. In his case, he had a Richfaces table which had...
-
Image by quasarkitten via Flickr The basics for creating a Maven archetype can be found in the Maven - Guide to Creating Archetypes . The ...
-
Previously, I posted an example of how to use JSF 1.2 with form based authentication (j_security_check). In this example, I use JSF 2.x to...
-
Abstract A common use case is to iterate over a collection of elements, and display them on a page. In the world of JSP, we would use a Ja...