This sounds great. It would be nice if we could coordinate on the non-presentation portions of the app so that we can share some backend code.
For example...
Only the Roller Editor UI uses Struts: the page and RSS generation are done using Velocity and the backend is just Castor (soon to be Hibernate). The quickest way for you to get up and running would be to use the Roller backend and just rewrite the editor UI using WebWork and SiteMesh.
- Dave
Jason Carreira wrote:
Ok, so here's an idea for the Webwork2.0 sample app:
Let's do Roller, only better, using Webwork 2.0, Hibernate, and Joe's RSSLibJ.
Roller is annoying me because of a) performance and crashing issues, and b) Support for PostgreSql is poor :-)
Thoughts? Volunteers? Of course I'm volunteering...I think this app should be easy enough to get working pretty quickly (not with all the features, but getting started) and should be both complex enough to be a showcase and simple enough to be easily understood by newcomers.
Jason
-- Jason Carreira Technical Architect, Notiva Corp. phone: 585.240.2793 fax: 585.272.8118 email: [EMAIL PROTECTED] --- Notiva - optimizing trade relationships (tm)
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
