> Hi, > > Instead of using different frameworks and wiring > them manually, using a > framework like rumba should make things easier for > the production. Reminded > me ruby a little bit. Nice work!
Thanx a lot :). Rumba tries to combine best of both worlds - being scalable up to huge projects from Java and productivity from Rails. > > Haven't read the thread in detail but have a > question, how is Rumba's > support for lazy objects? How does it take care of > the lazy initialization > exceptions? We always ensure that all the persistent objects are always associated with active Hibernate Session. If so , no LazyInitializationException is possible. Effectively this is a Session-per-Request pattern from "Hibernate in Action". Both page rendering and postback processing work within the scope of active Session. Thus, any Rumba action can work with lazy objects because there's active Session running in the background. Rumba does not store object instances between request. Instead it always reloads persistent objects using the active Session. A developer can get LazyInitializationException only if he/she keeps a reference to the persistent object, for instance storing it in HTTP session. We have provided a simple and convenient abstraction - ObjectProxy - that may be used to have a persistent object reference that is always valid. Regards, Alexey __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
