Re: creating first framework
Re: creating first framework
- Subject: Re: creating first framework
- From: Paul Yu <email@hidden>
- Date: Mon, 26 Sep 2011 12:49:56 -0400
I've learned to set the connection dictionary in the Properties.[myUsername] file of the Application not the model framework for development. Then in production or test environments, set them in /etc/WebObjects/AppInstanceName/Properties file.
Paul
On Sep 26, 2011, at 11:46 AM, David Holt wrote:
>
> On 2011-09-26, at 3:28 AM, Theodore Petrosky wrote:
>
>> thanks Paul and George,
>>
>> So here are my steps based on information gleaned from your replies.
>>
>> 1. Create new Wonder Framework. This framework is special in that it contains no Application nor DirectAction nor Session java classes.
>>
>> 2. Add a .eomodeld file for the database. if using the properties file, set up the migrations and database connection dictionary.
>
> I don't add a connection dictionary at the framework level. I always do it at the application level. I think this is because all of the examples in Wonder do it this way, so it must be right :-)
>
> d
>
>>
>> 3. Run EOGenerate (this creates the your.app.model structure)
>>
>> 4. Create the Migrations
>>
>> This completes the Framework and it is a project in Eclipse.
>>
>> 1. Create a new Wonder Project.
>> 2. RIght click the project name and Configure the build path. The new framework shows up in Add Library, Webobject Library (This one caused me a little problem as Paul referred to it as:
>>> Then just put the
>>> Framework on your Application project's classpath.
>>
>> Obviously, there was a divergence somewhere and paul refers to it as the classpath and eclipse refers to it as the build path. But for a neophyte like me, I was confused.
>>
>> But Voila, it works beautifully.
>>
>> Thanks again.
>>
>> Ted
>>
>>
>>
>> --- On Sun, 9/25/11, Paul D Yu <email@hidden> wrote:
>>
>>> From: Paul D Yu <email@hidden>
>>> Subject: Re: creating first framework
>>> To: "Theodore Petrosky" <email@hidden>
>>> Date: Sunday, September 25, 2011, 6:49 PM
>>> Ted
>>>
>>> Here's the simple ModelFramework that I created for my
>>> Fluffy Bunny presentation.
>>>
>>> Should give you the pattern. Then just put the
>>> Framework on your Application project's classpath.
>>> Then when you embed the frameworks I believe it will just be
>>> copied into the Application tar ball.
>>>
>>> Paul
>>>
>>> On Sep 25, 2011, at 6:17 PM, Theodore Petrosky wrote:
>>>
>>>>
>>>> 1. Create a new framework project
>>>>
>>>> ok
>>>>
>>>> 2. add the framework to the build path of your primary
>>> project.
>>>>
>>>> a framework doesn't need to be compiled? what about
>>> the references to the .eomodeld file
>>>>
>>>> the attributes class reference
>>> com.something.model.EOClass and what about the .eogen file?
>>>>
>>>> My goal is to create a framework that has only the
>>> eomodeld and eogen so I can create multiple apps that
>>> reference this one .eomodeld and only modify the one
>>> eomodeld file and the migrations in the framework.
>>>>
>>>>
>>>> Ted
>>>>
>>>>
>>>>
>>>>
>>>> --- On Sun, 9/25/11, George Domurot <email@hidden>
>>> wrote:
>>>>
>>>>> From: George Domurot <email@hidden>
>>>>> Subject: Re: creating first framework
>>>>> To: "Theodore Petrosky" <email@hidden>
>>>>> Cc: email@hidden
>>>>> Date: Sunday, September 25, 2011, 11:29 AM
>>>>> Hi Ted,
>>>>>
>>>>> Frameworks are pretty straight forward.
>>> Create a new
>>>>> framework project, then add the framework to the
>>> build path
>>>>> of your primary project.
>>>>>
>>>>> Then try a test. Add a class to your
>>> framework and
>>>>> use it in your project.
>>>>>
>>>>> -G
>>>>>
>>>>> On Sep 25, 2011, at 8:15 AM, Theodore Petrosky
>>> wrote:
>>>>>
>>>>>> I have a Wonder project that is growing.
>>>>>>
>>>>>> I want to create a framework that includes
>>> the
>>>>> migrations and EOModel. Problem is I have never
>>> created a
>>>>> framework and I don't understand the process.
>>>>>>
>>>>>> I checked the examples and as best I could
>>> the
>>>>> multitude of tutorials that exist to no avail.
>>>>>>
>>>>>> I don't know where to start.
>>>>>>
>>>>>> Ted
>>>>>>
>>> _______________________________________________
>>>>>> 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
>>>
>>>
>> _______________________________________________
>> 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
_______________________________________________
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