search

ninjaframework / ninja-appengine

Google App Engine support for Ninja Framework
Apache License 2.0
40 stars 21 forks source link

local_datastore_service error #5

Closed sliard closed 11 years ago

sliard commented 11 years ago

When we use datastore we have an error FileNotFoundException. (run with mvn jetty:run) If I create a directory "target/ninja-appengine" manually. all is ok after

java.io.FileNotFoundException: /ninja-appengine/ninja-appengine-demo/target/ninja-appengine/local_datastore_service (No such file or directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:194) at java.io.FileOutputStream.(FileOutputStream.java:84) at com.google.appengine.api.datastore.dev.LocalDatastoreService$PersistDatastore.persist(LocalDatastoreService.java:2573) at com.google.appengine.api.datastore.dev.LocalDatastoreService$PersistDatastore.access$2500(LocalDatastoreService.java:2535) at com.google.appengine.api.datastore.dev.LocalDatastoreService$PersistDatastore$1.run(LocalDatastoreService.java:2554) at java.security.AccessController.doPrivileged(Native Method) at com.google.appengine.api.datastore.dev.LocalDatastoreService$PersistDatastore.privilegedPersist(LocalDatastoreService.java:2551) at com.google.appengine.api.datastore.dev.LocalDatastoreService$PersistDatastore.run(LocalDatastoreService.java:2541) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680)

raphaelbauer commented 11 years ago

On Thu, Apr 11, 2013 at 1:08 PM, Samuel Liard notifications@github.comwrote:

When we use datastore we have an error FileNotFoundException. (run with mvn jetty:run) If I create a directory "target/ninja-appengine" manually. all is ok after

java.io.FileNotFoundException: /ninja-appengine/ninja-appengine-demo/target/ninja-appengine/local_datastore_service (No such file or directory) at java.io.FileOutputStream.open(Native Method) at java.io.FileOutputStream.(FileOutputStream.java:194) at java.io.FileOutputStream.(FileOutputStream.java:84) at com.google.appengine.api.datastore.dev.LocalDatastoreService$PersistDatastore.persist(LocalDatastoreService.java:2573) at com.google.appengine.api.datastore.dev.LocalDatastoreService$PersistDatastore.access$2500(LocalDatastoreService.java:2535) at com.google.appengine.api.datastore.dev.LocalDatastoreService$PersistDatastore$1.run(LocalDatastoreService.java:2554) at java.security.AccessController.doPrivileged(Native Method) at com.google.appengine.api.datastore.dev.LocalDatastoreService$PersistDatastore.privilegedPersist(LocalDatastoreService.java:2551) at com.google.appengine.api.datastore.dev.LocalDatastoreService$PersistDatastore.run(LocalDatastoreService.java:2541) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439) at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918) at java.lang.Thread.run(Thread.java:680)

Yes. That is true. I am currently moving jetty stuff to appengine:devserver... That we get a 100% non hacked solution while developing. I almost finished the branch and stuff looks really good (jetty:run still does work though).

Cheers,

Raphael

sliard commented 11 years ago

Yes, use appengine:devserver is the best solution. And for the moment we can use jetty :)

Thx Raphael

raphaelbauer commented 11 years ago

On Thu, Apr 11, 2013 at 3:39 PM, Samuel Liard notifications@github.comwrote:

Yes, use appengine:devserver is the best solution. And for the moment we can use jetty :)

Hi Sam,

I more or less finished the next version of the plugin. It now uses appengine:devserver and runs quite well (tests also run etc pp).

Could you please have a look at: https://github.com/reyez/ninja-appengine/tree/feature-full-gae-devserver-support

Any feedback welcome! I plan to release that as 1.1 asap.

Best,

Raphael

sliard commented 11 years ago

Thx Raphael !

I use it without problem. GAE Development Console works.

All is good for the moment :)

Samuel

2013/4/11 Raphael A. Bauer notifications@github.com:

On Thu, Apr 11, 2013 at 3:39 PM, Samuel Liard notifications@github.comwrote:

Yes, use appengine:devserver is the best solution. And for the moment we can use jetty :)

Hi Sam,

I more or less finished the next version of the plugin. It now uses appengine:devserver and runs quite well (tests also run etc pp).

Could you please have a look at: https://github.com/reyez/ninja-appengine/tree/feature-full-gae-devserver-support

Any feedback welcome! I plan to release that as 1.1 asap.

Best,

Raphael

— Reply to this email directly or view it on GitHub.