35 messages in net.java.dev.ajax.devRe: component.getClientId only unique...| From | Sent On | Attachments |
|---|---|---|
| Gregory Murray | Apr 10, 2007 10:44 pm | |
| Norbert Truchsess | Apr 11, 2007 12:03 am | |
| Norbert Truchsess | Apr 11, 2007 12:05 am | |
| Gregory Murray | Apr 11, 2007 12:26 am | |
| Gregory Murray | Apr 11, 2007 12:48 am | |
| Craig McClanahan | Apr 11, 2007 12:58 am | |
| Craig McClanahan | Apr 11, 2007 1:19 am | |
| Ed Burns | Apr 11, 2007 6:32 pm | |
| Ed Burns | Apr 11, 2007 7:52 pm | |
| Craig McClanahan | Apr 11, 2007 7:53 pm | |
| Ed Burns | Apr 11, 2007 8:28 pm | |
| Craig McClanahan | Apr 11, 2007 9:41 pm | |
| Craig McClanahan | Apr 11, 2007 9:44 pm | |
| Craig McClanahan | Apr 11, 2007 9:51 pm | |
| Norbert Truchsess | Apr 11, 2007 10:08 pm | |
| Norbert Truchsess | Apr 11, 2007 10:15 pm | |
| Craig McClanahan | Apr 12, 2007 12:19 am | |
| Norbert Truchsess | Apr 12, 2007 1:19 pm | |
| Norbert Truchsess | Apr 12, 2007 2:54 pm | |
| Norbert Truchsess | Apr 12, 2007 3:43 pm | |
| Gregory Murray | Apr 14, 2007 4:56 pm | |
| Gregory Murray | Apr 14, 2007 5:03 pm | |
| Craig McClanahan | Apr 14, 2007 5:06 pm | |
| Ed Burns | Apr 16, 2007 8:18 am | |
| Gregory Murray | Apr 16, 2007 8:32 am | |
| Ed Burns | Apr 16, 2007 8:55 am | |
| Gregory Murray | Apr 16, 2007 9:09 am | |
| Norb...@t-online.de | Apr 16, 2007 9:21 am | |
| Ed Burns | Apr 17, 2007 9:59 am | |
| Craig McClanahan | Apr 17, 2007 10:23 am | |
| Norbert Truchsess | Apr 17, 2007 1:05 pm | |
| Craig McClanahan | Apr 17, 2007 3:30 pm | |
| Gregory Murray | Apr 18, 2007 1:54 am | |
| Norb...@t-online.de | Apr 18, 2007 4:44 am | |
| Norbert Truchsess | Apr 19, 2007 1:40 pm |
| Subject: | Re: component.getClientId only unique to a given page. | |
|---|---|---|
| From: | Craig McClanahan (Crai...@Sun.COM) | |
| Date: | Apr 14, 2007 5:06:08 pm | |
| List: | net.java.dev.ajax.dev | |
Gregory Murray wrote:
On Apr 11, 2007, at 9:41 PM, Craig McClanahan wrote:
Ed Burns wrote:
On Wed, 11 Apr 2007 19:53:46 -0700, Craig McClanahan <Crai...@Sun.COM> said:
CM> Ed Burns wrote:
On Tue, 10 Apr 2007 22:45:16 -0700, Gregory Murray <Greg...@Sun.COM> said:
EB> When using jMaki with JSF, IF there is no "service" attribute but there EB> is a "value" attribute on the a:widget tag, AND the value of the "value" EB> attribute is an EL ValueExpression, THEN there should be no service EB> handed to the widget. Rather, the system should make it so that the EB> postback happens to the regular JSF page.
CM> Ed, does this really cover all the use cases?
CM> Consider an autocomplete text field ... the fact that I might use a CM> value binding expression on the "value" property is orthogonal to the CM> fact that the widget *also* needs some sort of service callback to get CM> the set of valid options as the user types keystrokes. If I am reading CM> your proposed functionality description right, it would seem to prohibit CM> this kind of combination.
Yes. I see. You need the ValueExpression when you render the page, and when the form is actually submitted (via Ajax or otherwise). You need the service only when doing autocomplete *before* the form is submitted. However, as I stated my above rule (which is the same rule for this I've been stating for at least a year) I'm addressing the case where *there is no service attribute* and there is a value attribute. Another clause on the rule is necessary to handle your case.
Let me restate my rule to consider your case.
if (using jMaki with JSF) {
if (no service attribute on tag) {
I am not omfortable with this restriction.
For a JSF based autocomplete component, the URL that would be specified is normally an implementation detail of the component, not something the application developer should care about. Consider the way we implemented this in the Blueprints Auto Complete Text Field ... the renderer creates the callback URL (the moral equivalent of the "service" property for jMaki) that maps to an internal (to the component) class that actually does the lookups. The fact that the component-provided code delegates to application-provided code via a method binding expression is, again, an implementation detail. The key point is that the *component* should own setting this URL, not the *developer*.
This is what jMaki was doing in the other runtime and now this is broken. I've started a new thread on this and I need to have the new runtime support this for the time being as it is a regression and I would like to come to some form of agreement soon.
Any chance we could have a con call on this the coming week?
I'm available most anytime on Monday, or anytime Tuesday morning (both Pacific time). A conversation on this topic would be very useful -- and we'll need to expand it into the semantics of comboboxes too -- see my other response :-).