So you would bind every field in the control from the client? Keep in mind that this control would be accessed from multiple applications and the data would not change for the different applications. It is standard data not specific to any one application. It would seem to me to add quite a bit of duplication to bind the control from every client if the display data will be basically the same. It does have an input form too.
On Nov 3, 9:41 am, Jason Meckley <[email protected]> wrote: > I wouldn't put a dependency on the control to query hibernate. rather > push data to the server control and have the control work with the > data. the burden of retrieving the data is left to the application. > > On Nov 3, 9:25 am, suedeuno <[email protected]> wrote: > > > > > I'm looking at adding NHibernate to a server control and the > > encapsulated business logic and data code. What would be the preferred > > way to wire up NH to the database if the server control's parent > > container doesn't use NH yet?- 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 -~----------~----~----~----~------~----~------~--~---
