• 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: URGENT : Sessions and Forms
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: URGENT : Sessions and Forms


  • Subject: RE: URGENT : Sessions and Forms
  • From: "Jonathan Fleming" <email@hidden>
  • Date: Sat, 13 Dec 2003 05:33:47 +0000

Beware of these dynamic elements, they require state to be stored on the server and so will create a session while you are using a directAction:

WOHyperlink when the action attribute is bound
WOCollapsibleComponentContent
WOTabPanel
and depending on how you bind them
WOBrowser; WOCheckBox; WORadioButton and so on
all of these and a few more can catch you out with the creation of a session if you're not carefull. Test and check that request handler 'wa' in the WebObjects Http URL does not turn to 'wo'. or simply overide Application.createSessionForRequest() and log an exception stack trace there to find the culprit... that's probably much easier


WODisplayGroup - this is not generally regarded as a dynamic element this is simply a segmented data source where you can add stuff. You normally use it in the context of a session but it does not create one, however, if you dragndrop an eoentity into wobuilder and configure the displaygroup then wo uses session.defaultEditingContext in the woo file to initialize the wodisplaygroup's datasource. So beware of this if you use a WODisplayGroup


From: Owen McKerrow <email@hidden>
To: email@hidden
CC: email@hidden
Subject: URGENT : Sessions and Forms Date: Sat, 13 Dec 2003 15:36:01 +1100

Hi All,

We'll we were given a rush project last week ( due in 2 days ) which
uses direct actions. I've just spent the last hour tracking down were a
session was being made. It appears that unless you have a form bound to
a Direct Action class, it creates a session.
However if you bind the Action class, when the form is submitted this
binding overrides which action gets called and thus always calls the
same one, even with multiple submit  = true and your different submit
buttons being bound to different actions.

Help ! How do I stop this ? I can't have the session created, but I
need to be able to have multiple submit buttons calling different
actions!

Thanks
Owen

"As of tomorrow, employees will only be able to access the building
using individual security cards. Pictures will be taken next Wednesday
employees will receive their cards in two weeks."
- "Dilbert Quotes" Winner, Fred Dales, Microsoft Corp
_______________________________________________
webobjects-deploy mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-deploy
Do not post admin requests to the list. They will be ignored.

_________________________________________________________________
It's fast, it's easy and it's free. Get MSN Messenger today! http://www.msn.co.uk/messenger
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.

  • Prev by Date: What's component unroll?
  • Next by Date: Writing EOAdaptor for EOModeler
  • Previous by thread: What's component unroll?
  • Next by thread: Re: URGENT : Sessions and Forms
  • Index(es):
    • Date
    • Thread