Re: Velocity EOGenerator: refactor package?
Re: Velocity EOGenerator: refactor package?
- Subject: Re: Velocity EOGenerator: refactor package?
- From: Patrick Robinson <email@hidden>
- Date: Tue, 24 Jun 2008 16:25:25 -0400
I'm happy to have the _Entity.java files regenerated as often as
EOGenerator likes. But definitely not all those Entity.java files. :-)
This seems to be a more straightforward approach, and also seems to
work well. I hadn't noticed the "update fully qualifierd names..."
box when I was doing this, before. Thanks for the tip!
- Patrick
On Jun 24, 2008, at 12:11 PM, Don Lindsay wrote:
Hello;
If you are using WOLips and Eclipse. Double click on your eogen
file for your project, if you cannot see it click the small
triangle in the upper right of the project explorer and choose
filters and ensure eogen is not checked. Once you are editing your
eogen, set the package there. Then just regenerate your entities.
If you are using WOLips and Ecipse and you do not want to re-
generate your entities. Select each entity that you want to put in
a new package by holding down the Open Apple/Command key and
clicking on it in project explorer. AFter you have them all
selected, right click, choose refactor | Move, type in the new
package. Make sure you select "Update fully qualified names in non-
Java text files" (this will catch your plist files in your
eomodel. Click ok then go though the preview to ensure the changes
were made correctly.
Don
On Jun 24, 2008, at 10:10 AM, Patrick Robinson wrote:
This is a bit old, but I assume it's still true:
On Dec 19, 2007, at 8:48 PM, Mike Schrag wrote:
is it possible to setup packagename argument in the EOGenerator
command or turn on create package functionality?
No, because this is really a setting of your EOModel, not just of
the generation of Java files. However, there is a new setting
coming to Entity Modeler that will allow you to define the
default package name for entities (which WILL actually write into
the model file properly). (coming = probably next week)
Is there a way to mass-refactor your entities' classes into a
different package, and (the real problem!) have that change
reflected in the model? I'm dealing with a rather old project
where the entity classes had been in the default package. It took
a bit of reading (old posts) and experimenting to figure out that
you can't change the existing package for all your entity classes
by just specifying something in the eogen file. You apparently
have to specify the "fully qualified" package.class name in each
entity. OK, so I did that, and all is now as it should be. But
what do you do if you want to change the package for your
entities' classes?
Did I miss out on the easy and magical way to do this? :-)
- Patrick
_______________________________________________
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