[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [wsrp] Supplying additional parameters to render URLs from theclient side
Richard Jacob wrote: > :-) > and here we go with form mothod=GET ;-) Yes, one more time :) There are too many usages for this. > Currently its impossible in 2.0. The only thing we need as I suggested to > add a form params structure to MarkupParams. Here is a simple use case that Mike Caffyn brought up offline. Use case: Auto-Complete, typing into an input field calls via ajax to give a list of items that start with what has been entered so far. For web developers, this is a very simple use case. Has any one explored updating the navigationalState via some producer-supplied JavaScript? Regards, Subbu > > Mit freundlichen Gruessen / best regards, > > Richard Jacob > ______________________________________________________ > IBM Lab Boeblingen, Germany > Dept.8288, WebSphere Portal Server Development > WSRP Technical Lead > WSRP Standardization > Phone: ++49 7031 16-3469 - Fax: ++49 7031 16-4888 > Email: mailto:richard.jacob@de.ibm.com > > > > Subbu Allamaraju > <subbu@bea.com> > To > 06/29/06 11:44 PM wsrp <wsrp@lists.oasis-open.org> > cc > > Subject > [wsrp] Supplying additional > parameters to render URLs from the > client side > > > > > > > > > > > In WSRP 1.0/2.0, portlets can use forms with action URLs to let > users/browsers supply new parameters to portlets. How would one do that > with render URLs? > > Here is a use case. > > A portlet generates a form containing a dropdown for zip codes. The > portlet would like to use some JavaScript to supply the selected zip > code to a render URL to render some relevant markup. > > How would the portlet solve this use case? > > Regards, > Subbu > _______________________________________________________________________ > Notice: This email message, together with any attachments, may contain > information of BEA Systems, Inc., its subsidiaries and affiliated > entities, that may be confidential, proprietary, copyrighted and/or > legally privileged, and is intended solely for the use of the individual > or entity named in this message. If you are not the intended recipient, > and have received this message in error, please immediately return this > by email and then delete it. > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. You may a link to this group and all your TCs in > OASIS > at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > > > _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]