Hi Guillaume,

Thanks a lot for the pointer to the javadoc at
http://code.google.com/appengine/docs/java/tools/localunittesting/javadoc/com/google/appengine/tools/development/testing/LocalBlobstoreServiceTestConfig.htmle.google.com/appengine/docs/java/tools/localunittesting/javadoc/com/google/appengine/tools/development/testing/LocalBlobstoreServiceTestConfig.html

I just read the developper doc for LocalTesting and didn't find any
parag about Blobstore and so deduced (wrongly) that I had nothing to
do.  When I saw javadoc, it became clear that I had to do the same
kind of init I am used to for datastore.

When initialized properly, my junit tests work fine.

BTW, don't you think that the dev doc should be updated to also
mention Blobstore service ?

Thanks again (Merci beaucoup! ;-) )
didier

On Oct 13, 11:12 am, Guillaume Laforge <[email protected]> wrote:
> In your test case, are you using the testing 
> support?http://code.google.com/intl/fr-FR/appengine/docs/java/tools/localunit...
te rt
> I've used it in the past for the datastore and memcache, but I've not
>

On Oct 13, 11:12 am, Guillaume Laforge <[email protected]> wrote:
> In your test case, are you using the testing 
> support?http://code.google.com/intl/fr-FR/appengine/docs/java/tools/localunit...
>op

On Oct 13, 11:12 am, Guillaume Laforge <[email protected]> wrote:
> In your test case, are you using the testing 
> support?http://code.google.com/intl/fr-FR/appengine/docs/java/tools/localunit...
>e  used it for testing my blobstore usage yet.
> But I think it should be working.
>
> Look at the documentation above, especially the structure of the unit tests.
> And be sure to configure the 
> LocalBlobstoreServiceTestConfig:http://code.google.com/appengine/docs/java/tools/localunittesting/jav...
>
>
>
> On Wed, Oct 13, 2010 at 11:05, Didier Durand <[email protected]> wrote:
> > Thanks Romesh, Guillaume,
>
> > -> Romesh: I am in 1.3.7 but I get the message.
>
> > I don't run in local app jetty server but just under JUnit in a
> > testcase: is that the reason ?
>
> > didier
>
> >> On Wed, Oct 13, 2010 at 10:22, romesh soni <[email protected]> wrote:
> >> > Hi Didier,
> >> > You have nothing to do anything special for using blobstore service in 
> >> > dev.
> >> > It seems that your app engine api is not up to date. Can you try updating
> >> > your app engine. The blobstore api has been added recently.
>
> >> > See what your error is saying:
> >> > package 'blobstore' or call 'DeleteBlob()' was not found.
>
> >> > The blobstore service fine without any issue in dev env too.
>
> >> > Thanks
> >> > Romesh
>
> >> > On Wed, Oct 13, 2010 at 1:48 PM, Didier Durand <[email protected]>
> >> > wrote:
>
> >> >> Hi there,
>
> >> >> Trying to use BlobstoreService via the SDK on my local dev machine
> >> >> (Ubuntu): I get CallNotFoundException if I try to use either
> >> >> BlobstoreService.delete() or BlobstoreService.fetchData() in Junit
> >> >> tests. See trace below.
>
> >> >> a) is it possible BlobsotBlobstoreService in dev environment ?
>
> >> >> b) Do I need to do something specific to initialize or emulate it when
> >> >> being in dev as it has to be done for local DataStore ?
>
> >> >> thanks
> >> >> didier
>
> >> >> com.google.apphosting.api.ApiProxy$CallNotFoundException: The API
> >> >> package 'blobstore' or call 'DeleteBlob()' was not found.
> >> >>        at
> >> >> com.google.apphosting.api.ApiProxy.makeSyncCall(ApiProxy.java:95)
> >> >>        at
> >> >> com.google.apphosting.api.ApiProxy.makeSyncCall(ApiProxy.java:48)
> >> >>        at
>
> >> >> com.google.appengine.api.blobstore.BlobstoreServiceImpl.delete(BlobstoreServiceImpl.java:
> >> >> 108)
> >> >>        at
>
> >> >> net.didierdurand.gwtlib.server.TestBlob.testDeleteInvalidBlob(TestBlob.java:
> >> >> 37)
> >> >>        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >> >>        at
> >> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:
> >> >> 57)
> >> >>        at
>
> >> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:
> >> >> 43)
> >> >>        at java.lang.reflect.Method.invoke(Method.java:616)
> >> >>        at org.junit.runners.model.FrameworkMethod
> >> >> $1.runReflectiveCall(FrameworkMethod.java:44)
> >> >>        at
>
> >> >> org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:
> >> >> 15)
> >> >>        at
>
> >> >> org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:
> >> >> 41)
> >> >>        at
>
> >> >> org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:
> >> >> 20)
> >> >>        at
>
> >> >> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:
> >> >> 76)
> >> >>        at
>
> >> >> org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:
> >> >> 50)
> >> >>        at org.junit.runners.ParentRunner$3.run(ParentRunner.java:193)
> >> >>        at 
> >> >> org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:52)
> >> >>        at
> >> >> org.junit.runners.ParentRunner.runChildren(ParentRunner.java:191)
> >> >>        at 
> >> >> org.junit.runners.ParentRunner.access$000(ParentRunner.java:42)
> >> >>        at 
> >> >> org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:184)
> >> >>        at org.junit.runners.ParentRunner.run(ParentRunner.java:236)
> >> >>        at
>
> >> >> org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:
> >> >> 46)
> >> >>        at
>
> >> >> org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:
> >> >> 38)
> >> >>        at
>
> >> >> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:
> >> >> 467)
> >> >>        at
>
> >> >> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:
> >> >> 683)
> >> >>        at
>
> >> >> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:
> >> >> 390)
> >> >>        at
>
> >> >> org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(RemoteTestRunner.java:
> >> >> 197)
>
> >> >> --
> >> >> 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
> >> >> [email protected].
> >> >> To unsubscribe from this group, send email to
> >> >> [email protected].
> >> >> 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 
> >> > [email protected].
> >> > To unsubscribe from this group, send email to
> >> > [email protected].
> >> > For more options, visit this group at
> >> >http://groups.google.com/group/google-appengine-java?hl=en.
>
> >> --
> >> Guillaume Laforge
> >> Groovy Project Manager
> >> Head of Groovy Development at SpringSourcehttp://www.springsource.com/g2one
>
> > --
> > 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 [email protected].
> > To unsubscribe from this group, send email to 
> > [email protected].
> > For more options, visit this group 
> > athttp://groups.google.com/group/google-appengine-java?hl=en.
>
> --
> Guillaume Laforge
> Groovy Project Manager
> Head of Groovy Development at SpringSourcehttp://www.springsource.com/g2one

-- 
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 [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine-java?hl=en.

Reply via email to