Developing a Spring Framework MVC application step-by-step

最新推荐文章于 2017-03-06 17:11:22 发布

chenyujin999

最新推荐文章于 2017-03-06 17:11:22 发布

阅读量789

点赞数

分类专栏： Spring Framework

Spring Framework 专栏收录该内容

11 篇文章 0 订阅

订阅专栏

Copies of this document may be made for your own use and for distribution to others, provided that you do not charge any fee for such copies and further provided that each copy contains this Copyright Notice, whether distributed in print or electronically.

Table of Contents

Overview

1. What's covered 2. Prerequisite software 3. The application we are building

1. Basic Application and Environment Setup

1.1. Create the project directory structure 1.2. Create 'index.jsp' 1.3. Deploy the application to Tomcat 1.4. Check the application works 1.5. Download the Spring Framework 1.6. Modify 'web.xml' in the 'WEB-INF' directory 1.7. Copy libraries to 'WEB-INF/lib' 1.8. Create the Controller 1.9. Write a test for the Controller 1.10. Create the View 1.11. Compile and deploy the application 1.12. Try out the application 1.13. Summary

2. Developing and Configuring the Views and the Controller

2.1. Configure JSTL and add JSP header file 2.2. Improve the controller 2.3. Decouple the view from the controller 2.4. Summary

3. Developing the Business Logic

3.1. Review the business case of the Inventory Management System 3.2. Add some classes for business logic 3.3. Summary

4. Developing the Web Interface

4.1. Add reference to business logic in the controller 4.2. Modify the view to display business data and add support for message bundle 4.3. Add some test data to automatically populate some business objects 4.4. Add the message bundle and a 'clean' target to 'build.xml' 4.5. Adding a form 4.6. Adding a form controller 4.7. Summary

5. Implementing Database Persistence

5.1. Create database startup script 5.2. Create table and test data scripts 5.3. Add Ant tasks to run scripts and load test data 5.4. Create a Data Access Object (DAO) implementation for JDBC 5.5. Implement tests for JDBC DAO implementation 5.6. Summary

6. Integrating the Web Application with the Persistence Layer

6.1. Modify service layer 6.2. Fix the failing tests 6.3. Create new application context for service layer configuration 6.4. Add transaction and connection pool configuration to application context 6.5. Final test of the complete application 6.6. Summary

A. Build Scripts

关注

0
点赞
踩
0

收藏

觉得还不错? 一键收藏
0
评论
复制链接

分享到 QQ

分享到新浪微博

扫一扫

专栏目录

chenyujin999 CSDN认证博客专家 CSDN认证企业博客

码龄14年

141: 原创

107万+: 周排名

201万+: 总排名

18万+: 访问

: 等级

3304: 积分

3: 粉丝

1: 获赞

6: 评论

4: 收藏

私信

关注

热门文章

分类专栏

最新评论

NFS Server and Yum Repository Setup
chenyujin999: The solution is to use RHN Classic and to disable subscription-manager by editing the katello plugin configuration file and set "enabled" value to '0' Disable the plugin by editing the file /etc/yum/pluginconf.d/katello.conf then change the value "enabled=1" to "enabled=0" and save file. Once the change is performed and saved, execute following commands: rm -rf /var/cache/yum/* yum clean all yum update
55 New Features in JDK 7 - NIO2
chenyujin999: https://blogs.oracle.com/java/entry/a_file_i_o_tutorial
why Jquery and (Javascript Fundamentals ) Understanding the Document Object Model(DOM)
chenyujin999: So the code that is directly in the head and body of the web page and not enclosed in functions or objects will run sequentially as soon as the file containing the code has loaded sufficiently for that code to be accessed. Basically this means that whatever code you have in the head and body of your page that is not inside a function or object will run as the page is loading once the page has loaded sufficiently for the line of code to be available to be run. What this means is that any code placed directly in the page that is intended to interact with elements within the page needs to appear further down the page than the elements in the page that it needs to interact with. In general this means that if you want to use direct code to interact with your page content that such code should be placed at the bottom of the body. http://javascript.about.com/od/hintsandtips/a/exeorder.htm
why Jquery and (Javascript Fundamentals ) Understanding the Document Object Model(DOM)
chenyujin999: window.onload这个函数将会在你的所有页面DOM元素（说白了就是整个页面）加载完成之后触发。自己写的东西放在其中是为了防止页面的东西还没有全部加载完成就调用。　　比如你想在利用js来初始化一个文本输入框，让里面默认就写上“请输入”三个字。　　如果不用onload的话很有可能出现一种情况，那就是：打开网页的人网络很差，你的文本框还没有加载出来就调用了你写的方法去初始化文本框。这时候就会报错因为页面根本没有文本框。这样用onload的好处出来了。等所有DOM都加载完成再去调用你写的函数就不会出现问题了。------手动码字很辛苦啊。
why Jquery and (Javascript Fundamentals ) Understanding the Document Object Model(DOM)
chenyujin999: JavaScript中为什么要用window.onload对应的函数将所有要运行的脚本包起来 2013-08-25 15:49落叶之殇恋| 分类：JavaScript| 浏览55次如果不这么做脚本还可以正常运行吗我是新手，想找个师傅带带我，虽然能找到书本但是具体情况的处理还是缺乏经验，希望有个大神能指导一二，非常感谢！ window.onload方法是在页面的所有元素都加载完毕后才会触发，包括图片。所以当链接质量不好的时候会导致该方法触发延迟。在使用的时候需要注意。通常我们希望在Dom元素初始化完成的时候就执行操作，那么可以借助一些javascript框架。比如jquery中提供了$(document).ready(function(){});方法。或者在元素加载完成后再写javascript脚本如 <body>  </body> <script> function customOnload(){ // do something. } customOnload(); </script> 追问所有脚本都要放在函数里面吗，我没定义函数直接把脚本写在script标签里面了，执行的时候就报错，我的脚本是这样的：<script>var p = document.getElementById("hotTags");p.onclick = function() {...}</scipt>但是我把所有的内容放在window.onload = function() {..}里面就不会出错回答你遇到的问题就是使用window.onload要解决的问题，如果我没有猜错的话你的script标签应该是放在head标签内的。当脚本放在window.onload外时，当执行到var p = document.getElementById("hotTags");这一行时，id为hotTags的dom元素还没有被创建。所以才会报错。建议你仔细看一下答案，已经写的很清楚了。提问者评价谢谢你，明白了！

最新文章

目录

评论

被折叠的条评论为什么被折叠?

到【灌水乐园】发言

查看更多评论

添加红包

成就一亿技术人!

hope_wisdom

发出的红包

实付元

使用余额支付

点击重新获取

扫码支付

钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。