HappyCoding | A Java Utility Library for Happy Coding Projects | Application Framework library

maybe try this?

Based on guillaume blaquiere's suggestion in their comment, I tried following this guide for manually running Datastore locally.

I ran gcloud beta emulators datastore start in one command line, which seemed to run fine, and then I ran $(gcloud beta emulators datastore env-init) in another command line, and I got this error:

I figured out the problem.

The browser was only displaying the 503 error, but the terminal from which I had started the server was actually displaying more error information. The error was that the current version of jdk I was using was not compatible with jetty. I couldn't figure out how to change the java version in bluej, so instead I just downloaded se 8 and compiled through the command line. This fixed the problem.

I think your problem is that you are including the Main class in the war itself, and App Engine is unable to find it.

As you can see in the GCP migration guide, the Main class is defined in an external dependency named simple-jetty-main.

With the execution of the maven-dependency-plugin this dependency is copied to the appengine-staging directory, making it accessible from the Java classpath.

This is the reason why the Main class can be found in the example proposed in the guide when executing the command from the app.yaml entrypoint:

You need HTML to display the image. PHP only does the processing. Try rendering the image on HTML

To replicate the given XML, you want to call setGravity(Gravity.CENTER) on the LinearLayout, rather than fiddling with the individual child Views' LayoutParams.

For a LinearLayout, gravities on its children's LayoutParams that are in the same direction as the LinearLayout's orientation are ignored, as LinearLayout just wants to plainly stack its children in the given direction. That is, for your vertically oriented LinearLayout, the vertical centering inherent to Gravity.CENTER has no effect, so only the horizontal centering is applied, when those lines are un-commented.

However, the gravity set on the LinearLayout itself is a different story. Though the children's individual gravities are ignored, the LinearLayout will still apply its own internal gravity to the children when they're laid out. That's why setting the gravity directly on the LinearLayout has the desired effect.

Also, you can also omit the LayoutParams that you're setting on the LinearLayout. It will fill the content space by default, and the gravity you're setting there isn't effecting anything, as it's telling the LinearLayout's parent how to lay out the LinearLayout itself, not anything to do with its children.