Hi,
this is a know issue.
Workaround: Under Window/Preferences/Java/Organize Import set the
number to 2. This will organize imports in a WOBuilder compatible way.
Ulrich
Am Donnerstag, 23.01.03 um 10:32 Uhr schrieb Anders Peterson:
> This is a consequence of using eclipse...
>
> Begin forwarded message:
>
>> From: Anders Peterson <anders_peterso..ptimatika.se>
>> Date: tor jan 23, 2003 10:31:03 Europe/Stockholm
>> To: webobjects-de..mnigroup.com
>> Subject: Re: WODisplayGroup in WOBuilder
>>
>> I got it!
>>
>> If I replace these imports
>>
>> import com.webobjects.appserver.WOComponent;
>> import com.webobjects.appserver.WOContext;
>> import com.webobjects.appserver.WODisplayGroup;
>> import com.webobjects.foundation.NSDictionary;
>>
>> with the default set
>>
>> import com.webobjects.foundation.*;
>> import com.webobjects.appserver.*;
>> import com.webobjects.eocontrol.*;
>> import com.webobjects.eoaccess.*;
>>
>> things start to work.
>>
>> /Anders
>>
>> On torsdag, jan 23, 2003, at 10:24 Europe/Stockholm, Anders Peterson
>> wrote:
>>
>>> Hi all,
>>>
>>> I have a problem with WOBuilder and display groups. There's no
>>> problem running the application, but while editing WOBuilder doesn't
>>> recognize keys of type WODisplayGroup (I can't use the special
>>> editor or make bindings by drag-and-drop).
>>>
>>> If I create a new display group component things work! I have many
>>> existing components. None of those work. I've experimented a bit,
>>> but can't see what the key to getting it working is. Anyone know?
>>>
>>> Creating new display group keys in the existing pages doesn't work
>>> either.
>>>
>>> /Anders
>
>
This archive was generated by hypermail 2.0.0 : Thu Jan 23 2003 - 04:58:34 EST