Dear Wiki user, You have subscribed to a wiki page or wiki category on "Jakarta-tapestry Wiki" for change notification.
The following page has been changed by NathanHamblen: http://wiki.apache.org/jakarta-tapestry/Tapestry31Spring The comment on the change is: updating references to tapestry 3.1, cleaning up a little ------------------------------------------------------------------------------ - = Combining Tapestry3.1, Hivemind1.1 and Spring = + = Combining Tapestry 4.0, Hivemind 1.1 and Spring = - Many people ask how to combine above solution, I'm also curious about that and spend one-and-a-half-day to figure out the best way to do that. Reasons behind that are: + Many people ask how to combine the above solution, I was also curious about that and spent one-and-a-half-day to figure out the best way to do that. Reasons behind that are: - 1. Tapestry is good framework for web UI. + 1. Tapestry is a good framework for web UI. 2. Spring is a good container framework. Spring is also a good example of software project development. 3. Hivemind for me, is not mature enough (and proved when I found bug while I do this project). Hivemind has good future, but I doubt it'll 100% replace Spring. Both of them have their own advantage. - For release version, I like combination of Tapestry+Spring+Hibernate, but they are all growing very fast and I really like to try milestone version of Tapestry31+Spring+Hibernate30+(Hivemind11). I'll omit Hibernate in my explanation since the hard part is between Tapestry and Spring. Once Spring is correctly configured, Hibernate solution is very pluggable. + For release version, I like combination of Tapestry+Spring+Hibernate, but they are all growing very fast and I really like to try milestone version of Tapestry4+Spring+Hibernate30+(Hivemind11). I'll omit Hibernate in my explanation since the hard part is between Tapestry and Spring. Once Spring is correctly configured, Hibernate solution is very pluggable. - Magic reference for Tapestry and Spring combination is in Spring Reference. We still can use that solution but we will lost the pretty combination offered by new Tapestry+Hivemind. Another disadvantage is the solution extend BaseEngine which will deprecated in Tapestry 3.1. + Magic reference for Tapestry and Spring combination is in Spring Reference. We still can use that solution but we will lost the pretty combination offered by new Tapestry+Hivemind. Another disadvantage is the solution extend BaseEngine which will deprecated in Tapestry 4. - [I assume basic knowledge of Java, Tapestry, and Spring] + ''Basic knowledge of Java, Tapestry, and Spring assumed.'' == Hivemind Configuration == + '''You can skip this step''' (Hivemind Configuration) by downloading tapestry-spring.jar from http://sourceforge.net/projects/diaphragma and placing it on your classpath. Then skip down to Spring Configuration and you should be able to reference Spring beans from Tapestry 4. ''Or, keep reading below if you're interested in how it works...'' - {{{ - Now you can forget this step (Hivemind configuration) by simply download a tapestry-spring jar from http://sourceforge.net/projects/diaphragma and place it on your classpath. - }}} Hivemind is related intimately with Tapestry, even HLS has provide some way to easily play with Hivemind in Tapestry. Like Spring, Hivemind is working by special XML metadata. Hivemind also has its own metadata, and so Tapestry. If we want to contribute to the whole Hivemind registry, the easiest way is by creating hivemodule.xml in your WEB-INF directory. Here is what you need in this project: {{{ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
