Modify AppScale tools / AppController to allow for Java GAE apps

[GoogleCodeExporter]

Currently the appscale-tools and AppController assume a python app is being
uploaded. Need to make changes to both to allow for Java apps to be
uploaded. Some parts to change include:

- in python, we check the app.yaml file for the app's name. if that file
doesn't exist, need to check the web.xml file (and if it's found, we know
its java)

- need to start up the app using different command line flags in java than
python

Original issue reported on code.google.com by shattere...@gmail.com on 13 Oct 2009 at 6:26

[GoogleCodeExporter]

First steps are done. Have done the following:

- added a "language" tag to the app's internal data, which was added in 
soap_server
and prime_*.py

- changed appcontroller to start up the app as usual if language == python, and 
to
print a message if java (need to coordinate with yiming what the actual command 
will be)

- changed appscale-tools to first assume the app is a python app and rip the 
app.yaml
from it, and if that fails, assume its a java app and rip the appscale-web.xml 
from
it. tested and working with the guestbook-java app, saved in bazaar as
sample_apps/javabook.tar.gz

Should be done once we have integrated in Yiming's modified version of Java-GAE 
and
made the necessary changes to the appcontroller. Will do so after tomorrow's 
meeting.

Original comment by shattere...@gmail.com on 14 Oct 2009 at 3:40

[GoogleCodeExporter]

Preliminary integration is done. Can now run apps that don't require 
authentication,
although app startup and access is notably slower than python apps. Will 
investigate
why this is.

Yiming is currently working on authentication, should be done relatively soon.

Original comment by shattere...@gmail.com on 3 Nov 2009 at 7:32

[GoogleCodeExporter]

Integrated code from Yiming, authentication appears to be functional now. Two
problems remain:

1) Performance from Java AppServer needs to be greatly improved before release.
Starting Java GAE takes far too long, and (more importantly) performing normal
operations with the javabook test app takes far too long.

2) Database access does not work properly when deployed over multiple nodes. 
Appears
to be accessing a locally cached version of the data instead of actually 
populating
data from the database.

Will meet with Yiming on Wednesday to integrate fixed Java GAE.

Original comment by shattere...@gmail.com on 17 Nov 2009 at 4:45

[GoogleCodeExporter]

Fixed. There are still some quirks in authentication and multinode deployments, 
but
will address these after the release as individual issues. 

Java source has been added in AppServer_Java/src.

Original comment by shattere...@gmail.com on 19 Nov 2009 at 7:00

• Changed state: Fixed

[GoogleCodeExporter]

Reopened. Need to fix how we deal with cookies to address recent security 
problems.

Original comment by shattere...@gmail.com on 23 Nov 2009 at 7:20

• Changed state: Started
• Added labels: Priority-Critical
• Removed labels: Priority-High

[GoogleCodeExporter]

Fixed, will be in next release.

Original comment by shattere...@gmail.com on 30 Nov 2009 at 7:47

• Changed state: Fixed