Re: App Engine supports Java
Re: App Engine supports Java
- Subject: Re: App Engine supports Java
- From: Pascal Robert <email@hidden>
- Date: Wed, 8 Apr 2009 17:10:06 -0400
Look like it's really for basic apps :
"A Java application cannot create a new java.lang.ThreadGroup nor a
new java.lang.Thread. These restrictions also apply to JRE classes
that make use of threads. For example, an application cannot create a
new java.util.concurrent.ThreadPoolExecutor, or a java.util.Timer. An
application canperform operations against the current thread, such as
Thread.currentThread().dumpStack()."
"A Java application cannot use any classes used to write to the
filesystem, such as java.io.FileWriter. An application can read its
own files from the filesystem using classes such as
java.io.FileReader. An application can also access its own files as
"resources", such as with Class.getResource()
orServletContext.getResource()."
"Only files that are considered "resource files" are accessible to the
application via the filesystem. By default, all files in the WAR are
"resource files." You can exclude files from this set using the
appengine-web.xml file."
Dunno... basically BigTable is the same as Amazons SimpleDB: a loose
property store with no relations in it. You can model them with some
tricks, though. But it still doesn't make that good of a match with
EOF.
I'd rather wonder how they run their "servlets"? Can they keep
state? How?
Cheers, Anjo
Am 08.04.2009 um 19:30 schrieb David Holt:
I found this little snippet from way back in 03:
Damon Clinkscales's "Object Persistence Approaches" presentation
further compared JDO and EJB with WebObjects's Enterprise Objects
Framework (EOF). EOF is a third-party object persistence framework
library owned by Apple and provides the technology behind the Apple
e-commerce Website. Since EOF is a pure Java library, it does not
require complex containers (EJB) or byte code post-processors
(JDO). EOF provides access to the generated raw SQL, and adaptors
can provide access to nonrelational datastores. However, EOF is a
nonstandard vendor-specific technology. It requires the developer
to learn the proprietary API and creates vendor lock-in.
http://www.javaworld.com/javaworld/jw-03-2003/jw-0314-nfjs.html?
page=3
So it sounds like a specific adaptor will have to be created for
the Google Datastore?
On 8-Apr-09, at 9:50 AM, Guido Neitzer wrote:
On 8. Apr. 2009, at 07:34 , Anjo Krank wrote:
http://googleappengine.blogspot.com/
WO in the cloud, anyone?
Hmmm. I guess that could be really interesting if there were an
EOF integration for JDO. Will have to look into that. It's
definitely an interesting option.
cug
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
@krank.net
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
-------------------------------------------------------
Pascal Robert
http://www.macti.ca
http://www.aircourriel.com
http://www.linkedin.com/in/macti
Skype: MacTICanada
AIM/iChat : MacTICanada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden