[appengine-java] Problem starting development after adding backends.xml
After adding a backends.xml file to my application I'm no longer able to startup my development environment. Has anybody seen this before? Removing the file clears everything up, but I really need to get a backend running :-) [ERROR] Unable to start App Engine server java.lang.ClassCastException: com.google.appengine.tools.appstats.Recorder cannot be cast to com.google.appengine.tools.development.ApiProxyLocal Unable to start embedded HTTP server com.google.gwt.core.ext.UnableToCompleteException: (see previous log entries) at com.google.appengine.tools.development.gwt.AppEngineLauncher.start(AppEngineLauncher.java: 102) at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509) at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068) at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811) at com.google.gwt.dev.DevMode.main(DevMode.java:311) at com.google.appengine.tools.development.AbstractContainerService.startup(AbstractContainerService.java: 235) at com.google.appengine.tools.development.BackendServers $ServerWrapper.startup(BackendServers.java:816) at com.google.appengine.tools.development.BackendServers.startupAll(BackendServers.java: 304) at com.google.appengine.tools.development.DevAppServerImpl.start(DevAppServerImpl.java: 155) at com.google.appengine.tools.development.gwt.AppEngineLauncher.start(AppEngineLauncher.java: 97) at com.google.gwt.dev.DevMode.doStartUpServer(DevMode.java:509) at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1068) at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:811) at com.google.gwt.dev.DevMode.main(DevMode.java:311) [ERROR] shell failed in doStartupServer method I don't see anything wrong with my backends.xml --> B2 1 true true true Thanks for any help! Rick Mangi -- 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-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] JMS Queue service in Google App Engine
Read this documentation about Task Queues and the Pull Queues: http://code.google.com/appengine/docs/java/taskqueue/overview.html I think this is the functionality you are looking for. It's not JMS, though. -- Ikai Lan Developer Programs Engineer, Google App Engine plus.ikailan.com | twitter.com/ikai On Thu, Dec 15, 2011 at 8:57 PM, suresh ashok wrote: > 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 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-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > -- 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-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] LocalDatastoreServiceTestConfig does not keep modificatins
This is to be expected. You're tearing down the helper between test runs.
All tests are green because you are not using assertions. Example:
assertNotNull(someInstance);
There's something very bad happening in these tests: you don't ever want
state to leak across tests. This is a very bad practice. You want each test
to exist in its own universe. When state leaks across tests, you become
dependent on the order of the tests being run (not guaranteed). You also
can't parallelize tests (this is important to some people). Your tests also
become incredible brittle because if a single test fails in the middle of
the chain, you have a ton of tests that will fail after it that you might
never be able to fix because they were all dependent on a state change in
the failing test - you want that test and only that test to fail.
Here's how you should write the test instead:
@Test public void testFetch() {
final EntityController ec = new EntityController(); // There's
no point caching this. Again, don't want to leak state.
final Flight flight = new Flight("origin", "destination"); // There
also isn't really a point in making any of these final, but that's a minor
nitpick
ec.create(flight);
Flight returnedFlight = ec.find(Flight.class, 1);
assertNotNull("Should be able to find a Flight that was just
created", returnedFlight);
}
--
Ikai Lan
Developer Programs Engineer, Google App Engine
plus.ikailan.com | twitter.com/ikai
On Fri, Dec 16, 2011 at 6:11 AM, Alexander Orlov
wrote:
> All tests are green but *retrive()* resp. *zFind()* are *empty* resp *
> null.*
>
> public class InitDatastore extends Common {
> private final LocalServiceTestHelper helper =
> new LocalServiceTestHelper(new
> LocalDatastoreServiceTestConfig());
> final EntityController ec = new EntityController();
>
> @Before
> public void setUp() {
> helper.setUp();
> }
>
> @After
> public void tearDown() {
> helper.tearDown();
> }
>
> @Test
> public void create() {
> final Flight flight = new Flight("origin", "destination");
> ec.create(flight);
> }
>
> @Test
> public void retrieve() {
> System.err.println("isEmpty = " +
> ec.retrieve(Flight.class).isEmpty());
> }
>
> @Test
> public void zFind() {
> System.out.println("flight###1 = " + ec.find(Flight.class, 1));
> }
> }
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine for Java" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/google-appengine-java/-/78mOAWSJ86EJ.
> To post to this group, send email to
> google-appengine-java@googlegroups.com.
> To unsubscribe from this group, send email to
> google-appengine-java+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/google-appengine-java?hl=en.
>
--
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-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] Datastore indexes
you have to run through the code path locally (not just compile) to get auto generated indexes. then use vacuum index to delete old indexes once you are certain you have defined all your indexes in datastore-indexes.xml On Dec 16, 2011, at 8:03 AM, Gaël wrote: > > Running Eclipse, I don't see all indexes in the datastore-indexes.xml > file (I see only one..), and I also don't have any datastore-indexes- > auto xml file. > > But all my queries are running fine on the app engine, and when I take > a look at my "Data Store Indexes" page in the admin console, I see all > indexes corresponding to the queries I'm running. Fine, fair enough. > But now, why are "old" indexes still serving ? As far as I understood, > after changing or deleting a particular request, the corresponding > index should be delete. Or am I wrong ? > > How can I trigger the app engine to delete the old indexes that I'm > not using anymore ? > > Thanks. > > -- > 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-appengine-java@googlegroups.com. > To unsubscribe from this group, send email to > google-appengine-java+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > -- 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-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Datastore indexes
Running Eclipse, I don't see all indexes in the datastore-indexes.xml file (I see only one..), and I also don't have any datastore-indexes- auto xml file. But all my queries are running fine on the app engine, and when I take a look at my "Data Store Indexes" page in the admin console, I see all indexes corresponding to the queries I'm running. Fine, fair enough. But now, why are "old" indexes still serving ? As far as I understood, after changing or deleting a particular request, the corresponding index should be delete. Or am I wrong ? How can I trigger the app engine to delete the old indexes that I'm not using anymore ? Thanks. -- 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-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: LocalDatastoreServiceTestConfig does not keep modificatins
Btw, I'm using JPA. -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/K-ZC_U4epWgJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] LocalDatastoreServiceTestConfig does not keep modificatins
All tests are green but *retrive()* resp. *zFind()* are *empty* resp *null.*
public class InitDatastore extends Common {
private final LocalServiceTestHelper helper =
new LocalServiceTestHelper(new
LocalDatastoreServiceTestConfig());
final EntityController ec = new EntityController();
@Before
public void setUp() {
helper.setUp();
}
@After
public void tearDown() {
helper.tearDown();
}
@Test
public void create() {
final Flight flight = new Flight("origin", "destination");
ec.create(flight);
}
@Test
public void retrieve() {
System.err.println("isEmpty = " +
ec.retrieve(Flight.class).isEmpty());
}
@Test
public void zFind() {
System.out.println("flight###1 = " + ec.find(Flight.class, 1));
}
}
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/78mOAWSJ86EJ.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: SDK 1.6.1, JPA and JUnit Tests
Ok, got it :)
Add
private final LocalServiceTestHelper helper =
new LocalServiceTestHelper(new *LocalDatastoreService*
TestConfig());
and
${SDK_ROOT}/lib/impl/appengine-api-*.jar to your claspath.
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/VvmXeXAh-8MJ.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: SDK 1.6.1, JPA and JUnit Tests
Maybe posting the whole JUnit file will help:
public class InitDatastore extends Common {
private final LocalServiceTestHelper helper =
new LocalServiceTestHelper(new LocalTaskQueueTestConfig());
@Before
public void setUp() {
helper.setUp();
}
@After
public void tearDown() {
helper.tearDown();
}
@Test
public void doTest() {
final Flight flight = new Flight("origin", "destination");
final EntityController ec = new EntityController();
ec.create(flight);
}
}
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/W6acAoaShHUJ.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] SDK 1.6.1, JPA and JUnit Tests
I'm trying to
@Test
public void doTest() {
final Flight flight = new Flight("origin", "destination");
final EntityController ec = new EntityController();
ec.create(flight);
}
whereby Flight is a JPA annotated entity but I get this when executing this
test:
Dec 16, 2011 12:09:21 PM org.datanucleus.plugin.NonManagedPluginRegistry
resolveConstraints
INFO: Bundle "org.datanucleus" has an optional dependency to
"org.eclipse.equinox.registry" but it cannot be resolved
Dec 16, 2011 12:09:21 PM org.datanucleus.plugin.NonManagedPluginRegistry
resolveConstraints
INFO: Bundle "org.datanucleus" has an optional dependency to
"org.eclipse.core.runtime" but it cannot be resolved
Dec 16, 2011 12:09:22 PM org.datanucleus.plugin.NonManagedPluginRegistry
resolveConstraints
INFO: Bundle "org.datanucleus" has an optional dependency to
"org.eclipse.equinox.registry" but it cannot be resolved
Dec 16, 2011 12:09:22 PM org.datanucleus.plugin.NonManagedPluginRegistry
resolveConstraints
INFO: Bundle "org.datanucleus" has an optional dependency to
"org.eclipse.core.runtime" but it cannot be resolved
Dec 16, 2011 12:09:22 PM org.datanucleus.PersistenceConfiguration
setProperty
INFO: Property datanucleus.rdbms.sql.allowAllSQLStatements unknown - will
be ignored
Dec 16, 2011 12:09:22 PM org.datanucleus.PersistenceConfiguration
setProperty
INFO: Property datanucleus.rdbms.query.containsUsesExistsAlways unknown -
will be ignored
Dec 16, 2011 12:09:22 PM org.datanucleus.PersistenceConfiguration
setProperty
INFO: Property datanucleus.rdbms.stringDefaultLength unknown - will be
ignored
Dec 16, 2011 12:09:22 PM org.datanucleus.ObjectManagerFactoryImpl
logConfiguration
INFO: = Persistence Configuration ===
Dec 16, 2011 12:09:22 PM org.datanucleus.ObjectManagerFactoryImpl
logConfiguration
INFO: DataNucleus Persistence Factory - Vendor: "DataNucleus" Version:
"1.1.5"
Dec 16, 2011 12:09:22 PM org.datanucleus.ObjectManagerFactoryImpl
logConfiguration
INFO: DataNucleus Persistence Factory initialised for datastore
URL="appengine" driver="" userName=""
Dec 16, 2011 12:09:22 PM org.datanucleus.ObjectManagerFactoryImpl
logConfiguration
INFO: ===
Dec 16, 2011 12:09:22 PM org.datanucleus.PersistenceConfiguration
setProperty
INFO: Property datanucleus.appengine.autoCreateDatastoreTxns unknown - will
be ignored
Dec 16, 2011 12:09:22 PM org.datanucleus.PersistenceConfiguration
setProperty
INFO: Property datanucleus.query.cached unknown - will be ignored
Dec 16, 2011 12:09:22 PM org.datanucleus.jpa.metadata.JPAAnnotationReader
processClassAnnotations
INFO: Class "com.google.appengine.demos.helloorm.Flight" has been specified
with JPA annotations so using those.
*com.google.apphosting.api.ApiProxy$CallNotFoundException: The API package
'datastore_v3' or call 'BeginTransaction()' was not found.*
at
com.google.appengine.tools.development.ApiProxyLocalImpl$AsyncApiCall.callInternal(ApiProxyLocalImpl.java:475)
at
com.google.appengine.tools.development.ApiProxyLocalImpl$AsyncApiCall.call(ApiProxyLocalImpl.java:452)
at
com.google.appengine.tools.development.ApiProxyLocalImpl$AsyncApiCall.call(ApiProxyLocalImpl.java:430)
at
java.util.concurrent.Executors$PrivilegedCallable$1.run(Executors.java:463)
at java.security.AccessController.doPrivileged(Native Method)
at
java.util.concurrent.Executors$PrivilegedCallable.call(Executors.java:460)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:680)`
--
You received this message because you are subscribed to the Google Groups
"Google App Engine for Java" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-appengine-java/-/lD2qtD4goMAJ.
To post to this group, send email to google-appengine-java@googlegroups.com.
To unsubscribe from this group, send email to
google-appengine-java+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-appengine-java?hl=en.
Re: [appengine-java] May datastore reuse a deleted entity key?
Many thanks, that is the answer I was looking for :) -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine-java/-/VTFHIW9xBbwJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Basic Question Regarding Deploying the apps with Google Engine
Simon, Thanks for the valuable feedback on my queries. Regards, suresh On Dec 16, 2:40 pm, Simon Knott wrote: > Suresh, > > I don't mind answering queries when there is a genuine problem, but I'm not > going to type "gae java task queue" into Google for you. You've got to do > some of the leg work yourself. > > As for your other query, if you want to do publish-subscribe in the client > then look at Pubnub. > > Cheers, > Simon -- 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-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Basic Question Regarding Deploying the apps with Google Engine
Suresh, I don't mind answering queries when there is a genuine problem, but I'm not going to type "gae java task queue" into Google for you. You've got to do some of the leg work yourself. As for your other query, if you want to do publish-subscribe in the client then look at Pubnub. 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 the web visit https://groups.google.com/d/msg/google-appengine-java/-/WgE301DKUdUJ. To post to this group, send email to google-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: ConcurrentModificationException question
I would like to hear Ikai or other Google folk weigh in on this point, as I find that caveat quite unsettling myself.I would like to hear why it is possible to get those exceptions and the transaction still succeed. Broc On Dec 15, 2:24 am, coltsith wrote: > Hi Broc, thanks for the reply. > > This sounds great to me. I'm concerned about one small note on this > page:http://code.google.com/appengine/docs/java/datastore/transactions.html > > "If your app receives an exception when submitting a transaction, it > does not always mean that the transaction failed. You can receive > DatastoreTimeoutException, ConcurrentModificationException, or > DatastoreFailureException exceptions in cases where transactions have > been committed and eventually will be applied successfully. Whenever > possible, make your datastore transactions idempotent so that if you > repeat a transaction, the end result will be the same." > > Doesn't that mean I can still get a ConcurrentModificationException > even if the write was/will be successful? And if so then that example > I outlined could still be possible? > > Thanks > > On Dec 14, 4:43 pm, Broc Seib wrote: > > > > > > > > > I think you are mistaken about ConcurrentModificationException meaning > > it will eventually commit. > > > If you get a ConcurrentModificationException, then that means the > > entity *failed* to write (because another write has modified the > > update timestamp on that entity group). You must catch that exception > > and try to write again (unless you don't want to overwrite). > > > You can see this behavior first hand here:http://gaetestjig.appspot.com/ > > and click on the "Unique Constraint" tab. Click the "Advance Alice" > > button four times, and click the "Advance Bobby" button four times (in > > any order). Now click on either button a fifth time and it will write > > the entity to the data store, and clicking the other button will > > experience a ConcurrentModificationException. > > > Broc > > > On Dec 13, 5:48 pm, coltsith wrote: > > > > I recently got a ConcurrentModificationException, and the > > > documentation states that this will be "committed and eventually will > > > be applied successfully." However I got to thinking of a possible > > > outcome: > > > > Request A modifies entity > > > Request B modifies entity and receives ConcurrentModificationException > > > D > > > Request E modifies entity > > > ConcurrentModificationException D commits and is applied, which > > > overwrites Request E's work. > > > > Can this happen? Or does Request E get its own > > > ConcurrentModificationException since (D) hasn't been committed yet? > > > > Many thanks -- 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-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: App is very slow on production - how to fix it?
I don't think it's that. My app is not so heavy. I have just one entity for now, there are no big operations, my user just saves to user entity, only one at a time. Sure, there are ways for improvement, like memcache, etc, but from App Stats it looks like database get is about 11ms, out of 600 total. So I don't think it's db problem. But I'd like to get some suggestion on finding what it is. Even my main page, which is just one image and login form, takes way too much to load [200-300ms]. On Dec 15, 11:39 am, Raphael André Bauer wrote: > 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 loading request? This is when we have to > >> start up the JVM and the Wicket framework. Do subsequent requests return > >> much faster? > > The development datastore is always much much much faster as the > "real" datastore. > > Most likely you are runninng into issues > like:http://stackoverflow.com/questions/7049717/appengines-entity-group-wr... > > Check out "usage notes" > at:http://code.google.com/appengine/docs/java/datastore/hr/overview.html > > A "cool" thing would be to artificially throttle the development > datastore to notice such problems early on and not when deploying the > app. Maybe that's a feature request... > > Best, > > Raphael > > > > > > > > > > > > >> -- > >> Ikai Lan > >> Developer Programs Engineer, Google App Engine > >> plus.ikailan.com | twitter.com/ikai > > >> On Wed, Dec 14, 2011 at 1:17 AM, Paul wrote: > >> > Hi, > > >> > My app is very fast and smooth when run locally, no lag at all. But > >> > when I deploy it on server it gets really slow. Response times are few > >> > times of the acceptable ones. Pages load in 20-80ms locally, but > >> > average in production is about 500-800ms. Acceptable time would be > >> > around 100ms for most operations. I have appstats on my app, but I > >> > cannot really get what is causing the problem. > > >> > I check details in appstats and I see 3 things: > >> > datastore_v3.Get 11ms (8ms api) > >> > RPC Total 11ms (8ms api) > >> > Grand Total 525ms (8ms cpu+api) > > >> > There are details only about datastore_v3.Get, which is not a thing > >> > causing all that lag. > > >> > How can I determine what is the cause of all that? > > >> > I am using 1.5.3 SDK, HR datastore and Apache Wicket framework. > > >> > -- > >> > 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-appengine-java@googlegroups.com. > >> > To unsubscribe from this group, send email to > >> > google-appengine-java+unsubscr...@googlegroups.com. > >> > For more options, visit this group at > >> >http://groups.google.com/group/google-appengine-java?hl=en. > > > -- > > 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-appengine-java@googlegroups.com. > > To unsubscribe from this group, send email to > > google-appengine-java+unsubscr...@googlegroups.com. > > For more options, visit this group > > athttp://groups.google.com/group/google-appengine-java?hl=en. > > -- > inc:http://ars-machina.raphaelbauer.com > tech:http://ars-codia.raphaelbauer.com > web:http://raphaelbauer.com -- 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-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Basic Question Regarding Deploying the apps with Google Engine
Hi simon , I just want to implement a queue to the existing project which is deployed in google api. For ex : I have to get the set of message and publish it to the other clients . Any suggestions ? Regards, Suresh -- 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-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
[appengine-java] Re: Basic Question Regarding Deploying the apps with Google Engine
Hi, Thats fine but can u share some links which shows how to use the Task Queue API with Java ? Regards, Suresh -- 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-appengine-java@googlegroups.com. To unsubscribe from this group, send email to google-appengine-java+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-appengine-java?hl=en.
