• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
WO Builder - binding to superclass
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

WO Builder - binding to superclass


  • Subject: WO Builder - binding to superclass
  • From: Gavin Eadie <email@hidden>
  • Date: Wed, 24 Aug 2005 22:33:43 -0400

WebObjects Builder Version 5.3.1 (680)


WebObjects Builder (WOB) displays the Keys and Actions available in the Java source for the component in work, in the bottom left pane of the WOB browser. In the case when the component extends WOComponent directly, eg:


   public class MyComponent extends CoreComponent { ...

"session" and "application" are available as Keys, even though their getters are not present in MyComponent.java -- I assume the inheritance from WOComponent makes these available via the session() and application() methods in WOComponent.


However, if I want all my components to have some common custom behavior, I establish an intermediate class which extends WOComponent, implements the commonality and from which my component would inherit, eg:


   public class CoreComponent extends WOComponent { ...

   public class MyComponent extends CoreComponent { ...

Now, when working on MyComponent in WOB, Session and Application may, or may not, be available in the WOB browser lower-left pane. The ARE available if CoreComponent.java is in the same framework (or application) as MyComponent.java, but NOT available if I put CoreComponent.java in a different framework, EVEN IF the "CoreComponent" framework is provided to the "MyComponent" framework in the XCode framework list. [Note that this behavior doesn't cause bindings to "application" or "session" to fail in MyComponent, the runtime does the right thing, it only means WOB isn't as helpful as I would like as I develop.]


Since in the first, simple case, the getters of WOComponent are being obtained by inspecting the contents of the JavaWebObjects framework, I would have thought that following two (and, in fact, arbitrary) levels of inheritance through ancillary frameworks should also work.


I'm wondering if WOB's failure to satisfy my expectations is a bug or a feature. The new WOB has enough other things broken that I have no way to tell. I'll file this in Radar anyway.
_______________________________________________
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
References: 
 >WOComponent api inheritance? (From: LD <email@hidden>)
 >Re: WOComponent api inheritance? (From: Chuck Hill <email@hidden>)

  • Prev by Date: Re: WOComponent's synchronizesVariablesWithBindings
  • Next by Date: WO Builder - viewing keys/actions in subclass of Application / Session
  • Previous by thread: Re: WOComponent api inheritance?
  • Next by thread: failed to open database channel with mysql
  • Index(es):
    • Date
    • Thread