On Mon, Sep 15, 2008 at 12:04 PM, Rick <[EMAIL PROTECTED]> wrote: > On Mon, Sep 15, 2008 at 1:02 PM, Matt Raible <[EMAIL PROTECTED]> wrote: >> I like the annotation approach. The reason AppFuse Light doesn't use >> annotations is I haven't gotten around to adding them. >> >> Here's something I blogged last November about AppFuse Light 2.0 >> (http://raibledesigns.com/rd/entry/appfuse_light_1_8_1): >> >> What's on tap for AppFuse Light 2.0? Here's what I'm hoping to do: >> >> 1. Drop the seldom-used persistence frameworks: JDBC, JDO and OJB. >> 2. Drop Struts 1.x and WebWork as web frameworks (replaced by Struts 2). >> 3. Support the same persistence frameworks as AppFuse: Hibernate, >> iBATIS and JPA. >> 4. Re-use appfuse-service, appfuse-hibernate, appfuse-ibatis and >> appfuse-jpa in AppFuse Light. I'll likely include the core classes >> (User, Role) since AppFuse Light is more "raw" than AppFuse. >> 5. Require Java 5. >> >> Let me know if you disagree with any of these items or would like to >> see other enhancements. > > One things I'm trying to do, and possibly this might not be a bad idea > for even appfuse light, is I like the persistence framework to remain > it's own jar, so for appfuse light consist of the persist.jar and then > the war which uses this persist.jar. I know this might be a bit > overkill but I still like it. (I debated about even moving out the > model into its own project, but felt that overkill... just having the > model and daos in the peristence module works for me. ) > > One of things now I wan to do is use the annotation based approach > that regular appfuse uses, but it might take me a while to get the > dependencies I need all correct. > Also I"m confused since the applicationContext.xml file is so > different between the two. (This is why j2ee stuff gets so overly > complicated imo, since there are often different ways to do things > within the same framework - never mind trying to integrate multiple > frameworks. Again, another reason why I like the concept of appfuse- a > standard way of getting started that uses best practices.) > > Matt, if you could make some quick modifications to the current > appfuse light to use the hibernate annotations that would be awesome. > (I don't care about the web framework setup.. just a modification of > any of the spring-hibernate ones would be fine.) Even if it's not > official build or anything, just something for me to go off of. In the > meantime I'll work on it myself to see what I come up with.
I wish I had the time and energy to make this happen. However, I don't this week. Patches welcome. ;-) Matt > > Do you consider regular appfuse using the current best practices that > you are happy with? If so, I can just drive off of that instead of > appfuse light. > > Thanks Matt > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
