Progress... some success (thanks for all feedback to date)...
I have reinstalled WebObjects from the 5.2 and this provided the missing
DLLs etc... I am now getting EOGenerator to work to some degree. Any
manual generation creates a "empty" class (the "underscore" class
filename e.g. _Author.java) with no attributes, but when I build the
project EOGenerator runs (despite explicitly deselecting the WOLips
Build option of "Auto EOGenerate on build") and builds the classes
correctly with the attributes from the model. Simply, behaviour appears
to be that the manual process fails, but the auto process succeeds (and
runs on every build). Is this a bug that needs to be logged?
Thanks,
Peter Thompson
-----Original Message-----
From: Stephen Edwards [mailto:edward..s.vt.edu]
Sent: Thursday, 2 August 2007 2:11 a.m.
To: woproject-de..bjectstyle.org
Subject: Re: Help with EOGenerator - Windows XP Development
Peter Thompson wrote:
> "This application has failed to start because the EOAccess.dll was
not found.
This message (from trying eogenerator from the command line) indicates a
likely problem. This dll comes from your c:\Apple\Library\Executables
directory (from your WO install; replace c:\Apple with your personal
NEXT_ROOT).
If you install WO normally, this subdir is automatically added to your
system's PATH variable, and so it is available for eogenerator to use,
too.
Check your path and add this dir. If you can't run eogenerator
successfully from the command line, it's a good bet it won't run from
inside eclipse, either.
As a side note ...
> I have configured WOLips EOGenerator options as follows:
>
> > Executable Path = D:\\dev\\apps\\eogenerator\\eogenerator.exe
> > Template Folder = D:\\dev\\apps\\eogenerator\\Templates
> > Java Template = JavaSourceEOF52.eotemplate
> > Subclass Java Template = JavaSubclassSourceEOF5.eotemplate
I just use forward slashes for the paths, and it works perfectly
(winxp).
Since I use both win and mac development platforms, I really hate all
the backslashes. Especially in the woproject/* files. They create
annoying problems with version control across multiple OSes.
Within the JVM, however, forward slashes always work for specifying
files on win platforms, so religiously using the file.separator sequence
on windows seems to cause way problems than it solves ...
and it solves almost none (it is only useful on Windows when
communicating file paths to external tools, but is nearly useless
internally within Java tools).
OK, so here's a related question:
If one specifies the eogenerator executable path in the wolips
preferences in eclipse, then why in the world is it also hard-coded into
the generated *.eogen files? That also makes cross-platform (and
cross-developer) version control annoying and troublesome, for no
readily apparent reason. It also means that *.eogen files can contain
stale information when you change the setting in the prefs (no single
point of control over this platform-specific setting). Is there a good
reason for that?
-- Steve
------------------------------------------------------------------------
--- Virginia Tech, CS Dept. Web-CAT: Web-based Center for Software Testing 660 McBryde Hall (0106) Automatic grading using student-written tests Blacksburg, VA 24061 USA http://web-cat.sourceforge.net/ (540)-231-5723 http://people.cs.vt.edu/~edwards/
This archive was generated by hypermail 2.0.0 : Wed Aug 01 2007 - 19:25:02 EDT