Paul Mansfield a �crit : > I got an answer, but I think I didn't explain myself properly (I > realise getService is a function in the same file), what I meant was > where does getService get the service from?
>From the property file, look jetspeedsecurity.properties, it's to define which >service / which object representing a user you're really going to use. This is the way turbine framework works. > (getService -> TurbineAuthentication -> JetspeedUserManagement -> > getService -> getUser -> TurbineUserManagement-> > TurbineUserPeer.doSelectusers) >I've achieved what I want to, i.e. tapping in to the login scheme, but >I'd still like to understand the program flow... arcane as it is. I wanted too, took some time too ! ><rant>Seems to me that it'd be hard to make it more complicated, >considering all it really does it check user/pass against the DB, then >populate a User object and store it in the session. I counted at least >12 levels of function calling, easy! I agree on that, login part on jetspeed is a bit complicated, and I don't get why the action JLoginUser doesn't only call the authentication method which can do the same job (I'd say for historical reason as js 1.3 didn't use all the capabilities of Turbine, but not sure). >And then there's the matter of the code in the package >com.workingdogs.village which just magically appears and seems >unreferenced in any of the main jetspeed documentation! Village is used by Torque which is used by Turbine / Jetspeed to make the SQL statements :) Talking about integration ? ;) HTH, Aurelien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
