auth - Page 32 - Developer IT

SOAP and NHibernate Session in C#

- by Anonymous Coward

In a set of SOAP web services the user is authenticated with custom SOAP header (username/password). Each time the user call a WS the following Auth method is called to authenticate and retrieve User object from NHibernate session: [...] public Services : Base { private User user; [...] public string myWS(string username, string password) { if( Auth(username, password) ) { [...] } } } public Base : WebService { protected static ISessionFactory sesFactory; protected static ISession session; static Base { Configuration conf = new Configuration(); [...] sesFactory = conf.BuildSessionFactory(); } private bool Auth(...) { session = sesFactory.OpenSession(); MembershipUser user = null; if (UserCredentials != null && Membership.ValidateUser(username, password)) { luser = Membership.GetUser(username); } ... try { user = (User)session.Get(typeof(User), luser.ProviderUserKey.ToString()); } catch { user = null; throw new [...] } return user != null; } } When the WS work is done the session is cleaned up nicely and everything works: the WSs create, modify and change objects and Nhibernate save them in the DB. The problems come when an user (same username/password) calls the same WS at same time from different clients (machines). The state of the saved objects are inconsistent. How do I manage the session correctly to avoid this? I searched and the documentation about Session management in NHibernate is really vast. Should I Lock over user object? Should I set up a "session share" management between WS calls from same user? Should I use Transaction in some savvy way? Thanks Update1 Yes, mSession is 'session'. Update2 Even with a non-static session object the data saved in the DB are inconsistent. The pattern I use to insert/save object is the following: var return_value = [...]; try { using(ITransaction tx = session.Transaction) { tx.Begin(); MyType obj = new MyType(); user.field = user.field - obj.field; // The fields names are i.e. but this is actually what happens. session.Save(user); session.Save(obj); tx.Commit(); return_value = obj.another_field; } } catch ([...]) { // Handling exceptions... } finally { // Clean up session.Flush(); session.Close(); } return return_value; All new objects (MyType) are correctly saved but the user.field status is not as I would expect. Even obj.another_field is correct (the field is an ID with generated=on-save policy). It is like 'user.field = user.field - obj.field;' is executed more times then necessary.

Search Results

Search found 1925 results on 77 pages for 'auth'.

Page 32/77 | < Previous Page | 28 29 30 31 32 33 34 35 36 37 38 39 | Next Page >

- by Anonymous Coward

- by Prabhakar

- by Joe Mayo

- by dazzle

- by Trick

- by Joey Adams

- by tooba

- by Zayatzz

- by Robert A Henru

- by BryanWheelock

- by Trick

- by davidhayes

- by Akash

- by viatropos

- by MichaelGG

- by hora

- by thebossman

- by Pai Gaudêncio

- by f1sh

- by Darwin Tech

- by Matthew Rankin

- by David G

- by bradhe

- by Nux

- by Joshua

< Previous Page | 28 29 30 31 32 33 34 35 36 37 38 39 | Next Page >