Re: Reverse Engineering in WOLips/EOModeler not finding Driver
Re: Reverse Engineering in WOLips/EOModeler not finding Driver
- Subject: Re: Reverse Engineering in WOLips/EOModeler not finding Driver
- From: Lon Varscsak via Webobjects-dev <email@hidden>
- Date: Thu, 10 Sep 2020 07:53:00 -0700
Thanks for trying. The project itself runs fine (has for years), it's just
in EOModeler that I'm having the trouble.
On Thu, Sep 10, 2020 at 2:49 AM Markus Ruggiero <email@hidden>
wrote:
> On 9 Sep 2020, at 19:57, Lon Varscsak <email@hidden> wrote:
>
>
> Hmm, when you say driver in the "workspace" where do you mean? It's
> currently on the classpath.
>
>
> yes, of course, that's what I meant, sorry for the wrong wording.
>
> There might be other issues like driver not being compatible with the
> database (newer db, older driver ?) or some such. Did you explicitly
> specify the driver class in the connection dict in the model? I found that
> usually one does not need to do this. Having the driver on the project
> class path should be enough if the credentials and the url to the db given
> in the model are ok. Did you specify the correct plugin? URL scheme ok?
>
> Often when there are unexplicable things going on quitting Eclipse,
> manually deleting the project's build folder from the file system,
> restarting Eclipse and doing an explicit Project -> Clean can fix things.
>
> Other than that I have no idea.
>
>
> I do have credentials in the model for this, so that isn't an issue.
>
> On Fri, Sep 4, 2020 at 6:14 AM Markus Ruggiero <email@hidden>
> wrote:
>
>>
>> > On 4 Sep 2020, at 05:29, Lon Varscsak via Webobjects-dev <
>> email@hidden> wrote:
>> >
>> > Hey guys,
>> >
>> > I'm trying to do reverse engineering in EOModeler, but when I go to do
>> it it complains that it can't find a suitable driver. The drive is on the
>> classpath for the project (and works fine connecting), but I'm wondering if
>> there's something I need to do for WOLips to know about the jar file? I
>> can't find anything on it.
>> >
>>
>> Driver in the workspace is a good starting point, but reverse engineering
>> (and generating SQL) in EntityModeler does not read the Properties files in
>> your project, thus does not use and of the DB credentials specified there.
>> You must edit your Default db config in the model. These values will not be
>> used by your application but overridden by what is in the Properties
>> file(s), so no problem with db credentials and such that disagree between
>> the model connection dict and the Properties file
>>
>> ---markus---
>>
>> > Any help would be appreciated,
>> >
>> > Lon
>> > _______________________________________________
>> > 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
>>
>>
>
_______________________________________________
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