Similar here.
Now only logs WARNING and ERROR.
Logging properties set to INFO and prior to 1.3.8 upgrade INFO logged
fine.
Have configuration procedures been changed or something?
Window 7 32bit
Eclipse 3.5 and 3.6
--
You received this message because you are subscribed to the Google Groups
Hi App Engine team,
the Cursor stores the full state of a prepared query to check if it
matches the query when applied and raise an exception if this is not
the case. Now the usual use case is that during a paging operation the
cursor is transferred between client (e.g HTML page, JSP, ...) and
ser
Hi,
I see different purposes for the 2:
- cron tasks are the tasks I always want to do for sure
- tasks via API are tasks that I schedule programmatically when needed
and triggered by event that I can't predict in advance.
I see personally 2 other purposes for API tasks:
a) when I run a task a
Hie Thanks for the response.
I am confused a bit. If cron job does the scheduling then what Task Queue
does?
Thankx and Regards
Vik
Founder
www.sakshum.com
www.sakshum.blogspot.com
On Mon, Oct 25, 2010 at 8:51 AM, Didier Durand wrote:
> Hi Vik,
>
> Tasks scheduled via cron.xml is the way I wo
Hi Vik,
Tasks scheduled via cron.xml is the way I would go:
http://code.google.com/appengine/docs/java/config/cron.html
I would schedule a task every minute, make a query on the deadline for
donors and then do what has to be done.
didier
On Oct 24, 7:11 pm, Vik wrote:
> Hie Guys
>
> Our applic
Hi,
see http://code.google.com/appengine/docs/domain.html: it is what you
need.
Did it myself and it was fine.
didier
On Oct 25, 5:06 am, pman wrote:
> can i have this.
>
> app1.abc.com --> point to --> app1.appspot.com
>
> app2.abc.com --> point to --> app2.appspot.com
>
> any help or guide?
can i have this.
app1.abc.com --> point to --> app1.appspot.com
app2.abc.com --> point to --> app2.appspot.com
any help or guide?
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group, send email to google-appeng
> I'm just here because i feel i need to rant a little. I came here expecting
> way too much.
Been there with JDO -- the docs are not adequate.
I don't know your exact requirements but I suspect you'll find many on
this list who found objectify to be the "simplest convenient interface
to the Goog
*Sir, Thanks for your guidelines. Thankyou.
*
On Sun, Oct 24, 2010 at 5:14 PM, Vikas Hazrati wrote:
> Hi Matthieu,
>
> You are right, you need some conditioning and then you need to work
> around the limitations of working with relationships around JPA. Then
> finally you tend to realize more and
*Sir, Thanks for your guide lines. Thank you.
*
On Sun, Oct 24, 2010 at 10:41 PM, Vik wrote:
> Hie Guys
>
> Our application manages a list of blood donors. Time to time these blood
> donors are unreachable so the administrators can mark such blood donors as
> inactive.
>
> However, these blood do
*Sir,Thanks for your guide lines. Thankyou.
*
On Mon, Oct 25, 2010 at 1:18 AM, Cyrille Vincey wrote:
> Have you created a descending index on the key of the entity group you try
> to map ?
> (required for mapreduce jobs)
>
> From: suersh babu
> Reply-To:
> Date: Fri, 22 Oct 2010 14:52:17 +0530
Have you created a descending index on the key of the entity group you try
to map ?
(required for mapreduce jobs)
From: suersh babu
Reply-To:
Date: Fri, 22 Oct 2010 14:52:17 +0530
To: ,
Subject: [appengine-java] Mapreduce gives error when I execute job on
appengine cloud?
Hi,
I am using
Hie Guys
Our application manages a list of blood donors. Time to time these blood
donors are unreachable so the administrators can mark such blood donors as
inactive.
However, these blood donors should be active again after 1 day
automatically. How should we achieve this? ?In regular J2EE apis we
Hello,
I upgraded my project from 1.3.4 to 1.3.8. After the upgrade, the
console fails to log. If I switch back to 1.3.4, the console logs
properly.
I am on a 64-bit Windows Vista environment, running Eclipse 3.4.2 w/
(MyEclipse and Instantiations GWT tools)
Thanks
--
You received this message
Hi Matthieu,
You are right, you need some conditioning and then you need to work
around the limitations of working with relationships around JPA. Then
finally you tend to realize more and more that may be you are better
off with unowned relationships
Here are the issues that we faced and tried to
I now have problem with
com.google.appengine.api.datastore.DatastoreNeedIndexException: no
matching index found...
And, the admin Dashboard shown
===
Number of Indexes
100%
100%199 of 200
===
the application is a relatively simple, yet got suc
16 matches
Mail list logo
