Hi all,
Jason Carreira wrote:
Hi Dave,
Can you point us to some entry points where we would start plugging
Webwork on top of the core Roller code? I'm still not sure, like Patrick
said, if it would make more sense to start from scratch or build on top
of the Roller backend.
Sounds like you guys want to roll your own example app from scratch and a weblogger is a great example app. I look forward to seeing it develop and to stealing whatever code I can.
Are you guys going to dump the faux-EJB backend
you have now?
We will not be generating the persistent objects anymore, if that is what you mean. I'm working on that right now. We will still be using XDoclet though.
I know you're working on putting in Hibernate, but I had the impression it was going to be a runtime choice, rather than a replacement.
I don't have the time to maintain two backends, so if Hibernate works out then our Castor implementation will probably go away. Unless somebody volunteers to maintain it (fat chance of that).
Thanks again for the awesome tool in Roller... Maybe we can convert you guys over to Webwork? :-)
You are welcome.
I don't plan on rewriting the Roller UI. I'll just switch over whole-hog to your new weblogging software once it is up to snuff, maintaining my own is a persistent pain in the backend ;-)
Cheers, Dave
------------------------------------------------------- This SF.net email is sponsored by: Scholarships for Techies! Can't afford IT training? All 2003 ictp students receive scholarships. Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more. www.ictp.com/training/sourceforge.asp _______________________________________________ Opensymphony-webwork mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
