No, it is two separate commands.
Here's my two separate eogenerator commands that I use in terminal:
Server Side
eogenerator -model ERP.eomodeld -destination src/ -packagedirs -
verbose -java -javaTemplate /Developer/EOGenerator/
JavaSource.eotemplate -subclassJavaTemplate /Developer/EOGenerator/
JavaSubclassSource.eotemplate
Client Side
eogenerator -model ERP.eomodeld -destination src/ -packagedirs -
verbose -javaclient -javaTemplate /Developer/EOGenerator/
JavaClientSource.eotemplate -subclassJavaTemplate /Developer/
EOGenerator/JavaClientSubclassSource.eotemplate
I set up WOLips to using two .eogen files. One points to the server-
side templates and the other to the client-side templates.
Maybe WOLips' EOGen file needs a flag for "Client Side" so it
executes eogenerator with the -javaclient flag set?
Even with EOGenerate not working quite "perfectly" for me, it is
still so much better than using EOGenerator from the terminal from
the user-friendly perspective!
I mistakenly marked the bug as "Major" in Jira, it should have been
"minor". I tried to change it, but alas, I can't.
Dave
On Aug 28, 2006, at 3:10 PM, Mike Schrag wrote:
> You have a single eogenerator commandline that generates files into
> two different source folders? What exactly is your commandline
> script for this?
>
> On Aug 28, 2006, at 1:47 PM, David Avendasora wrote:
>
>> Hi,
>>
>> I have both Server-side and Client-side classes. When I generate
>> them manually using EOGenerator from a terminal window, it works
>> as expected, but when I use WOlips' "EOGenerate..." function I run
>> into two problems:
>>
>> 1) If an Entity has only a client-side class, neither an
>> Entity.java nor an _Entity.java file is generated.
>>
>> 2) When there are both server- and client-side classes specified,
>> the client-side java files are generated into the server-side
>> class package.
>>
>> I will submit bugs to Jira on this.
>>
>> Thanks,
>>
>> Dave
>
>
>
This archive was generated by hypermail 2.0.0 : Mon Aug 28 2006 - 15:56:06 EDT