That's a good suggestion indeed, but right now I'm having trouble with the
most elementary stuff.
I have get myself familiar with Tapestry and then start doing real fun stuff
with it.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Jumping-to-a-new-page-tp4706239p4710938.h
Ok, now it's working as supposed to, I rewrote the grid like this:
Borrar
I put a Usuario property to map the rows at the page with the grid:
@Property
private Usuario usuario;
...to map the user, then at the page B
I guess it has a value since its shown in the browser.
I'm gonna try with
Borrar
And see what happens.
Cheers!
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Passing-parameters-from-one-page-to-another-tp4710394p4710794.html
The url is this:
http://localhost:8080/Volumetria/seguridad/borrarusuario
So, no parameters shown, right?
Cheers!
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/Passing-parameters-from-one-page-to-another-tp4710394p4710745.html
Sent from the Tapestry - User mailing list
Hi again,
According to this page http://tapestry.apache.org/page-navigation.html , you
should be able to catch the parameters sent form one page to another with an
onActivate() method. In my case I have something like this in one page:
Borrar
Everything worked as you said, t:pagelink instead of t:actionlink, and
@InjectPage instead of @Inject.
The silly part is that I had used both techniques before, but I got confused
up with the names and usages of each one.
Regarding to Thiago's questions,
"I guess you're using a structure that
Hi,
I'm having some trouble shifting from the conventional event-driven model to
the way Tapestry works.
Is there a newbie forum where I can ask the most basic questions?
Right now I'm stuck trying to jump from one page in charge to create users
to others in charge of editing and deleting them.
