Hey spierce, Your event class needs to go in the shared package (com.spierce7.gwt.test.shared.Event). Both the server and client will use that class. The Event should implement IsSerializable, and have an empty constructor at the minimum. As with all serialized objects, all it's members need to be serializable. If your using java.util.Date, you should be fine.
Tom On Aug 3, 7:14 pm, spierce7 <[email protected]> wrote: > Hey guys, I've been mess making an app for a while now, and I've > finally got something that is able to save an entity on the server. > That entity (to keep it simple) is of type Event. It has 2 Date > objects: startDate and endDate. I understand how to do queries and > what not, but what I found my program encountering issues with is in > my method within the ServiceImpl, getEvents(), it's having a difficult > time distinguishing between my client side Event object and my server > side. This creates issues when I try to have my return type as > List<Event>. How should I be handling this? Does the client side Event > object need to be serializable? I've tried this, still without much > luck. > > On the client side Service, and ServiceAsync classes, should I be > declaring the types through the server side object? Example: > public List<com.spierce7.gwt.test.server.Event> getEvents(); > or should I perhaps be doing the same thing, but with the client side > on the server? I've tried both of these, but can't seem to get it to > be happy with whatever I put. Any direction in this would be greatly > appreciated! Thanks! -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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-web-toolkit?hl=en.
