Tanks a lot. That really helps.
regards, Robert
Jesse Kuhnert schrieb:
Not anymore they don't.
On 11/9/06, Robert Binna <[EMAIL PROTECTED]> wrote:
Hi.
Thanks, but I know about this method getClientId(), but each component
looses its client id information after rendering is finished and so t
Not anymore they don't.
On 11/9/06, Robert Binna <[EMAIL PROTECTED]> wrote:
Hi.
Thanks, but I know about this method getClientId(), but each component
looses its client id information after rendering is finished and so the
parent component will never know.
regards
Robert
Roberto Ram
Hi.
Thanks, but I know about this method getClientId(), but each component
looses its client id information after rendering is finished and so the
parent component will never know.
regards
Robert
Roberto Ramírez Vique schrieb:
Hello,
I'm not sure because I've never used it ... but
Hello,
I'm not sure because I've never used it ... but I think tapestry 4.1 (I'm
using 4.0 because 4.1 is not stable) let you know which is the clientId for
a component:
http://tapestry.apache.org/tapestry4.1/tapestry-framework/apidocs/org/apache/tapestry/IComponent.html#getClientId()
I don't k
Hi
You are right.
There seems to be situation when you get the right id, but I just came
across one where this is not the case. After that I take a short
look at the tapestry code and I wonder why my sugested solution ever worked.
My Question is, can anyone give me a hint how to implement dojo
I'm using this method (also using tap 4.0.2), but seems to be not working.
For me it gets the next supposed "id", I mean, if I have a component named
legalId the id in the page is legalId but when I executed the method I get
: legalId_0 ... probably I make any mistake...
thanks,
robert
yes i did use idPath for the hidden field.
but i'm using tapestry 4.0.2 - could that be the reason i'm seeing different
results than you are?
On 11/5/06, Patrick Moore <[EMAIL PROTECTED]> wrote:
did you assign the hidden field's id using idPath?
Also I am using the 4.1.1 SVN build.
I am havi
did you assign the hidden field's id using idPath?
Also I am using the 4.1.1 SVN build.
I am having some success with this method (borrowed from another's
email) in finding the unique ids but I haven't throughly tested it
yet:
public String getUniqueId(AbstractComponent component) {
retu
Pat, I tried an example similar to the one you've mentioned above. My
observation however is that the output will be something like this:
i.e. in the second instance of input type="hidden"
the id="my.path.foo" and *NOT* id="my.path.foo_0" as you had suggested.
Any comments?
Patrick Mo
Whenever you're not sure about something there are always branchesVery
cheap and easy to use and allows for easier collaboration on code.
On 11/4/06, andyhot <[EMAIL PROTECTED]> wrote:
Patrick Moore wrote:
> I am hardly close to being an expert ... :-) So I always qualify what
> I am saying
Patrick Moore wrote:
> I am hardly close to being an expert ... :-) So I always qualify what
> I am saying because some of the times I was just making a mistake in
> my understanding. For me clientId was not working if I had a component
> nested in a @For loop.
clientId also didn't work for me...
I am hardly close to being an expert ... :-) So I always qualify what
I am saying because some of the times I was just making a mistake in
my understanding. For me clientId was not working if I had a component
nested in a @For loop.
On 11/3/06, Roberto Ramírez Vique <[EMAIL PROTECTED]> wrote:
He
Hello Jesse,
thanks for your response, but I'm afraid my problem was that I'm using
tapestry 4.0 (clientId is public accessible in 4.0, no?). (sorry for not
warning you before).
Well, As I explained before I've tried using the clientId, always inside a
For component. In this For loop I have a co
Hello Pat!
first of all, thanks you for your comments !
Well, I'm really not an expert developer on tapestry, and for sure you have
tried this. But the div tag shouldn't be something like:
I tell you this because to me in this way is working .. tapestry uses the
clientId for me.
Btw, I'm using
I just realized that what I said was not completely clear. if you have this:
with mycomponent template like this:
you would end up with generated out put like this:
so the second instance of the div tag would refer to the first
instance of the hidden field, not the second like i
However see :
http://issues.apache.org/jira/browse/TAPESTRY-1131
use clientId does not always generate a unique Id on a page level
basis. If another component tried to access the first component's
clientId, the result returned would be the first id not the correct
uniquified value.
-Pat
On 1
IComponent.getClientId() or IComponent.getId()
getClientId() is only relevant "in context"...ie calling it inside a For
loop would be good.
On 11/2/06, Roberto Ramírez Vique <[EMAIL PROTECTED]> wrote:
Hello!
I want to use something that I supose tapestry already made for me.
I'll try to expl
17 matches
Mail list logo
