Hi Amrik,
the way to manage frameworks with WOLips has changed slightly.
Bring up the Java Build Path properties:
If the WOFrameworks container is not visible add one with the "Add
Library" button. To change a existing WOFrameworks container you have
to select it and click on "Edit".
Don't add frameworks that are projects in the workspace. Select them
under the projects tab.
Ulrich
Am 16.02.2004 um 08:36 schrieb Amrik:
> Hi Ulrich,
>
> I am able to open my EOModels in Eclipse by following your solution.
> But after updating WOLips from 1.0.6 to 1.0.7 version,
> when I am trying to add any framework/variables to the Eclipse
> Application its giving an error saying:
>
> please use WOlips classpath container instead.
>
> Even I tried to add the frameworks manually into
> ant.frameworks.wo.wolocalroot file, but the changes are not getting
> reflected in the Eclipse
> Application.
>
> Can you suggest any solution to this problem.
>
>
> Thanks
> Amrik
>
>
>
>
>
>
> On Friday, February 6, 2004, at 03:04 PM, Ulrich Köster wrote:
>
>> Hi Amrik,
>>
>> to get rid of the problem with EOModels:
>>
>>
>>
>> • 1. Update to WOLips 1.0.7.23 or later
>> • 2. Open the preferences. Window->Preferences
>> • 3. Restore the defaults of the
>> WOLips->ProjectBuilder->WOAppResources exclude page.
>> • 4. Save the preferences.
>> • 5. Open your PB.project files with the text editor.
>> • 6. If there are entries like foo.eomodeld/index.eomodeld right
>> click on the project root and select WOLips->Update PB.project
>>
>>
>> Try a driver for JDBC 1 and 2.
>>
>> Ulrich
>>
>> Am 06.02.2004 um 10:16 schrieb Amrik:
>>
>>> Hi Ulrich,
>>>
>>> The driver is for JDBC2, and I am facing one more problem i.e I
>>> have imported a framework into Eclipse which has been
>>> been developed using WebObjects, that framework has an EOModel.
>>> But after importing it into Eclipse when I am trying to open that
>>> EOModel in Eclipse by double-clicking index.eomodeld, its giving an
>>> exception saying
>>>
>>> - NSInvalid ArgumentException
>>> Reason: addModel -- EOModelGroup 0x54be810:
>>> illegal attempt to add model named AP more than once
>>>
>>>
>>> I have checked the Framework, it has only a single EOModel with
>>> name AP.
>>>
>>> Can you suggest any solution to this problem
>>>
>>>
>>> Thanks
>>> Amrik
>>>
>>>
>>>
>>>
>>>
>>> On Friday, February 6, 2004, at 12:44 PM, Ulrich Köster wrote:
>>>
>>>> Hi Amrik,
>>>>
>>>> is the driver for JDBC 1 and 2. Are you able to connect with
>>>> EOModeler?
>>>>
>>>> Ulrich
>>>>
>>>> Am 06.02.2004 um 05:40 schrieb Amrik:
>>>>
>>>>> Hi Ulrich,
>>>>>
>>>>> I am setting the Sybase Driver to the classpath by defining a
>>>>> variable in the application which will hold
>>>>> the path to that driver class and in turn adding that variable to
>>>>> the application using (Add Other Framework option)
>>>>> But at Runtime its saying :
>>>>>
>>>>> An exception occurred while trying to open a channel:
>>>>> com.webobjects.jdbcadaptor.JDBCAdaptorException:
>>>>> JDBC connection failed for driver
>>>>> :'com.sybase.jdbc2.jdbc.SybDriver'.
>>>>> Driver not found in Java Runtime! Please verify your CLASSPATH
>>>>> environment
>>>>> variable.
>>>>>
>>>>> But in the current Classpath to my Application includes
>>>>> sybdriver.jar i.e
>>>>> D:\Apple\Library\Java\Extensions\sybdriver.jar;
>>>>>
>>>>> Do you have any solution to this problem.
>>>>>
>>>>>
>>>>> Thanks
>>>>> Amrik
>>>>>
>>>>
>>>
This archive was generated by hypermail 2.0.0 : Mon Feb 16 2004 - 04:01:18 EST