Geert Bevin <gbevin <at> uwyn.com> writes:
>
> Hi Claudio,
Geert, thanks for your time to provide de answers.
First of all, sorry to compare all of this with the action based framework
(as I worked with Struts and now with WebWork), but I need to compare with
something I already know. My clear intention is to understand how RIFE can bring
me more productivity.
Please see below:
> in practice you will only rarely declare individual parameters, but
> use submission beans instead. In that case everything is driven from
> your bean class and constraints are propagated throughout the
> framework. For instance a non editable constraint will automatically
> remove the parameter from the submission when the bean is declared
> (http://rifers.org/wiki/display/RIFE/Constraints).
Cool!
I looked at the friends example, and the submission bean can be a POJO
class.
Can the wiki page be updated, for the newcomers (like me) understand that
their POJO class can be used as the submission bean ?
> The reason why every this declared in RIFE is three-fold:
>
> * The engine guarantees that you have no naming conflicts in the data
> flow which allows elements to function into any context (widget,
> portlet, page, site).
Humm, looks like I need to understand much more of RIFE offers, than a web
framework.
> * The engine takes control over your data flow and state transitions,
> you don't have to handle it yourself at all, this is only possible it
> it knows what it's working with.
Sorry, I didn't get it, when it relates to the state transitions. Is there
some example out there ?
When you talk about "you don't have to handle it yourself at all" I
understand that, eg: I don't need to care about validations ?
> * The data flow of your web application is clearly documented and
> you're 100% sure that nothing else drives your element since no other
> parameter will come in. This is a huge benefit once your application
> starts growing beyond a trivial prototype or when multiple people are
> working together on it.
So, I am sure, RIFE has much more than I thought. ;)
I already downloaded everything. Expect some questions (at least those I
could not find on the list archives)
> Hope this helps,
>
> Geert
>
> On 18 Jul 2006, at 19:37, Claudio Miranda wrote:
>
> >
> > First of all, I started to understand the RIFE framework. One
> > of the point I
> > use is to compare how I do things today and how it could be done
> > with RIFE.
> > Currently I use webwork 2.1.x.
> >
> > Looking at the Element Definition wiki page [1], I see that
> > every form
> > parameter must be declared at submission element. So why is that
> > needed ?
> > I ask this because, if the web form has 5 parameters, it must
> > be declared on
> > the following "aspects": View (velocity, JSP, whatever), validation
> > layer, POJO,
> > O/R mapping and database fields. So thats is 5 things to change, if
> > some new
> > field is needed.
> > With RIFE, it grow one more point to change (as I understood
> > how the forms
> > works), that is the element definition.
> > So, I didn't get how the things works ?
> >
> > 1 - http://rifers.org/wiki/display/RIFE/Element+Definition
> >
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
