It sounds like what you need is to implement the authentication as a hivemind service which can be injected whereever you need it.
Better yet: in both cases the username/password fields, submit button (link?) and service could all be dropped into a custom component that you could reuse anywhere you wanted. Or... You could also just get an instance of the login page from the request cycle and call the login method from there, but that sounds, um, less than ideal. -Mike On 3/14/06, Apache <[EMAIL PROTECTED]> wrote: > I have a Login page with a username/password field > and a login method. > > I also added a login box with the a username/password field. > > The logic of processing the login is within the login page class. > > I want to the login page also to process the login request that comes from a > login box as I do not want to copy and paste the same code within the login > component code. > > Is the any way to make a form action to direct to a page method rather than > to direct to a method within the same component class ? > > > -------------------- m2f -------------------- > > Sent from www.TapestryForums.com > > Read this topic online here: <<topic_link>> > > http://www.tapestryforums.com/viewtopic.php?p=14550#14550 > > -------------------- m2f -------------------- > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
