Re: How do I configure an EOModel's connection info if it comes from a framework
Re: How do I configure an EOModel's connection info if it comes from a framework
- Subject: Re: How do I configure an EOModel's connection info if it comes from a framework
- From: Paul Yu <email@hidden>
- Date: Wed, 02 Oct 2013 18:40:56 -0400
Riccardo
I store the deployed connection dictionaries under the
/etc/WebObjects/[AppInstanceName]/Properties
file
So I don't have to check these into my source repo.
Then in WOLips I have a Properties.paul where I would store my development connection dictionaries. Then I would have an ignore for *.paul file patterns.
Does that help?
Paul
On Oct 2, 2013, at 6:35 PM, Riccardo De Menna <email@hidden> wrote:
> Yes... Wonder is in place.
>
> Riccardo De Menna
>
>> On 03/ott/2013, at 00:18, Chuck Hill <email@hidden> wrote:
>>
>> Are you using Project Wonder? If not, start. It provides all of this for
>> free. E.g. "there is a property for that"
>>
>> Chuck
>>
>>
>>> On 2013-10-02 3:04 PM, "Riccardo De Menna" <email@hidden> wrote:
>>>
>>> Hi All,
>>>
>>> I have a question regarding how to configure an EOModel. The model is
>>> complete with connection info, db driver setup and so on and it works
>>> fine.
>>> How should I behave if I wanted it to be more of an abstract thing and
>>> stick it into a framework so that different apps can include it, but
>>> replace their specific connection info that is relevant to them only?
>>>
>>> Putting the model in the framework seems straightforward, but when I run
>>> the app, the model uses the connection info it finds in the framework
>>> copy of itself .
>>>
>>> I clumsily attempted to duplicate the model in the app, and it does seem
>>> to replace the original model in the framework while editing (allowing me
>>> to enter custom connection details), but at runtime, it still picks up
>>> the original one.
>>>
>>> Am I missing an obvious way of doing this?
>>>
>>> regards,
>>> Riccardo
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Webobjects-dev mailing list (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>> age.net
>>>
>>> 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
_______________________________________________
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