Hi,
you can force Eclipse to generate the import statements in a WOBuilder
compatible way.
Just take a loo into the section 'Bugs/Issues/Other Things' of WOLips
help.
Ulrich
Am Samstag, 22.02.03 um 05:56 Uhr schrieb Dirk Olmes:
> Ian McDougall wrote:
>> win 2k, eclipse M5, WOLips 0.9.9, WO 5.2
>> I've been struggling with a problem that comes up every now and then
>> and
>> wastes countless hours of my time. It happens when WOBuilder refuses
>> to
>> recognize classes located in one of my frameworks.
>
> That's not the fault of WOLips, I suppose. WOBuilder needs correct
> import statements in the Java file to display info correctly. Make
> sure you import com.webobjects.appserver.* and
> com.webobjects.foundation.* in your component classes. Make sure that
> Eclipse doesn't replace these with individual class imports.
>
> As to classes in frameworks, I bet you use them in packages. WOBuilder
> doesn't find them in the package, then. What helps is to specify the
> fully qualified class name in the..ypeInfo javadoc comment.
>
> HTH,
>
> -dirk
>
This archive was generated by hypermail 2.0.0 : Sat Feb 22 2003 - 11:48:40 EST