On 10/5/07, Wes Wannemacher <[EMAIL PROTECTED]> wrote: > I am poking around for things I can help with. I came across WW-1399 > and I remember some discussion before on struts-[dev|user] that > hibernate's license is not compatible with apache's. So, assuming we > want to use ORM, is there a particular mapper I should look at? I could > give this a try with cayenne. It isn't as popular, but mostly similar. > One issue though is that Spring and cayenne don't make much sense, so > it probably would not include DI... > > Anyhow, what are your thoughts? I could be wrong about hibernate, if > it can be distributed with mailreader, I'll use it.
Today, I would go with JPA and TopLink (we can distribute TopLink as a binary.) See the end of Musachy's tutorial. * http://struts.apache.org/2.x/docs/struts-2-spring-2-jpa-ajax.html BTW, I have a refactored version of the people example here: * https://sq1-struts2.googlecode.com/svn/trunk/articles/people In the Shale repository, there is a JPA MailReader implementation, but I haven't had a chance to try it out. * http://svn.apache.org/viewvc/shale/framework/trunk/shale-apps/shale-mailreader-jpa/ A good way to go would be to snag the Shale JPA Mailreader classes, try them under Toplink, and make whatever changes we need to the MailReader to make it work. When Cayenne 3 comes out, we can try switching providers, to prove that JPA can be a commodity :) As far as the MailReader in general goes, the implementation could use an overhaul. The original MailReader DAO is quirky, and so the MailReader implementation has to work around the quirks. With a streamlined DAO, the MailReader implementation could also be streamlined. -- HTH, Ted Attend "Migrating to Ajax" at ApacheCon US 2007: * http://us.apachecon.com/us2007/program/talk/1883 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
