I have that crazy idea that a REST project could use some Veogen love. It could make it easier for people who start with ERRest, so that when they generate the EOs with Veogen, it would also generate two classes for the REST controller. So the idea is that if you have a project created with the (yet to be done) ERRest project template, when you call Veogen, it would create the following:
org.wocommunity.model._Entity.java org.wocommunity.model.Entity.java org.wocommunity.rest.controllers._EntityController.java org.wocommunity.rest.controllers.EntityController.java The idea is that _EntityController.java would extends from ERXDefaultRouteController and the methods in _EntityController.java would have the code for basic REST operations (eg, in createAction(), it would have a call to the creation() method, it would have default key filters, etc.). EntityController.java will be there to override what's in _EntityController.java. So anyway, the question is about how to generate the four files. I was looking at some WOLips code and I was thinking that the "JavaClient" option in the .eogen file would do something similar to what I want to do, and I was expecting that that the "JavaClient" option would create both server and client-side EOs, but I tried it and I didn't get a client-side file. I guess one of the options would be to have two .eogen files, one for REST, the other for the EO, but is there another way of handling this? _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (Webobjects-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
