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!
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?
Regards,
Cagatay,
On 4/3/06, Alexey Maslov <[EMAIL PROTECTED]> wrote:
> Martin Marinschek schrieb:
> >>> 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?
> >>
> >
> > If I understood the framework right, you define
> new
> > _expression_-language statements which have a
> special meaning. E.g.,
> > create a new object. There might be cases where
> just calling the
> > constructor is not enough - and I want to
> interfere with the creation
> > process. Same, and probably even more necessary on
> save. Do you define
> > and make available such hooks?
> >
> Well the way I see it, this framework can cover 70%
> of all simple crud
> usecases.
> Ok we do not have the clear bo/dao pattern here, but
> for simple apps amd
> normal crud forms you do not need that, the same
> goes for special
> creation code.
Yes, I completely agree.
We do not try to cover everything with Rumba - I do
not think it is possible/viable. But we want to
simplify typical activities while allowing a developer
to use plain Java coding for all the advanced tasks.
We do not hide the power of JSF and Hibernate in any
case building a higher level abstraction on top.
>
> This is a clear contestor for making it very simple,
> especially since it
> also seems to be able to cope with scoping via bean
> pushing over
> parameters and it does not seem to be the
> configuration hell seam is.
Thank you :)
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
