I am migrating a number of Tiger/Xcode 2/WO 5.3 WOApplication and
WOFramework projects to Leopard/Eclipse 3.2.2/WO 5.4. I chose Eclipse
3.2.2 rather than 3.3 because of Mike's warning that nightly WOLips
versions might not be as stable as WOLips 4118. I don't want to add
to my migration problems unnecessarily.
I have managed to eliminate all of the Eclipse build errors except
one type. I using an eomodel with a horizontal inheritance hierarchy
that includes a Hardware base class and its Computer subclass. In my
WO app are WOComponents HardwareManagement and its ComputerManagement
subclass. HardwareManagement defines an instance variable "hardware"
of type Hardware. ComputerManagement inherits this hardware instance
variable but Computer objects are assigned to it. By casting hardware
to a Computer type, I am able to access Computer methods that aren't
inherited from Hardware.
This all works fine as far as the Java compiler is concerned. But
WOLips' Component Editor understandably doesn't recognize bindings
like hardware.cpuType because cpuType() is a Computer, not Hardware
method. This works fine at run-time. How do I tell Component Editor
to warn me about this rather than labeling this as an error?
Or maybe I need to rewrite my ComputerManagement implementation in
some way so that Component Editor knows that hardware is a Computer
type. I don't want to create an additional "computer" instance
variable and not use "hardware" that's inherited from
HardwareManagement.
Any suggestions would be appreciated.
Aloha,
Art
This archive was generated by hypermail 2.0.0 : Fri Oct 19 2007 - 21:22:57 EDT