I also have the same issue - the header is not impacted by the
expiration value.
Yossi
On Sep 4, 3:50 pm, Patou patou.de.saint.ste...@gmail.com wrote:
hello,
I test the new sdk, and I see that we now add a expiration attribut in
the include tag in appengine-web.xml to set the expiration
OK, but why would this behavior be happening inconsistently across his
(and probably others) application?
On Sep 5, 7:06 pm, Max Ross maxr+appeng...@google.com wrote:
Key is not in the default fetch group because it is an appengine-specific
class. The JDO spec doesn't know anything about app
Similar problem with SimpleDateFormat here -
http://groups.google.com/group/google-appengine-java/browse_thread/thread/a7ea6dd1e097d496?pli=1
On Aug 20, 10:46 am, James H james.hollier...@gmail.com wrote:
Ah yes, I was looking for that very switch to disable Sessions and it
did help isolate
Hi!
I've the following Entity:
@PersistenceCapable(identityType = IdentityType.APPLICATION)
public class Document implements Serializable {
@PrimaryKey
@Persistent(valueStrategy = IdGeneratorStrategy.IDENTITY)
@Extension(vendorName = datanucleus, key =
Oh mine! It occurred again. JDO looks quite fragile.
Is there any wrong with following code?
@PersistenceCapable(identityType = IdentityType.APPLICATION)
public class Category {
@PrimaryKey
@Persistent(valueStrategy = IdGeneratorStrategy.IDENTITY)
private Long id;
Oh mine! It occurred again. JDO looks quite fragile.
Nothing fragile about the persistence process. You simply have to
define your classes as persistent and enhance them, and have the
enhanced ones in the CLASSPATH. Not hard
--~--~-~--~~~---~--~~
You received
I used the Eclipse Soft Updates menu on Sep 4th to apply SDK 1.2.5
after noticing Red errors in the local runtime log telling me to do
so. Actually, first I noticed my production app was failing to
retrieve data so I figured I needed to first upgrade as instructed by
the log message and then see
I saw white list http://code.google.com/appengine/docs/java/jrewhitelist.html
, java.lang.Thread is in it. Aren't Thread not supported?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
Google App Engine for Java
Task queues are working properly when I deploy my app to Google's
servers, but never get executed in my development environment (Eclipse
Galileo). There are no errors, no logs, no indication of what's going
wrong. Queue.add() returns successfully, but my tasks never get
executed. I'm running the
Hi,
I'm using Eclipse plugin and sdk-1.2.2 to upload my app to GAE, its
size is 109MB. From time to time I'm facing upload problems with the
following error: java.io.IOException: Error posting to URL:
http://appengine.google.com/api/appversion/addblob?path=__.500
Internal Server Error
The
I think it makes sense now. I did see more exceptions related to
incorrect transaction handling (e.g. updating multiple entities from
different entity groups) that didn't happen prior to 1.2.5. It seems
that it was the upgrade to datanucleus 1.1.5 that triggered these
exceptions. I am not
Hi Vince,
In order to get the task queue into the 1.2.5 release we had to take a
shortcut with the local development environment. Tasks execute
automatically in production but not locally. However, in the local
environment you can kick off your tasks manually by visiting the task queue
admin
Based on the Max Ross I/O video on Persistence, I understand the best
practice regarding handling of Master/Detail relations is to place
redundant Master data in the Detail row. Same would apply to any type
of relation (1-to-1, 1-to-many).
So for example if I have an entity Person relating as
Hi,
I have a class Foo defined as below:
public class Foo{
@PrimaryKey
@Persistent(valueStrategy=
IdGeneratorStrategy.IDENTITY)
private
14 matches
Mail list logo
