sorry if my response came over in such a tone, that was not my intention 1) my initial reply was a response to this: > I thought softwares like nhibernate were supposed to solve > problems like this and many more so that we as developers can focus on > our business issues. I suppose Nhibernate has not grown up to that > level yet..
this is bashing NH for something which is not NH's fault. This doesn't mean that NH is perfect, of course 2) to use your car analogy, sure, you don't need to know who engine works. However, if you enter a sharp curve with 100 mph, you will be in trouble. Complaining later that car manufacturer didn't support this scenario doesn't really make sense. The folks here have tried to guide you (although in a rude way sometimes): your design is wrong. 'Remote entity' pattern is actually an anti-pattern, as EJB community has learnt long ago. You can fix your architecture, or you can try to workaround design flaws. People here prefer clean solutions to hacks, sometimes even without considering the context, unfortunately. NH usage is very well documented (nhforge) - this documentation is enough to use NH correctly in overall architecture, there's no need to understand the implementation. I don't consider myself an NH expert, and I have never read the NH code. You have chosen to use NH in a way which is a poor fit for any ORM, and that's why it is hard to find the guidance. You can find some implementation discussions on Ayende's blog and on NHForge. I guess that people here will be glad to help with questions like: "I am extending X implementation and don't know how to do Y. Please help". X would most likely be some of the projects mentioned earlier by Angel Java Lopez good luck On Fri, Oct 23, 2009 at 12:04 AM, SGK <[email protected]> wrote: > > > 1) > > Let me re quote your reply > > "such things > are more likely to be developed as an extension of NH, and not an > integral part of it (and indeed, it seems that there is something > similar > in unhaddins project)." > > Thats is what I came here looking for in the first place.. and not to > criticize NHibernate which is not going to solve any problem for any > one. I might have said something about it but that is not the point of > this discussion is it? > > Now let me re quote what I wrote when I posted my problem: > > "Anyone kind enough to suggest a simple workaround/solution/ > pluginable > component/ or anything which will not disrupt my app architecture and > do the thing." > > > see it looks like I am asking for an extention if someone has already > written it. > > 2) I understand I started using Nhibernate even before becoming a > hardcore expert in it and NH has got a learning curve. But the point > of posting this problem was to learn more about NH + LazyLoading + > Remoting. I am so surprised that you folks instead of guiding me to a > solution and to a way of learning more about NH innerworking, are > concentrating on what could be useless gossip. See it's not just about > me or you or NHibernate, it's about problem to a solution. All I said > was that it should'nt be mandatory for a driver to know how his car's > engine works or to know how to build one, but a driver should know how > to drive a car and how to change tiers, replace oil, water etc(which > I am ready to learn) and when any tool reaches such a level only then > it is a mature tool otherwise it is meant for experts only. > My pattern of thinking might not be very much acceptable to you, but a > good thing you could do is point me to a resource/documentation which > will help me understand NH's source code or an explanation to it's > inner design or should I google this?? > Hope I am not asking you to waste your free time... If so then please > ignore my complete post. > > > Thanks for your help, > > On Oct 23, 1:54 am, Zdeslav Vojkovic <[email protected]> > wrote: >> I believe that most people here will not agree that this is something NH >> really requires, because most of people which visit this list would not >> design their app in such way due to a number of drawbacks it involves. >> >> On the other hand, adding support for every possible way of usage >> would result in an extremely bloated tool. Therefore, such things >> are more likely to be developed as an extension of NH, and not an >> integral part of it (and indeed, it seems that there is something similar >> in unhaddins project). As in most open source communities, these >> extensions are typically developed by people who face a specific issue. >> >> Actually, I am quite surprised that you didn't already received a reply >> that you would be welcome to provide such an extension. >> >> Don't get me wrong, i really don't mean to insult, but I don't think >> that you really know how to use it. NH is a complex tool, and it has a >> learning curve like many other tools of similar complexity. It is not >> only about calling session.Get() - there is much more to it. I am also >> surprised that you haven't noticed such a glaring issue earlier. >> >> Most of us here made mistakes when we started using NH >> (or any other ORM, for that matter) and it took time until we 'got it', >> often with help of this community. It would be great if you would >> be the one to finish such an extension, and I am sure people here >> would be glad to help you. You would also learn a lot about NH in process. >> >> >> >> On Thu, Oct 22, 2009 at 10:13 PM, SGK <[email protected]> wrote: >> >> > I understand that there is no simpler solution to this problem, but I >> > wrote this post to check if any simpler solution already exists. It's >> > really upsetting when you put lots of hardwork into something and >> > finally notice a simpler solution already existed. I do not know if my >> > work deserve's to be called an architecture but I wrote this post >> > because my architecture is going to take care of such things. This >> > post is all about a problem that I am facing (which will be sorted out >> > soon) and a solution from someone who has also been into such >> > situation so that I do not need to reinvent the wheel. Probably I made >> > my problem sound very important but thats because I want nh community >> > and it's developers to notice what nh is lacking and although it has >> > everything built into it, but one small problem can disrupt the very >> > purpose of projects like NHibernate. After all I am not supposed to >> > know how Nhibernate works, I should just know how to use it. Hope you >> > agree!! >> > Thanks anyways >> >> > On Oct 20, 4:22 am, José F. Romaniello <[email protected]> >> > wrote: >> >> "Something that doesn't take care of such things doesn't deserve to be >> >> called architecture." >> >> >> You have a "jenga"/"yenga" architecture, so you will not get a >> >> simpler/pluggable/[put pretty words here] >> >> solution.http://es.wikipedia.org/wiki/Jenga >> >> >> <http://es.wikipedia.org/wiki/Jenga>I don't know if this game exists in >> >> other countries.. but the gif is very explanatory. >> >> >> 2009/10/19 SGK <[email protected]> >> >> >> > I am at a stage in my project where I cannot chnge to another ORM. My >> >> > application looks like : >> >> >> > 1) Windows Forms - Presentation Layer >> >> > 2) BusinessObjects-Entities/Custom,Generic- >> >> > BindableAndFilterableCollections/EntityMappings -Serializable objects >> >> > 3) Server - DataRepository/UserAuthentication etc uses NHibernate - >> >> > MarshalByRef objects >> >> >> > Business objects are transfered from server to windows client via .Net >> >> > Remoting 2.0. Many objects have properties that are associated to >> >> > entities which are very large like images and documents. >> >> >> > LazyLoading is very compulsary otherwise it will seriously degrade my >> >> > application performance. >> >> >> > Anyone kind enough to suggest a simple workaround/solution/pluginable >> >> > component/ or anything which will not disrupt my app architecture and >> >> > do the thing. >> >> >> > Thanks in advance.. >> >> > Regards, >> >> > SGK- Hide quoted text - >> >> >> - Show quoted text -- Hide quoted text - >> >> - Show quoted text - > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
