I think I found one solution, what I did was to add the normal textfield
an AjaxFormComponentUpdatingBehavior associated to the onchange event. In the
code of onUpdate() I add an AttributeModifier that replaces the value of the
value attribute, then I replace the textfield in the form and use
hmmm
it doesnt work because the url is cached by the autocomplete script. we need
to think of another way.
-igor
On 3/27/07, Jaime De La Jara [EMAIL PROTECTED] wrote:
Ok, I understand, now I'm including a striped down code version of the
problem. It contains an ant build file whose
I'm not sure if I fully understand it, but maybe if the first textfield sent
its value and a serverside reference hold it until the autocomplete field
received the input and used this value?.
Jaime.
Igor Vaynberg [EMAIL PROTECTED] wrote: hmmm
it doesnt work because the url is cached by the
On 3/26/07, Jaime De La Jara [EMAIL PROTECTED] wrote:
Hi, I have a form with some fields and a AutoCompleteTextField that is
working nice, however now I need to retrieve the value of a TextField from
this AutoCompleteTextField so I can restrict the values shown for
autocompletion. Is this
Basically what I need is to narrow the possible choices of the autocomplete
field, depending on the value the user entered in the other field (which is a
normal field).
This is a user requirement to simplify their data entry, in this case the
normal field is an invoice number and the
ok, this is a bit tricky but is def doable. i dont think this is a very
common usecase, so i dont think we will create all the factories/etc for you
to be able to do this out of the box because in most cases it will just be
api bloat.
that said, although not trivial it is still def very possible
Absolutely !, thanks a lot Igor, I'll try it right now. I agree that is an
uncommon use case and it doesn't deserve an api change and a custom solution is
what is needed.
Jaime.
Igor Vaynberg [EMAIL PROTECTED] wrote: ok, this is a bit tricky but is def
doable. i dont think this is a very
Igor, unfortunely I haven't been able to use the solution proposed. I copied
and pasted the code for the getCallbackUrl method but it had a minor typo, but
after I corrected and reloaded the page with the autocomplete field the browser
(IE) throws a javascript error. The following works (using
Sorry in the last post I had a type instead of limiter=1415 it should be
numFact=1415, I'm using numFact as the request variable.
Jaime De La Jara [EMAIL PROTECTED] wrote: Igor, unfortunely I haven't been
able to use the solution proposed. I copied and pasted the code for the
getCallbackUrl
your textfield doesnt have an id attribute defined, so
docuement.getelemetnbyid is not finding it
-igor
On 3/26/07, Jaime De La Jara [EMAIL PROTECTED] wrote:
Sorry in the last post I had a type instead of limiter=1415 it should be
numFact=1415, I'm using numFact as the request variable.
No, it has one (returned by getMarkupId() and generated by
setOutputMarkup(true)).
This is the generated html :
input value= maxlength=16 type=text class=tipo size=12
name=numero id=numero
scriptdocument.getElementById('numero').focus();/script
The strange thing is that if I set the
if you feel like creating a quickstart i can take a look at that
-igor
On 3/26/07, Jaime De La Jara [EMAIL PROTECTED] wrote:
No, it has one (returned by getMarkupId() and generated by
setOutputMarkup(true)).
This is the generated html :
input value= maxlength=16 type=text class=tipo
the reason i wanted a quickstart is so that i can see the problem in
runtime. what you have sent over does not compile when i drop it into
quickstart as it contains your app-specific classes/daos/validators which
you have not included.
-igor
On 3/26/07, Jaime De La Jara [EMAIL PROTECTED]
13 matches
Mail list logo
