I'm CC'ing this to the list also, and I can put it up on the Wiki
maybe later tonight (in the middle of "real work" things at the moment):
Yeah, this is a process that isn't well-documented. We depend on
EOGenerator for Java class file generation. It's a much more
powerful system for generating Java classes than the traditional
mechanism. I wrote up some information in the Wikibook a while ago
( http://en.wikibooks.org/wiki/Programming:WebObjects/EOF/Using_EOF/
EOGenerator ) on EOGenerator independent of Entity Modeler.
Inside of WOLips, you will then need to go to
Window=>Preferences=>WOlips=>EOGenerator and setup the folders to
point to the correct location. I'm actually contemplating whether
there is some way to ship EOGenerator INSIDE of wolips, but it's a
native binary and thus presents some complications.
Once it's configured, you can create a new EOGenerator file that
specifies things like dependent models, etc, that are used to
generate your java files. You can manually create the EOGenerator
file in Eclipse with the New EOGenerator File Wizard, or you can
right-click on an EOModel and Create EOGenerator File from EOModel.
This will "figure out" most of the things you need.
You can either right-click=>WOLips Tools=>EOGenerate ... on
that .eogen file that is created, or you can turn on Automatic
EOGeneration at build time (Window=>Preferences=>WOlips=>Build(i
think?)=>Auto-EOGenerate). What this does is watch for any time
files inside of your eomodel change, and it automatically finds eogen
files dependent on that model (either direct reference or as ref-
models) and kicks of eogeneration of java files from those models
(which in turn auto-incremental-builds in Eclipse).
Hopefully this clarifies things a little. The setup is obviously a
little more complicated than old EOModeler, but the payoff is totally
worth it. The generated code is overall MUCH nicer to work with.
ms
On Aug 21, 2006, at 11:45 AM, Timothy Kompanchenko wrote:
> Greetings Michael,
>
> It was great to see your part of the presentation for the Entity
> Modeler during the related WWDC06 session. It was difficult to
> formulate all of the questions while chatting with you after the
> session. During the session it became very clear that we need to
> switch from Xcode/WebObjects Builders/EOModeler to Eclipse/WOLips/
> Entity Modeler for obvious reasons. While SQL generation seems to
> be pretty straight-forward, I am not sure about the best way to
> generate java classes - I saw you do it during the session, but
> until I get the sessions DVD it will be difficult to remember. I am
> having difficulties finding appropriate resources online. Would you
> be able to send me a couple of links to steer me in the right
> direction? Maybe a short "how to generate java classes" tip.
>
> Thanks for taking a little bit of your time for this, considering
> your very busy schedule.
>
> Timothy Kompanchenko
> tymof..ac.com
> 904.315.6620
This archive was generated by hypermail 2.0.0 : Mon Aug 21 2006 - 12:05:23 EDT