Okay, I have found my answer. You have to persiste the object first
before you could get its generated primary field value. Cheers!
On Jan 28, 4:07 pm, ivanceras wrote:
> When you instanciate a persisten object in google app engine the
> object automatically is assigned with a value
When you instanciate a persisten object in google app engine the
object automatically is assigned with a value to its primary field
even before persisting it in the database.
sample class:
MyClass{
@PrimaryKey @Persistent(valueStrategy=IdGeneratorStrategy.IDENTITY)
private Long id;
}
But in the c
, ivanceras wrote:
> Hello Miguel,
>
> Thanks for the link. Just a quick question here if you have tried it.
> That this mean if I exclude the validation, my code will now be able
> to use the blacklisted classes?
>
> Thanks,
> ivanceras
>
> On Jan 22, 3:51 am, Migue
Hello Miguel,
Thanks for the link. Just a quick question here if you have tried it.
That this mean if I exclude the validation, my code will now be able
to use the blacklisted classes?
Thanks,
ivanceras
On Jan 22, 3:51 am, Miguel Méndez wrote:
> See if the following link
> help
Is there a way to circumbent google app engine sdk to allow the usage
of classes that are not present in the GAE JRE white list? I know the
app that I would be building would not run in appspot, but at least in
my development server, I need to access a postgresql database
(java.net.socket.*) and ge
