Here's one crazy idea that might take you less time: go through the RIFE
"simple blog" movie (slightly out of date, but still fairly accurate)
and, once you have that application up and running and you understand
how it works (which you will, by virtue of going through the movie),
make a Struts version of it. Since you already know Struts that should
be pretty simple.
Then you can work backwards and write up why thing X in Struts looks
like Y in RIFE.
Trying to port an existing app to RIFE while learning RIFE is likely to
be more frustrating than porting a known working RIFE app to a framework
you're already expert in.
BTW, I recommend you initially go through the movie in one sitting,
rather than stopping at each point and trying to translate each newly
introduced concept in Struts terms. It will make a lot more sense once
you have the big picture. RIFE, as you'll discover, is a *very*
different beast than Struts or any other MVC framework with Struts-like
conceptual models (Spring MVC, etc.)
-Steve
Steve Holmes wrote:
I'd be happy to but my time is very limited so it might take a while. I was
thinking I would try to find a demo struts app or something like that and
rebuild it using RIFE and document how it is done.
I expected it would be more than 3 pages. Even if it is 20 pages it would
be very useful for Struts guys like me.
Thanks!
-Steve
_______________________________________________
Rife-users mailing list
[email protected]
http://lists.uwyn.com/mailman/listinfo/rife-users
