• 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
Re: woswitchcomponents
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: woswitchcomponents


  • Subject: Re: woswitchcomponents
  • From: Ramsey Gurley <email@hidden>
  • Date: Fri, 08 Jul 2011 11:53:20 -0700


On Jul 8, 2011, at 7:17 AM, Michael Gargano wrote:

Hey Ramsey,

So, this really helped me out.  I knew I was being stupid.  I didn't know you had to pass the WOComponentContent into the WOSwitchComponent.


Don't sweat it.  Even Chuck admitted to finding woswitch and wocomponentcontent confusing (^_^)  And he's always right.  So they are confusing.  I found the diagram from the D2W guide extremely helpful in understanding them though.

http://developer.apple.com/legacy/mac/library/#documentation/WebObjects/Developing_With_D2W/Architecture/Architecture.html#//apple_ref/doc/uid/TP30001015-DontLinkChapterID_2-TPXREF106

Edit page component organization

Look at figure 2-1.  Notice how the yellow page component is the root element.  The PageWrapper is like a picture frame, and the WOComponentContent is the hole in it.  Its parent() is the yellow page.  In fact, all the grey boxes in that diagram are WOSwitchComponents.  MenuHeader is a 'regular' wocomponent and it is placed in the PageWrapper by hard coding the name in the PageWrapper.wod.  Switches on the other hand are placed in the page by dynamically setting the WOComponentName binding at runtime.

Otherwise, switches work the same as regular wocomponents.  Passing a binding to a switch passes the binding directly thru to the named component at runtime.  If a switch component has component content, then whatever you wrap the switch around shows through the hole.


Using ERXD2WList, however, I still get this output in the log

Jul 08 10:11:26 eGM[60000] DEBUG NSLog (SelectUser) - Using JDBCPlugIn 'PostgresqlPlugIn' for JDBCAdaptor@1983923753
Jul 08 10:11:26 eGM[60000] DEBUG NSLog (SelectUser) -  === Begin Internal Transaction
Jul 08 10:11:26 eGM[60000] DEBUG NSLog (SelectUser) -  evaluateExpression: <the correct sql>
Jul 08 10:11:26 eGM[60000] DEBUG NSLog (SelectUser) - 9 row(s) processed
Jul 08 10:11:26 eGM[60000] DEBUG NSLog (SelectUser) -  === Commit Internal Transaction
Jul 08 10:11:26 eGM[60000] DEBUG NSLog (SelectUser) (null) - Using JDBCPlugIn 'PostgresqlPlugIn' for JDBCAdaptor@724020419
Jul 08 10:11:26 eGM[60000] DEBUG NSLog (SelectUser) (null) -  === Begin Internal Transaction
Jul 08 10:11:26 eGM[60000] DEBUG NSLog (SelectUser) (null) -  evaluateExpression: <the correct sql>
Jul 08 10:11:26 eGM[60000] DEBUG NSLog (SelectUser) (null) - 9 row(s) processed
processed

It looks like each null is a nested configuration name. If I had to guess, I would say you have a rule that uses an embedded component like ERDList or ERDEditRelationship on a self referential relationship in your main list entity.  Go through your displayKeys binding on your ERXD2WList and remove them one at a time. See if the problem goes away on a specific key.

Ramsey

 _______________________________________________
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: 
 >woswitchcomponents (From: Michael Gargano <email@hidden>)
 >Re: woswitchcomponents (From: Ramsey Gurley <email@hidden>)
 >Re: woswitchcomponents (From: Michael Gargano <email@hidden>)

  • Prev by Date: Re: Attribute being read as NSData instead of String
  • Next by Date: ERRest and Faulting control
  • Previous by thread: Re: woswitchcomponents
  • Next by thread: Languages for WOResourceManager
  • Index(es):
    • Date
    • Thread