What do you need to use JMS for - connecting to a third-party application,
outside of GAE?
If not, have you looked at the Task Queue API?
Cheers,
Simon
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this discussion on
hi Kesava Neeli,
I too got the same error wat u did to work that fine.
Regards,
Suresh
On Dec 7, 11:21 am, Kesava Neeli wrote:
> Worked fine at 10:00 PM PST
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To post to this group,
hi,
Can u share the same piece fo codes for the same.
Regards,
Suresh
On Dec 15, 4:07 am, Arvind wrote:
> In a Google App Engine for Java web app, I am trying to use the low
> level api to invoke an XML RPC ...After looking at the docs, I figured
> out the following code to connect using low le
Hi all,
What i'm looking for is a queue service that i can run locally on
google app engine might be using JMS queue for the same. Any inputs
and suggestions are welcome and i am trying to do for the past couple
of days but still cant able to fine the solution yet.
Regards,
Suresh
--
You re
Hi Simon,
Yes, This is my first attempt to deploy the application using google
application engine. And i am getting the same error in my browser too.
More over i just need one more clarification..
I am trying to use Javax.naming jar in the google application but it
seems it not supporting that p
Phil,
I believe you should also be able to develop against the local SDK. It just
won't work when deployed.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com | twitter.com/ikai
On Thu, Dec 15, 2011 at 3:49 PM, Amy Unruh wrote:
> Phil,
>
> It's still in the Trusted T
If you are using auto generated keys or keys generated using the
allocateIds() method, no, this should never happen. In fact, any key
created using allocateId will never appear again even if you never save an
entity with that key.
One thing to note is that that IDs are not monotonically incrementi
Phil,
It's still in the Trusted Tester phase. You can sign up here if you are
interested:
https://docs.google.com/a/google.com/spreadsheet/viewform?formkey=dEdWcnRJUXZ2VGR3YmVsT1Q1WVB2Smc6MQ&ndplr=1
The trial is being run in multiple stages, and the invitation pool will be
expanded in later stage
It seems as if documentation for the Full Text Search API has appeared
online as well as being included in the 1.6 java api. Is this supported in
appengine now?
URL of the api:
http://code.google.com/appengine/docs/java/javadoc/com/google/appengine/api/search/IndexManager.html
--
You receive
Okay. If there's anything I can do to make things better for you in this
case please let me know.
--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com | twitter.com/ikai
On Wed, Dec 14, 2011 at 7:08 PM, Kyle Baley wrote:
> Alas, bad timing, I suppose. We pulled the trig
Please fix this before you release the 1.6.1 version:
http://code.google.com/p/googleappengine/issues/detail?id=6290
It's trivial and it's been more than a month...
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this disc
Hi, I have been looking info about this and I haven't find an exact answer
(or I haven't known read the answer).
I am imagining a paranoic scenario where I delete an entity of certain kind
and at some point in the future I create another entity of the same kind
which receives the same key value
On Thu, Dec 15, 2011 at 9:44 AM, Paul wrote:
> I didn't even mention that startup requests, which take about
> 7000-9000ms. So yeah, subsequent requests are like 10x faster, but
> still few times too slow.
>
> On Dec 14, 10:37 pm, "Ikai Lan (Google)" wrote:
>> Could this be startup time? A loadin
Ah it would have helped if I'd read your original post - I believe (and I
haven't bothered with DataNucleus for a long time) that you need to add
that annotation for every property you wish to be unindexed.
Cheers,
Simon
--
You received this message because you are subscribed to the Google Gro
Yes, that's completely possible.
What persistence framework are you using, or are you using the low level
API? They all have different ways of turning off individual property
indexes. It should also be noted that once you change configuration, you
actually have to load and re-persist all of y
1 hour video? Nice :)
I have rather big entity, with over 100 properties, I will query maybe
on 5 of them, so I was wondering if I can turn off indexing for all of
them and just on for those 5.
On Dec 14, 10:39 pm, "Ikai Lan (Google)" wrote:
> Every property creates 2 indexes, so if you don't
I didn't even mention that startup requests, which take about
7000-9000ms. So yeah, subsequent requests are like 10x faster, but
still few times too slow.
On Dec 14, 10:37 pm, "Ikai Lan (Google)" wrote:
> Could this be startup time? A loading request? This is when we have to
> start up the JVM an
17 matches
Mail list logo
