+1. I don't have any problem with NHibernate. I'm just asking the question to the people who made NH happens and expected an answer.
"> Still... I don't see any problems with all those sessions for each > service as it needs to protect the data it is responsible for." Well that's quite right from a pure technical point of view, >From a business point of view, I have a service and I must ensure that the behavior is safe, not only regarding the surface. What happens really is that I have object loaded in one session, graph hydrated within another, and perhaps saved in another. Because of a business behavior, inducted by many services. At the end, my biggest risk is that if I want a global validation on 500 objects (let's say a portfolio priced position); I will spend time trying to attach,etc,etc.... Because each object and associated object in the graph will be the result of the use of many entities used through many sessions. My real question finally is : Is an ORM appropriate ? But that are just questions and considerations, Sorry for wasting your time; Selon Ramon Smits <[email protected]>: > > > So far I can see you have multiple services that can call each other > in random order and that is on design. > > AFAIK each service is message based and are stand alone applications > (either own process or own application domain). As each service will > open its own connection to its (or the which I guess in your > description...) database. > > If you have a service that is currently chatty because it needs to > fetch details for an object array and be processed for a request / > response model then I indeed understand that you want to remove chatty > overhead as the obvious guess here is that your interfaces/contract > need to be renewed to allow multiple request in one round-trip be > processed OR don't use a request/response model. > > My guess is that your domain objects somehow have state that can > affect other domain objects. Like bank accounts where ammounts flow > between them and that you somehow need to read such data in the same > transaction over multiple request thus having a session over a service > thus a statefull service. > > Still... I don't see any problems with all those sessions for each > service as it needs to protect the data it is responsible for. > > I think you are seeing problems that are not there or you are > experiencing problems not caused by NHibernate. > > Ramon > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nhusers?hl=en -~----------~----~----~----~------~----~------~--~---
