Hi Frederic, seriously, I cannot really follow your problem. Why would you need to instantiate a context within the login phase in the first place? The LoginAction is specifically desifned not to take a context, because of authorized PullTools, which have to be put inside the context afterwards. Can't you handle your access to your context within your first screen?
You said you disabled *almost* all your own services and pull tools. Which one
did you leave in and why. Can you post the source code.
You wrote you use your own LoginUser.java. Could you please send the source
code of that class
Kind regards
Juergen
Am Donnerstag, 20. Juli 2006 14:32 schrieb Frédéric KERNEUZET:
> Hi,
>
>
>
> After trying to disable almost all my "own" services declared in the
> TurbineResource.properties, connection has not been faster at all.
>
> I've decided to add some log in Turbine classes that are called during the
> user login.
>
>
>
> So, i describe a bit more the "calling schema" :
>
> In my LoginUser.java, I call this => context =
> TurbineVelocity.getContext(data);
>
>
>
> Then, this getContext() method calls the getService() one (always in
> TurbineVelocity).
>
> Then, it calls getInstance() method of TurbineServices class, and it's here
> that something looks strange :
>
> this getInstance() method is called 1663 times for only one user login into
> the application !
>
>
>
>
>
> After this, the LoginUser class redirect the user to the main page of
> application, and at this moment too (between my two classes !) the
> getInstance() method is called 7344 times !
>
>
>
> Does someone can tell me more about this method ? What kind of objects is
> it instancing ?
>
>
>
>
>
>
>
> Frederic
>
> !EXCUBATOR:1,44bfa6bf43383846368294!
--
Mit freundlichen Grüßen
Jürgen Hoffmann
Auf der Beune 83-85
64839 Münster
HRB33271
tel: +49 (0)6071 - 92160 (09:00 - 18:00 Uhr)
0700 byteaction / 0700 29832284 (24x7)
fax: +49 (0)6071 - 921620
0700 29832284
email: [EMAIL PROTECTED]
web: www.byteaction.de
***************************************************************************
This Communication is intended only for the party to whom it is
addresses, and may contain information which is privileged or
confidential. Any other delivery, distribution, copying or disclosure is
strictly prohibited and is not a waiver of privilege or confidentiality.
If you have received this telecommunication in error, please notify the
sender immediately by returning this electronic mail and destroy the
message
**************************************************************************
pgpXbKtmHb4ka.pgp
Description: PGP signature
