Try using an HTTP debugger such as Fiddler2 and logging in through your browser. The tool will show you all the fields submitted, how it submitted them (i.e. POST vs GET), etc. After that, try to reproduce what your browser did in your code. Tools like that have been a lifesaver for me when trying to do things like this.
On Mon, Jul 20, 2009 at 10:23 AM, chitgoks <[email protected]> wrote: > yeah i extracted the t:formdata from the page. > > Website/Java Games: http://www.chitgoks.com > Java Casino Games: http://chitgoks.tripod.com > Photo Gallery: http://gallery.chitgoks.com > My Blogs: > http://tech.chitgoks.com > http://wuhtevah.chitgoks.com > http://disneyusa.blogspot.com > > > On Mon, Jul 20, 2009 at 10:21 PM, Thiago H. de Paula Figueiredo < > [email protected]> wrote: > > > Em Mon, 20 Jul 2009 10:58:14 -0300, chitgoks <[email protected]> > > escreveu: > > > > hi thiago > >> > > > > Hi! > > > > and i included the t:formdata parameter when submitting to the form. i > do > >> quite a lot of login simulations in sites and i have no problems when > the > >> form post url is shown. though tapestry's different since it doesnt show > >> the form post url other than the /login.loginform > >> > > > > Tapestry deals with forms a little differently when compared to other Web > > frameworks or languages. > > Just adding a t:formdata parameter with random value doesn't work: you > > should extract it from the login page. > > Form post URLs are defined by t:id of the Form component. > > > > > > -- > > Thiago H. de Paula Figueiredo > > Independent Java consultant, developer, and instructor > > http://www.arsmachina.com.br/thiago > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > >
