• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: EOGenerator & D2JC
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: EOGenerator & D2JC


  • Subject: Re: EOGenerator & D2JC
  • From: David Avendasora <email@hidden>
  • Date: Thu, 16 Feb 2006 07:58:55 +0000

I received a VERY helpful response from Carl Lindberg, one of the developers of EOGenerator. Information inserted below:

On Feb 15, 2006, at 2:39 PM, David Avendasora wrote:

Some other frustrations with EOGenerator:

1) Since I have two different custom classes for each entity (for both Server- and Client-side - com.bestmaid.erp.server.Class and com.bestmaid.erp.client.Class) I have to run two separate terminal commands with different -destination parameters to generate both sets of java files.

If I use the -packagedirs flag, it will automatically build the java files in the proper package directory structure defined by the class name in EOModeler. This removes the need to specify different locations for server and client-side classes.



2) Even-though I specify the proper -destination for the server classes, it writes the package information for the client classes into the _Class.java files so I have to go back and manually change the _Class.java files, which then get over-written by EOGenerator the next time it is run.

I was accidentally generating the server-side class files using the - javaclient flag, which of course used the java client class and package name. My bad.



Am I missing something fundamental in EOGenerator or EOModeler? I've been through all the documentation for EOGenerator (readme.rtf) and looked at Chuck's notes in Practical WebObjects.


On Feb 15, 2006, at 1:40 PM, David Avendasora wrote:

Sorry about the double post, I forgot the subject...duh.

I'm working on a D2JC project and right now I only need custom client-side java classes. The problem is that if I don't put a custom class name in the server side, EOGenerator will not generate the java classes.

This is actually a bug. EOGenerator only checks the Class Name, not the Client-Side Class Name to determine if it should generate code. Carl said he would fix it and send me a patch. This fix will also make it into the next version of EOGenerator.


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >EOGenerator & D2JC (From: David Avendasora <email@hidden>)

  • Prev by Date: Re: Problem with page encoding
  • Next by Date: Re: No Instance issue from WebPDFReports 1.0
  • Previous by thread: EOGenerator & D2JC
  • Next by thread: Postgresql + booleans = error
  • Index(es):
    • Date
    • Thread