Hmmm... org.apache.turbine.modules is hardcoded. It will be added to the search path anyway. That is why it found the LoginUser action. It still executed the version in org.apache.turbine.modules.actions.
> -----Original Message----- > From: Eigen Technology Pty Ltd [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 03, 2003 7:40 PM > To: [EMAIL PROTECTED] > Subject: RE: setAction > > > My TR.properties does not have org.apache.turbine.modules > inlcuded in it. I believe this file is generated by Turbine > during the initial build, is it not? > > The puzzling thing is, my login actions works fine even > though this LoginUser.java / LoginUser.class file do not > exist. What is my login using for authentication then? FluxLogin? > > michael > > > > > > org.apache.turbine.modules should be included in the list. That is > > the package where LoginUser resides. > > > > If you want to change the login behavior, you will need to > create your > > own implementation. Don't both inheriting from the existing > > LoginUser. You might want to simply copy it and then modify it to > > suite your needs. Your version should go in > > com.mycompany.eigen.modules.actions. > > > > Even if you do create your own version of LoginUser, make sure that > > you still include org.apache.turbine.modules. There are > other actions > > which are still used. > > > >> -----Original Message----- > >> From: Eigen Technology Pty Ltd [mailto:[EMAIL PROTECTED]] > >> Sent: Friday, January 03, 2003 5:16 PM > >> To: [EMAIL PROTECTED] > >> Subject: RE: setAction > >> > >> > >> Thanks Quinton, > >> > >> I wanted to modify the LoginUser to change the login > behaviour. Your > >> explanation helps alot. But I could not seem to find the > >> LoginUser.java file anywhere in the directories as given in the > >> TR.properties. > >> > >> module.packages=com.mycompany.eigen.modules,org.apache.turbine > >> .flux.modules > >> > >> [root@linux actions]# pwd > >> /usr/local/tdk/webapps/eigen/WEB-INF/src/java/org/apache/turbi > >> ne/flux/modules/actions > >> [root@linux actions]# tree > >> . > >> |-- FluxAction.java > >> |-- FluxLogin.java > >> |-- FluxLogout.java > >> |-- group > >> | `-- FluxGroupAction.java > >> |-- permission > >> | `-- FluxPermissionAction.java > >> |-- role > >> | `-- FluxRoleAction.java > >> `-- user > >> `-- FluxUserAction.java > >> > >> > >> [root@linux modules]# pwd > >> /usr/local/tdk/webapps/eigen/WEB-INF/src/java/org/mycompany/ei > >> gen/modules > >> [root@linux modules]# tree > >> . > >> |-- actions > >> | |-- CustomerSQL.java > >> | |-- InvoiceSQL.java > >> | |-- SQL.java > >> | |-- SecureAction.java > >> | |-- TemplatePageAttributesEx.java > >> | `-- Upload.java > >> > >> > >> Any idea where that file is to be found? > >> > >> thankx > >> michael > >> > >> > >> > >> > >> > >> > The first thing that I would like to point out is that basic > >> > difference of leaving off the ".setPage()" on the $link context > >> object. I belive that it will use template.homepage from your > >> TR.props file in this case. I am not certain of this > because I have > >> not really looked at the code. It seems like I ran across this a > >> while > >> > back.... > >> > > >> > In your first example, the action that you are calling is > >> LoginUser. > >> > Turbine will execute the doPerform() method of the > >> LoginUser class as > >> > a result. It will use the setting of module.packages from > >> TR.props to > >> > determine which packages to look in. It will take each entry > >> (multiple entries are comma seperated), and add ".actions" > to the end > >> > of the package name. It then adds the class name to > arrive at the > >> fully qualified class name. Example: > >> > > >> > > >> > module.packages=com.mycompany.sampleapp.modules,org.apache.turbine.mo > >> d > >> > ul > >> > es > >> > > >> > Turbine will attempt to load > >> > com.mycompany.sampleapp.modules.actions.LoginUser first. If that > >> fails, it will attempt to load > >> > org.apache.turbine.modules.actions.LoginUser. > >> > > >> > > >> > > >> > There is a LoginUser action that come with Turbine. If you > >> check your > >> > module.packages setting, you will see where it is trying to look. > >> Turbine comes with a default LoginUser action. You might want to > >> make > >> > sure that you have org.apache.turbine.modules listed on your > >> > module.packages setting. > >> > > >> > I am not sure about the SQL action. Is this is a how-to > or similar > >> document? > >> > > >> > > >> >> -----Original Message----- > >> >> From: Eigen Technology Pty Ltd > >> >> [mailto:[EMAIL PROTECTED]] > >> Sent: Wednesday, January 01, 2003 12:26 AM > >> >> To: [EMAIL PROTECTED] > >> >> Subject: setAction > >> >> > >> >> > >> >> what is the difference between: > >> >> > >> >> <form method="post" action="$link.setAction("LoginUser")"> > >> >> > >> >> and > >> >> > >> >> <form method="post" > >> >> action="$link.setPage("Index.vm").setAction("SQL")"> > >> >> > >> >> where the setPage is not found in the first Form? I found > >> SQL.java in > >> >> the directory tree, but not LoginUser.java > >> >> > >> >> help appreciated. > >> >> michael > >> >> > >> >> > >> >> > >> >> -- > >> >> To unsubscribe, e-mail: > >> >> <mailto:turbine-user-> [EMAIL PROTECTED]> For > >> >> additional commands, > >> >> e-mail: <mailto:[EMAIL PROTECTED]> > >> >> > >> >> > >> > >> > >> > >> > >> -- > >> To unsubscribe, e-mail: > >> <mailto:turbine-user-> [EMAIL PROTECTED]> > >> For > >> additional commands, > >> e-mail: <mailto:[EMAIL PROTECTED]> > >> > >> > > > > > > -- > > To unsubscribe, e-mail: > > <mailto:[EMAIL PROTECTED]> For additional > > commands, e-mail: <mailto:[EMAIL PROTECTED]> > > > > > -- > To unsubscribe, e-mail: > <mailto:turbine-user-> [EMAIL PROTECTED]> > For > additional commands, > e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
