Re: No type for token
Thanks Brandon, I tied cleaning and GWT compile just in case (it did work
for getting request factory validation to work, once) but it didn't have
the desired effect. My request context is very similar to the one you
linked, the difference is I used only RequestT for all my method
invocations, not the InstanceRequestT, T. Here's the code bit:
@ServiceName(value = com.masteriti.manager.server.access.PersonDao,
locator =
com.masteriti.manager.server.locator.DaoServiceLocator)
public interface PersonRequest extends RequestContext {
RequestListPersonProxy listAll();
RequestVoid save(PersonProxy person);
RequestPersonProxy saveAndReturn(PersonProxy person);
RequestVoid delete(PersonProxy person);
}
The other thing I noticed looking around demo source code is that hardly
anyone uses @Embedded objects in their entities. Even the DynaTableRF
source doesn't use the @Embedded notation as shown in Google's RequestFactory
Tutorialhttp://code.google.com/webtoolkit/doc/latest/DevGuideRequestFactory.html#valueProxies,
instead it simply has
private Address address = new Address();
I'll try that today and see if it works, but any other suggestions would be
welcome!
Marco
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/xkDH2eCm9dcJ.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=en.
Re: No type for token
On Monday, February 20, 2012 9:29:54 AM UTC-5, Thomas Broyer wrote: Several things: - Annotation processing in Eclipse a barely usable. I battled for hours yesterday to make it refresh the generated DeobfuscatorBuilder. IIRC, I refresh the project in eclipse, then restarted it, then disabled annotation processing, deleted the .apt_generated folder and re-enabled annotation processing. If you can use Maven for your project, then I'd bet it works much better there! (I had the issue on the gwt-user project itself, so it wasn't an option for me) Next time, I'll try setting up a build action (or whatever) to run javac -proc:only instead of relying of Eclipse's built-in (and awfully buggy) APT. Thanks for the reply, Thomas. This item did the trick. Following your procedure to refresh the project took care of the No type for token... error. The code now runs without errors although its still not saving addresses, but at least I'll have an opportunity to debug it in my code. I've never used maven, and have been resistant to adding more new stuff on my plate, but I may have to at this point. Thanks -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/yPhwdjkGGU8J. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
