• 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
[Related To] AjaxUpdateLink's action not getting called
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Related To] AjaxUpdateLink's action not getting called


  • Subject: [Related To] AjaxUpdateLink's action not getting called
  • From: Daniel Beatty <email@hidden>
  • Date: Thu, 19 Mar 2009 21:22:28 -0500

Greetings all,
I have a similar question Ricardo's. If I have an update container in one WO Component can be referred by another WO Component nested in the first?


Example Let Component X be loosely defined as follows:
<wo:AjaxUpdateContainer id="FooX">
	<WO:SomeOtherComponent idToCall="FooX"/>
</wo:AjaxUpdateContainer>

and Component "SomeOtherComponent" be defined:

<wo:AjaxUpdateLink action="$doSomething" string="Do it" updateContainerID="$idToCall" />

Would that be a legal use of the AJAXUpdateContainer?

Could use some advise on this matter.

Thank you,
Dan Beatty, M.S. CS (B.S. EECS)
Ph.D. Student
Texas Tech University
email@hidden
http://venus.cs.ttu.edu/~dabeatty


On Mar 10, 2009, at 6:20 PM, Ricardo J. Parada wrote:


Yep I agree. I found that to be a nice feature. Not having to worry about giving your input elements a unique ID is nice. Specially if you are working on a reusable component that may be used multiple times on the page. In that case it's even more useful and elegant.


I also found out that any text fields wrapped I don't need to worry about catching the return key. In other words, if you press the return or enter key in any one of these text fields then the action associated with the AjaxObserveField gets called and the update container is updated.

I assume this is true for other input elements that get keyboard input focus.

:-)


On Mar 10, 2009, at 6:52 PM, Henrique Gomes wrote:


On Mar 10, 2009, at 5:48 PM, Ricardo J. Parada wrote:

From the javadoc:

If you do NOT specify an observeFieldID, all of the form fields contained within this component will be observed for changes instead.

I stand corrected. Might find that useful if it really works, or the bug gets fixed.


Henrique Gomes


_______________________________________________ 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

_______________________________________________ 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

_______________________________________________ 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
  • Follow-Ups:
    • Re: [Related To] AjaxUpdateLink's action not getting called
      • From: Mike Schrag <email@hidden>
References: 
 >AjaxUpdateLink's action not getting called (From: "Ricardo J. Parada" <email@hidden>)
 >Re: AjaxUpdateLink's action not getting called (From: Henrique Gomes <email@hidden>)
 >Re: AjaxUpdateLink's action not getting called (From: "Ricardo J. Parada" <email@hidden>)
 >Re: AjaxUpdateLink's action not getting called (From: Henrique Gomes <email@hidden>)
 >Re: AjaxUpdateLink's action not getting called (From: "Ricardo J. Parada" <email@hidden>)

  • Prev by Date: Re: [OT] A good free profiler
  • Next by Date: Re: [Related To] AjaxUpdateLink's action not getting called
  • Previous by thread: Re: AjaxUpdateLink's action not getting called
  • Next by thread: Re: [Related To] AjaxUpdateLink's action not getting called
  • Index(es):
    • Date
    • Thread