Google AppEngine: how to add your domain

In this blog post I will explain how you can add your own domain to a Google AppEngine Application. I will start from scratch just to show you how it works. 1. First of all, make sure you are signed in into Google AppEngine. Navigate to the Dashboard and create a new Application: 2. Create a new application by clicking on “Create Application”. On the next dialog, you need to specify some data about the application. This is the application identifier, a description and how the application will be accessed. We’ll select the “open for all” option, as we want our application to be generally available. Once this step is completed, you will see the “application created” page. 3. Next, we will navigate to the overview again and select our newly created application. Navigate down until you reach the section “Administration”. Select “Application Settings”. 4. In the “Application Settings” Dialog for Google AppEngine, scroll down until you reach the section

read more Google AppEngine: how to add your domain

Problem with Google AppEngine and Jersey with Java

I recently came across a significant problem with Google AppEngine 1.7.2 and Jersey. Whenever I tried to implement my Webservice, I got a 500 error. There was nothing really wrong with the code. So i took a look at the Logs in the Google AppEngine Dashboard and found the following exception:   // //   Uncaught exception from servlet java.lang.IncompatibleClassChangeError: Implementing class at at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass( at at at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke( at java.lang.reflect.Method.invoke( at java.lang.ClassLoader.loadClass( at com.sun.jersey.api.core.ScanningResourceConfig.init( at com.sun.jersey.api.core.PackagesResourceConfig.init( at com.sun.jersey.api.core.PackagesResourceConfig.<init>( at com.sun.jersey.api.core.PackagesResourceConfig.<init>( at com.sun.jersey.spi.container.servlet.WebComponent.createResourceConfig( at com.sun.jersey.spi.container.servlet.WebComponent.createResourceConfig( at com.sun.jersey.spi.container.servlet.WebComponent.init( at com.sun.jersey.spi.container.servlet.ServletContainer.init( at com.sun.jersey.spi.container.servlet.ServletContainer.init( at javax.servlet.GenericServlet.init( at org.mortbay.jetty.servlet.ServletHolder.initServlet( at org.mortbay.jetty.servlet.ServletHolder.doStart( at org.mortbay.component.AbstractLifeCycle.start( at org.mortbay.jetty.servlet.ServletHandler.initialize( at org.mortbay.jetty.servlet.Context.startContext( at org.mortbay.jetty.webapp.WebAppContext.startContext( at org.mortbay.jetty.handler.ContextHandler.doStart( at org.mortbay.jetty.webapp.WebAppContext.doStart( at org.mortbay.component.AbstractLifeCycle.start( at$TraceContextRunnable.runInContext( at$TraceContextRunnable$ at at$AbstractTraceContextCallback.runInInheritedContextNoUnref( at$AbstractTraceContextCallback.runInInheritedContext( at$ at This exception is caused by compatibility issues between asm-4.0.jar and asm-3.1.jar. With the new Version of AppEngine, asm-4.0.jar is used and it is not compatible with

read more Problem with Google AppEngine and Jersey with Java

Get the latest news on Cloud Computing and Big Data

[widgets_on_pages id=”sb”] [widgets_on_pages id=3] The most popular Posts: IDC: Big Data Market growing by 40% annually, reaching 16.9B $ by 2015 Problem with Google AppEngine and Jersey with Java Design Guidelines for Cloud Computing and Distributed Systems NoSQL as the Trend for databases in the Cloud? Creating a distributed, scalable WordPress Platform on Amazon Web Services (AWS)