Thanks Jason,As also pointed out by Shawn that we cannot simply use Key in
client code we need write a super class instead.
So now i have changed my implementation to use Long instead of key.

On Tue, May 12, 2009 at 12:03 AM, Jason (Google) <apija...@google.com>wrote:

> Hi Vijay. I believe the issue here is that the GWT compiler cannot find the
> source code for the Key class, as detailed in the post at
> http://fredsa.allen-sauer.com/2009/04/1st-look-at-app-engine-using-jdo.html
> .
>
> You should be able to follow the steps in that post, stubbing out the Key
> class, to get your application working.
>
> - Jason
>
>
> On Fri, May 8, 2009 at 3:04 PM, vijay <mymail.vi...@gmail.com> wrote:
>
>> Hi,
>> I am using GWT+ Appengine for building a simple web application and got
>> stuck with a error.
>>
>> I am using JDO to save some objects in datastore, I have a created a
>> service which returns a field of persistent class which is of type
>>  com.google.appengine.api.datastore.Key, i am calling this service from my
>> main .java file and hence imported the required path. When running the
>> application I got error as
>>
>> Line 6: The import com.google.appengine cannot be resolved
>>
>> The path com.google.appengine was auto completed and also it was not
>> showing any error for files under .server package, the error are only for
>> files under .client package.
>> I think I am missing something very basic here. Is there any restriction
>> that I cannot import appengine packages in .client package?
>>
>> Please let me know if my problem is not clear.
>>
>> Regards,
>> Vijay
>>
>>
>>
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to 
google-appengine+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to