Sorry, pressed the wrong button - "Send" instead of "Save" :)
We will provide API for developers to support custom type passing via a request as a string. We already have to do it for JodaTime ourselves. I expect this feature in one of the next builds. Werner, Martin and all the MyFaces developers, I'd like to thank you for such a great framework! Web framework choice was a tough decision and MyFaces came out as a clear winner due to component orientation and outstanding extensibility. Regards, Alexey > wrote: > > > I really like the idea. It shows that with JSF and > > Hibernate, you can > > start reduce boilerplate code to the max. What is > > left to do is > > defining the design, and that's it. > > > > Thank you. We were tired of writing boring code over > and over again. And JSF+Hibernate seemed like a > killing combo :) > > > You don't show in your tutorials how to customize > > the action methods > > if need be, though. > > Sorry, missing the point... Maybe you could give me > an > example of what you wanted to accomplish? > > > > > How are you handling hibernate sessions and state > > saving with the framework? > > Each request always have a new Hibernate session > associated. All the Hibernate-related logic is > performed only inside this session. We tried a lot > of > various approaches for Hibernate integration and > have > found out that the best way (and the simplest one) > was > to never store references to persistent objects > keeping their IDs instead. Having the ID we always > can > reload the object in the current session. The same > is > true for objects stored in the HTTP session (for > instance, ShoppingCart). > > Many current approaches to state saving favor HTTP > session over request. But writing applications we > try > to avoid storing data in HTTP session due to many > issues that arise in this case. I won't get into > details here because I'm sure every developer is > perfectly aware of them. > > To pass an object via a request we must be able to > assosiate the object with a string ID that can be > used > to restore the object on a target page. This is > pretty > easy for many built-in types (numbers, strings, > dates > etc). Such an approach can be easily extended any > object assuming that there's a unique ID > representing > the object. For instance, persistent objects can be > represented as Object Type + Hibernate ID. If the > objec t is not supported by Rumba we have to resort > to > HTTP session. > > Taking into account all the above Rumba can > associate > an object with ordinary <h:outputLink> which is very > useful for "edit links". For forms that get > submitted > we use JSF state saving but always encode objects > into > IDs to avoid any possible issues with persistent > objects. > > I'm sure it is nothing new, just a common pattern > built into a reusable framework. > > > > > regards, > > > > Martin > > > > On 3/31/06, Werner Punz <[EMAIL PROTECTED]> wrote: > > > Alxeij great... > > > > > > I think your way is the way to go, moving over > > > to the next level. > > > God knows why almost every week the next > framework > > pops > > > up which still messes around on servlet jsp > level > > > instead of trying to add value to one of the > > existing frameworks. > > > Great stuff. > > > > > > > > > > > > Werner > > > > > > Alexey Maslov schrieb: > > > > Hi, > > > > > > > > I want to introduce a new framework and I'm > a > > bit > > > > afraid of it. There are so many Java > frameworks > > > > announced these days that personally I'm tired > > of all > > > > this. So, please be kind to this post :). > Thank > > you. > > > > > > > > We have developed a new MyFaces-based > > application > > > > framework called "Rumba." It is not a silver > > bullet or > > > > "the best framework that will make you 10x > > > > productive." Rumba has a clear focus � it is > an > > > > application framework that builds a reusable > > > > Controller that should seamlessly integrate > web > > > > framework (MyFaces) and persistence framework > > > > (currently Hibernate). > > > > > > > > Key Rumba concepts: > > > > - Objects can be passed between web pages as > > simple > > > > request attributes > > > > - Page controls can be directly bound to an > > object > > > > model > > > > - Transparent persistence > > > > - Slick configuration > > > > > > > > You can read more on Rumba website: > > > > http://www.rumbaframework.org. We have made a > > brief > > > > tutorial to get started easily. > > > > > > > > What do you think? Does the idea make sense to > > you? > > > > Have we missed anything important? > > > > > > > > Thank you very much for feedback :) > > > > > > > > > > __________________________________________________ > > > > Do You Yahoo!? > > > > Tired of spam? Yahoo! Mail has the best spam > > protection around > > > > http://mail.yahoo.com > > > > > > > > > > > > > > > > -- > > > > http://www.irian.at > > > > Your JSF powerhouse - > > JSF Consulting, Development and > > Courses in English and German > > > > Professional Support for Apache MyFaces > > > > > > > __________________________________________________ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam > protection around > http://mail.yahoo.com > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
