1 Star 7 Fork 1

何呵呵/前后端分离的个人博客管理系统

加入 Gitee
与超过 1200万 开发者一起发现、参与优秀开源项目,私有仓库也完全免费 :)
免费加入
克隆/下载
贡献代码
同步代码
取消
提示: 由于 Git 不支持空文件夾,创建文件夹后会生成空的 .keep 文件
Loading...
README
GPL-3.0

前后端分离的个人博客管理系统

第一章 需求分析

  • 近年来随着信息技术的进步,B1og 也快速扩张,它已经满足不了用户的软件文档写作课程设计需求。目前用户在网络上发表文章、张贴内容的目的有很大的差异,但是, 由于沟通方式比电子邮件、讨论群组以及BBS和论坛更简单和容易,博客系统已经成为广大各界用户进行沟通的主流工具,本系统是针对博客用户的需求设计的,可以完成博客用户注册、登入、发表、浏览、修改博文、上传、浏览照片、留言等主要功能。
  1. 课程设计题目 Blog就是以网络作为载体,简易迅速便捷地发布自己的心得,及时有效轻松地与他人进行交流,再集丰富多彩的个性化展示于一体的综合性平台。 不同的博客可能使用不同的编码,所以相互之间也不一定兼容。这使得不同的博客各具特色。 Blog是继Email、BBS、ICQ之后出现的第四种网络交流方式,是网络时代的个人“读者文摘”,是以超级链接为武器的网络日记,是代表着新的生活方式和新的工作方式,更代表着新的学习方式。具体说来,博客(Blogger)这个概念解释为使用特定的软件,在网络上出版、发表和张贴个人文章的人。

  2. 课程设计任务及要求 在当下这个发展快速的信息化时代,越来越多的博客网站开始建立或者已经使用博客管理系统,利用计算机和网络对信息进行管理已是大势所趋。博客系统必将代替之前繁琐的人工操作模式,实现由复杂、冗余性手工操作向人机简便操作的转化,运用计算机完成数据增加、修改、查询、删除以及统计等工作,提高了管理人员工作效率,避免繁重的业务量造成的人为错误,还可运用信息共享加快数据传递。通过对博客管理系统的操作,既节省大量的人力与物力,又不用保存与整理数据文件,将一切信息转化为数字化,提高了工作效率。

  3. 系统开发技术和环境 软件体系:采用B/S模式。B/S结构(Browser/Server结构)即浏览器服务器结构。采用B/S结构是因为该结构在功能拓展和维护方面简单、方便,只需要增加或更改网页,并且B/S结构是以浏览为主,录入简单。而个人博客管理系统网站就是通过web浏览器访问,选用B/S模式最为合适。

  4. MyEclipse与Tomcat简介 在JSP的web程序设计中,常使用MyEclipse做编辑工具,在J2EE和数据库开发领域里,十分通用。通过对应用程序服务器进行整合,可以大大的增强运算速度。 Tomcat是一种小型web程序服务器,由于它是免费开源的,并且支持访问量较少,所以常常被用来私人使用,J2EE程序设计中成为最好的选择。

  5. JSP简介 JSP是一种开发动态系统的编程语言,它能嵌入在html中使用,也能单独使用,同时具有多种有优点,可以说,JSP已经成为Web脚本技术的先驱。它融合了现代编程语言(如C,JSP)的一些最佳特性。Linux、JSP、Tomcat和MySQL的组合已经成为Web服务器的一种配置标准。JSP可以用来:收集表单数据、生成动态网页、字符串处理、动态输出图片、处理服务器端文件系统、编写数据库支持的网页、会话跟踪控制、处理XML文件、支持利用大量的网络协议、服务器端的其他相关操作。

  6. 性能需求 该系统在性能功能上达到如下需求: 操作简单、界面友好:完全控件式的页面布局,使得博客的管理更简便,许多选项包括添加博客、删除博客等通过选择数字项就可以完成;另外,查询所有博客信息功能也让管理员随时清楚每一个博客的具体情况。对常见的博客管理的各个方面:博客添加、删除、修改、查询等方面都大体实现,实现了管理员对博客信息的管理要求; 即时可见:对博客的处理(包括添加、删除、修改)将立即在后台数据库中进行更新,达到“即时操作、即时生效”的功能; 系统运行应该快速、稳定、高效和可靠; 在结构上应具有很好的可扩展性,便于将来的功能扩展和维护。 管理员根据对博客管理系统的需求分析的上述要求及博客系统模型结构,博客管理的功能模块分为四个大的部分,博客的添加,博客的删除,博客信息的修改,博客的查询。

第二章 系统设计

  1. 系统设计方法三原则
  • 人类在复杂的工程技术系统如能源、交通等建设方面,积累了丰富的经验,为研究复杂系统如管理系统提供了科学的指导性方法论,其主要原则如下:
  1. 整体性原则。系统是相互联系,相互作用的诸要素组成的综合体。我们必须从整体和各组成部分的相互关系来考察事物,从整体目标和功能出发,正确处理系统各组成部分之间的相互关系和相互作用。
  2. 分解—协调原则。就是把复杂问题化成若干相对简单的子问题以方便求解。若子系统的问题比较复杂,还可以再分。但在处理各类子问题时,必须根据系统的整体功能和目标,协调各子系统的行为、功能与目标,以保证整体功能目标的实现。
  3. 目标优化原则。所谓目标优化原则对简单的系统来说,是求最优解,对复杂系统来说,求的是满意解。一定要注意,目标优化原则并不简单是求最优解的问题。
  • 这里最需要指出的是:以上三原则是系统方法中处理复杂系统问题的三个主要原则,并非是全部原则。在处理实际问题时,还需要在这些原则的指导下,根据问题的特点,确定求解的具体方法和策略。
  1. 系统的功能模块 个人博客管理系统分分为前台和后台。前台主要的功能分为博客的浏览,查询和评论。后台主要的功能分为三个大的部分,博客管理,标签管理,评论管理。博客管理分为添加博客,查询所有博客信息,修改博客信息,删除博客。添加博客是指通过添加博客的名称、作者等信息来加入该博客;查询所有博客信息是对所有博客的内容进行查询;修改博客信息是通过博客的ID找到该博客并修改其信息,删除博客是通过其ID找到该博客并删除。标签管理分为添加标签,查询所有标签信息,修改标签信息,删除标签。添加标签是指通过添加标签的名称、内容等信息来加入该标签;查询所有标签信息是对所有标签的内容进行查询;修改标签信息是通过标签的ID找到该标签并修改其信息,删除标签是通过其名称找到该标签并删除。评论管理中可以通过其名称找到该评论并删除。系统的功能模块图如图2-1所示。 图2-1个人博客管理系统功能模块图

  2. 系统实体类设计

  3. 博客实体类 Blog.java 此类里面存储博客类的成员变量、构造方法,用来创建blog对象;

  4. 用户实体类 User.java 此类里面存储管理员类的成员变量、构造方法,用来创建user对象。

  5. 标签实体类 Category.java 此类里面存储标签类的成员变量、构造方法,用来创建category对象。

  6. 评论实体类 Comment.java 此类里面评论类的成员变量、构造方法,用来创建comment对象。

  7. 系统接口设计

  8. 数据库中数据操作 1. “博客数据库操作”接口:BlogDao.java,该接口具有的方法如下:

    • add()方法用于向数据库中添加博客;
    • list()方法用于查询数据库中的博客;
    • delete()方法用于删除数据库中的博客;
    • update()方法用于修改数据库中博客的信息;
    • addReadCount()方法用于修改指定博客的阅读量。
    • getBlogById()方法用于通过博客ID获取博客。
    • getBlogFenYe()方法用于获取博客列表。
2. “用户数据库操作”接口:UserDao.java,该接口具有的方法如下:
   - login()方法进行登录验证;
   - register()方法用于向数据库中添加用户;
   - update()方法用于更新用户信息;
   - getUserById()方法用于通过用户ID获取用户信息;
   - getUserFenYe()方法用于获取用户列表;
   - updPassword()方法用于修改密码。
3.  “标签数据库操作”接口:CategoryDao.java
   - add()方法用于向数据库中添加标签;
   - delete()方法用于删除数据库中的标签;
   - update()方法用于修改数据库中标签的信息;
   - getCategoryrFenYe ()方法用于查询数据库中的标签;
4. “博客评论数据库操作”接口:CommentDao.java
   - add()方法用于向数据库中添加博客评论;
   - delete()方法用于删除数据库中的博客评论;
   - update()方法用于修改数据库中博客评论的信息;
   - getCommentFenYe ()方法用于查询数据库中的博客评论。
  1. 程序中的数据操作 1. “博客的功能操作”接口:DataBase.java,该接口具有的方法如下:
    • getConn()方法获取数据库连接;
    • closeAll()方法关闭数据库连接;
    • executeQuery()方法执行查询操作;
    • executeUpdate()方法执行增删改操作。
2.  “加密的功能操作”接口:Sha256.java
   - getSHA256()方法实现加密功能。
  1. 系统接口实现类设计

  2. 用户Dao层接口:UserDao.java,管理员Dao层接口类的实现类是UserDaoImpl.java。

  3. 博客Dao.java层接口:BlogDao.java,博客Dao层接口类的实现类是BlogDaoImpl.java。

  4. 评论Dao.java层接口:CommentDao.java,评论Dao层接口类的实现类是CommentDaoImpl.java。

  5. 标签Dao.java层接口:CategoryDao.java,标签Dao层接口类的实现类是CategoryDaoImal.java。

  6. 系统数据库设计 数据库是由多个相互关联的数据表组成,本数据库利用MySQL实现并完成数据库的设计,在本系统中包括如下:确定数据库内所有数据表的名称及表内所含字段的名称、评论、长度、主键及是否为空;确定数据库文件是否需要建立索引、是否具有外键,数据表等等。

  7. 数据库表设计 1. 用户表(USER)用于存储管理员的相关内容

序号 字段名称 字段说明 数据类型 位数 属性
1 userid 用户编号 int 11 必填,非空,主键
2 username 用户名 varchar 30 必填,非空
3 password 密码 varchar 100 必填,非空
4 email 邮箱 Varchar 50 必填,非空
5 admin 管理员 int 11 必填,非空
2. 博客表(BLOG)用于存储博客的相关信息
序号 字段名称 字段说明 数据类型 位数 属性
1 blogid 博客编号 int 11 必填,非空,主键
2 blogtitle 博客标题 varchar 50 必填,非空,唯一
3 blogimgurl 博客封面 varchar 100 必填,非空
4 blogdatetime 日期 datetime 必填,非空
5 blogsummary 摘要 varchar 500 必填,非空
6 blogcontent 博客内容 longtext 必填,非空
7 blogreadcount 阅读量 int 11 必填,非空
8 commentnum 评论量 int 11 必填,非空
9 categoryid 分类ID int 11 必填,非空,外键
3. 博客评论表(COMMENT)用于存储博客评论
序号 字段名称 字段说明 数据类型 位数 属性
1 commentid 评论编号 int 11 必填,非空,主键
2 blogid 博客ID int 11 必填,非空,外键
3 commentcontent 评论内容 varchar 300 必填,非空
4 commentname 评论者名称 varchar 11 必填,非空
5 commenttime 评论时间 datetime 必填,非空
6 commentLike 点赞量 int 11 必填,非空
4. 标签表(CATEGORY)用于存储标签  如表2-4示:

表2-4标签表

序号 字段名称 字段说明 数据类型 位数 属性
1 categoryid 标签编号 int 11 必填,非空,主键
2 categoryname 标签名称 varchar 20 必填,非空
3 categorycontent 标签描述 varchar 20 必填,非空
4 blognum 博客数量 int 11 必填,非空
  1. 数据库触发器设计 1. 当添加博客的时候触发标签中博客数量增加。 2. 当删除博客的时候触发标签中博客数量减少。 3. 当添加评论的时候触发博客中评论数量增加。 4. 当删除评论的时候触发博客中评论数量减少。

第三章 详细设计

  1. 个人博客管理系统前台的界面

  2. 访问者浏览的主界面。页面如图3-1所示: 图3-1 图管理系统的主界面

  3. 访问者可以在博客页面查看博客内容。页面如图 3-2所示: 图3-2 博客界面

  4. 访问者可以在博客页面文章下面发表评论,交流观点。如图3-3所示: 图3-3 评论界面

  5. 访问者可以通过搜索,博客标签,博客日期来查找博客。如图3-4,3-5和3-6所示: 图3-4 搜索内容界面 图3-5 标签查询界面 图3-6 日期查询界面

  6. 用户登录注册界面

  7. 用户可以再注册登录页面注册账号并登录。页面如图 3-7所示: 图3-7 用户登录注册界面

  8. 个人博客管理系统后台的界面 用户分为普通用户和管理员,只有管理员可以进入后台。

  9. 管理员可以在添加页面进行添加博客、标签的操作的页面。添加博客界面如图3-8所示: 图3-8 添加博客界面

  10. 管理员可以在列表页进行查询、删除博客、标签和用户的操作。博客管理界面如图3-9所示: 图3-9 博客管理界面

  11. 管理员可以在编辑页进行博客内容、用户信息和标签内容的修改操作。用户更新界面如图3-10所示: 图3-10 用户更新界面

第四章 系统测试

  • 为了更好的完成每个模块的功能测试,运用到了单元测试等一系列的方法。本系统的测试主要采用黑盒测试中的功能测试,测试用例设计采用等价类划分进行设计。
  1. 功能测试结果
  2. 用户登录,用户登录功能测试如表4-1、表4-2、表4-3所示: 1. 表4-1 登录描述 |用例编号| 101| |---|---| |功能名称| 用户登录| |功能描述| 用于判断、用户登录信息}| |测试方法| 黑盒测试|
2. 表4-2登录等价类划分
输入条件 有效等价类 编号 无效等价类 编号
用户名 用户名正确 1 用户名有误 3
密码 密码输入正确 2 密码输入有误 4
3. 表4-3测试用例设计
用例编号 测试数据 预期结果 覆盖范围 是否通过
1.1 admin ,123456 登录成功 1、2
1.2 admin ,12345 系统提示输入错误 1、4
1.3 admi ,123456 系统提示输入错误 2、3
1.4 admi ,12345 系统提示输入错误 3、4
  1. 管理员功能界面,管理员功能界面测试如表4-4所示: 1. 表4-4管理员功能界面测试
用例编号 102 功能名称 查看各个功能
功能描述 是否能查看到各个功能
测试步骤 登录主页面 输入用户名、密码进行登录
浏览 是否能查看到各个功能
测试结果 通过 发现问题
  1. 添加博客,添加博客功能测试如表4-5所示: 1. 表4-5添加博客功能测试
用例编号 103 功能名称 添加博客
功能描述 管理员在添加界面添加博客
测试步骤 登录主页面 输入用户名、密码进行登录
添加博客 能否在数据库里查询到该博客
测试结果 通过 发现问题
  1. 查询博客信息,查询博客信息界面测试如表4-6所示: 1. 表4-6查询所有博客功能测试
用例编号 104 功能名称 查询所有博客信息
功能描述 管理员查询数据库中的所有博客信息
测试步骤 登录主页面 输入用户名、密码进行登录
输出 界面显示所有数据库中存储博客的信息
测试结果 通过 发现问题
  1. 修改博客,修改博客功能界面测试如表4-7、表4-8、表4-9所示: 1. 表4-7修改博客信息功能测试
用例编号 105 功能名称 管理员修改博客
功能描述 管理员修改数据库中的博客 测试方法 黑盒测试
  2. 表4-8等价类划分
输入条件 有效等价类 编号 无效等价类 编号
要修改的博客标题 输入要修改的博客编号 1 编号输入错误
修改后的博客内容 输入修改后的博客内容 2
修改后的博客标签 输入修改后的博客标签 3
 3. 表4-9测试用例设计
用例编号 测试数据 预期结果 覆盖范围 是否通过
1.1 完全图树的计数 查找到该博客 1、3
1.2 测试博客内容 修改成功 2
  1. 删除博客,删除博客功能界面测试如表4-10、表4-11、表4-12所示: 1. 表4-10删除博客功能测试
用例编号 106 功能名称 管理员删除博客
功能描述 管理员删除表中的博客
测试步骤 输入 要删除的博客名称
输出 删除成功
测试结果 通过 发现问题
 2. 表4-11等价类划分
输入条件 有效等价类 编号 无效等价类 编号
要删除的博客名称 输入博客题名称 1 主题名称为空 3
 3. 表4-12测试用例设计
用例编号 输入 预期输出 覆盖范围 是否通过
博客标题 id 1
1.1 ajax post跨域请求解决 26 博客删除成功

第五章 课程设计总结与体会

  • 随着互联网技术的大力发展,人们的日常生活已经离不开网络。未来时代我们的生活和工作一定会更加借助于信息技术的发展,越来越方便、快捷、安全、高效,在线网络的发展过程以及当下的应用情况和发展趋势,我们可以充分地相信网络技术将极大的改变我们的生活和工作方式,使我们的生活变得更加美好、舒适。
  1. 课程设计总结 本文按照软件工程开发设计方法,实现了一个博客管理系统,本系统采用JDBC技术[14],数据库MySQL,开发工具Eclipse,实现了博客管理员对博客的添加、查询、修改、删除等具体功能的操作。所有功能全部都了通过测试。博客管理系统的主要目的是促进博客管理的信息化发展。不同于以往的人工管理、纸质记录等方式,博客管理系统能够更加快捷、高效地对博客进行增删改查的操作,能及时有效地掌握博客信息,具有极强的实用价值。
  2. 心得体会 在这次课程设计中,我用所学网页设计、Java与数据库的相关知识实现博客管理员增加博客、删除博客、修改博客以及查询博客等功能,其中也运用到了到程序代码分层的思想。经过设计,加强了自己之前所学的HTML知识,也让自己懂得了程序设计思想的关键所在。同时,经过本学期的JSP课程设计,我认识到了自己学习和上机中的缺陷,还要主动了解和掌握更多的知识。本次课程设计,不仅提高了我的逻辑思考、实践操作的能力, 而且也增强了我的团队合作意识。更重要的是,我还学会了很多程序学习的好方法,这是一笔宝贵的财富。此外也使我了解到做好一个完整的系统,首先要先对系统的整体框架进行建立,然后分步进行各个系统的实现。面对日益激烈的社会工作岗位竞争,我们要不断地学习、上机,反复扩充自己的专业课知识。最重要的是要有一个清晰的架构,最后进行一系列的分析,最后在进行整个系统的实现。

参考文献

  • [1] 陈庆荣.基于B/S模式应用的研究与设计[J].福建电脑,2018,34(02):125-126+67.
  • [2] 崔兰超,韩晓丹.基于B/S结构的学校综合管理系统的开发[J].电脑编程技巧与维护,2018(02):87-89.
  • [3] 王高亮.基于Eclipse的实验室设备管理系统设计[J].现代计算机(专业版),2012(10):57-60.
  • [4] 秦园园关于Tomcat的一些问题探讨[J].山西科技,2011,26(04):40-41.
  • [5] 吴小青.JSP+TOMCAT+MYSQL开源软件整合配置初探——以揭阳职业技术学院博客馆网站服务器配置为例[J].齐齐哈尔大学学报(自然科学版),2012,28(04):66-69.
  • [6] 魏强.JSP技术简介及发展前景[J].装备制造技术,2008(07):118-119+124.
  • [7] 常大俊.基于MySQL数据库结构设计[J].信息安全与技术,2015,6(09):55-57.
  • [8] 张彤,赵丽.移动医疗App功能模块的比较分析与发展建议[J].廊坊师范学院学报(自然科学版),2016,16(02):28-31.
  • [9] 王绵金,郑海涛,范耀明.黑盒测试用例设计方法探究[J].信息与电脑(理论版),2016(06):127-128.
  • [10] 黄玉春.浅谈下一代Web开发标准的核心技术—HTML5[J].计算机时代,2015(04):3-5.

致谢

在这篇课程设计的完成中,我最尊敬的指导教师给了我很大的帮助,他不断地支持和鼓励一直伴随着我本阶段的学习工作和生活。课程设计选题、构思、查阅文献、修改、定稿,每一步都凝聚着导师的心血。他以他严谨的治学态度广博的学识宽广的视野敏锐的观察力给我在学习研究上的指导,使我的学习研究工作受益匪浅。同时老师还经常教导我们怎样为人处世,他勤奋的工作作风,遇事勤于思考的学习和工作态度,积极进取的勇气和魄力给我的人生带来了宝贵的精神财富。在此,我深切和怀着十分感激的心情,向老师表达我最真挚的感谢。在同时我也要感谢我的同事和朋友,在我课程设计过程中对我的鼓励和支持!在漫长的学习生涯中,感谢我的父母在精神上的理解与支持和在生活上的照顾。我的课程设计凝聚着他们的长期支持,我对他们在我成长道路上所付出的艰辛和汗水致以真诚的感谢! 值此课程设计完成之际,再次向所有关心、支持、帮助我的老师、同学和朋友们表示我衷心的感谢。

GNU GENERAL PUBLIC LICENSE Version 3, 29 June 2007 Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/> Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Preamble The GNU General Public License is a free, copyleft license for software and other kinds of works. The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply it to your programs, too. When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces of it in new free programs, and that you know you can do these things. To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others. For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights. Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission to copy, distribute and/or modify it. For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions. Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is fundamentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for individuals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If such problems arise substantially in other domains, we stand ready to extend this provision to those domains in future versions of the GPL, as needed to protect the freedom of users. Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the GPL assures that patents cannot be used to render the program non-free. The precise terms and conditions for copying, distribution and modification follow. TERMS AND CONDITIONS 0. Definitions. "This License" refers to version 3 of the GNU General Public License. "Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks. "The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or organizations. To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work. A "covered work" means either the unmodified Program or a work based on the Program. To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copyright law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available to the public, and in some countries other activities as well. To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network, with no transfer of a copy, is not conveying. An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in the list meets this criterion. 1. Source Code. The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work. A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a particular programming language, one that is widely used among developers working in that language. The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Component, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, window system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code interpreter used to run it. The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is specifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work. The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source. The Corresponding Source for a work in source code form is that same work. 2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output, given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law. You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material outside their relationship with you. Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary. 3. Protecting Users' Legal Rights From Anti-Circumvention Law. No covered work shall be deemed part of an effective technological measure under any applicable law fulfilling obligations under article 11 of the WIPO copyright treaty adopted on 20 December 1996, or similar laws prohibiting or restricting circumvention of such measures. When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures. 4. Conveying Verbatim Copies. You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program. You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee. 5. Conveying Modified Source Versions. You may convey a work based on the Program, or the modifications to produce it from the Program, in the form of source code under the terms of section 4, provided that you also meet all of these conditions: a) The work must carry prominent notices stating that you modified it, and giving a relevant date. b) The work must carry prominent notices stating that it is released under this License and any conditions added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices". c) You must license the entire work, as a whole, under this License to anyone who comes into possession of a copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole of the work, and all its parts, regardless of how they are packaged. This License gives no permission to license the work in any other way, but it does not invalidate such permission if you have separately received it. d) If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make them do so. A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not combined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggregate does not cause this License to apply to the other parts of the aggregate. 6. Conveying Non-Source Forms. You may convey a covered work in object code form under the terms of sections 4 and 5, provided that you also convey the machine-readable Corresponding Source under the terms of this License, in one of these ways: a) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by the Corresponding Source fixed on a durable physical medium customarily used for software interchange. b) Convey the object code in, or embodied in, a physical product (including a physical distribution medium), accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or customer support for that product model, to give anyone who possesses the object code either (1) a copy of the Corresponding Source for all the software in the product that is covered by this License, on a durable physical medium customarily used for software interchange, for a price no more than your reasonable cost of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a network server at no charge. c) Convey individual copies of the object code with a copy of the written offer to provide the Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you received the object code with such an offer, in accord with subsection 6b. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer equivalent access to the Corresponding Source in the same way through the same place at no further charge. You need not require recipients to copy the Corresponding Source along with the object code. If the place to copy the object code is a network server, the Corresponding Source may be on a different server (operated by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy these requirements. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the object code and Corresponding Source of the work are being offered to the general public at no charge under subsection 6d. A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the object code work. A "User Product" is either (1) a "consumer product", which means any tangible personal property which is normally used for personal, family, or household purposes, or (2) anything designed or sold for incorporation into a dwelling. In determining whether a product is a consumer product, doubtful cases shall be resolved in favor of coverage. For a particular product received by a particular user, "normally used" refers to a typical or common use of that class of product, regardless of the status of the particular user or of the way in which the particular user actually uses, or expects or is expected to use, the product. A product is a consumer product regardless of whether the product has substantial commercial, industrial or non-consumer uses, unless such uses represent the only significant mode of use of the product. "Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified versions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued functioning of the modified object code is in no case prevented or interfered with solely because modification has been made. If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized), the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM). The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modification itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network. Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying. 7. Additional Terms. "Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions. When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission. Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms: a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or d) Limiting the use for publicity purposes of names of licensors or authors of the material; or e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors. All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying. If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms. Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way. 8. Termination. You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11). However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior to 60 days after the cessation. Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means, this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after your receipt of the notice. Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10. 9. Acceptance Not Required for Having Copies. You are not required to accept this License in order to receive or run a copy of the Program. Ancillary propagation of a covered work occurring solely as a consequence of using peer-to-peer transmission to receive a copy likewise does not require acceptance. However, nothing other than this License grants you permission to propagate or modify any covered work. These actions infringe copyright if you do not accept this License. Therefore, by modifying or propagating a covered work, you indicate your acceptance of this License to do so. 10. Automatic Licensing of Downstream Recipients. Each time you convey a covered work, the recipient automatically receives a license from the original licensors, to run, modify and propagate that work, subject to this License. You are not responsible for enforcing compliance by third parties with this License. An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organizations. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts. You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, royalty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it. 11. Patents. A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called the contributor's "contributor version". A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner consistent with the requirements of this License. Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale, import and otherwise run, modify and propagate the contents of its contributor version. In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express permission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commitment not to enforce a patent against the party. If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that country that you have reason to believe are valid. If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent license you grant is automatically extended to all recipients of the covered work and works based on it. A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007. Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under applicable patent law. 12. No Surrender of Others' Freedom. If conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot convey a covered work so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not convey it at all. For example, if you agree to terms that obligate you to collect a royalty for further conveying from those to whom you convey the Program, the only way you could satisfy both those terms and this License would be to refrain entirely from conveying the Program. 13. Use with the GNU Affero General Public License. Notwithstanding any other provision of this License, you have permission to link or combine any covered work with a work licensed under version 3 of the GNU Affero General Public License into a single combined work, and to convey the resulting work. The terms of this License will continue to apply to the part which is the covered work, but the special requirements of the GNU Affero General Public License, section 13, concerning interaction through a network will apply to the combination as such. 14. Revised Versions of this License. The Free Software Foundation may publish revised and/or new versions of the GNU General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later version" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software Foundation. If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program. Later license versions may give you additional or different permissions. However, no additional obligations are imposed on any author or copyright holder as a result of your choosing to follow a later version. 15. Disclaimer of Warranty. THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 16. Limitation of Liability. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. 17. Interpretation of Sections 15 and 16. If the disclaimer of warranty and limitation of liability provided above cannot be given local legal effect according to their terms, reviewing courts shall apply local law that most closely approximates an absolute waiver of all civil liability in connection with the Program, unless a warranty or assumption of liability accompanies a copy of the Program in return for a fee. END OF TERMS AND CONDITIONS How to Apply These Terms to Your New Programs If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms. To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively state the exclusion of warranty; and each file should have at least the "copyright" line and a pointer to where the full notice is found. <one line to give the program's name and a brief idea of what it does.> Copyright (C) <year> <name of author> This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see <http://www.gnu.org/licenses/>. Also add information on how to contact you by electronic and paper mail. If the program does terminal interaction, make it output a short notice like this when it starts in an interactive mode: <program> Copyright (C) <year> <name of author> This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details. The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, your program's commands might be different; for a GUI interface, you would use an "about box". You should also get your employer (if you work as a programmer) or school, if any, to sign a "copyright disclaimer" for the program, if necessary. For more information on this, and how to apply and follow the GNU GPL, see <http://www.gnu.org/licenses/>. The GNU General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License. But first, please read <http://www.gnu.org/philosophy/why-not-lgpl.html>.

简介

前后端分离的个人博客管理系统,使用ajax和servlet进行数据交互。 展开 收起
GPL-3.0
取消

发行版

暂无发行版

贡献者 (1)

全部

近期动态

接近3年前推送了新的提交到 master 分支,e4bea1b...5f8dd00
接近3年前推送了新的提交到 master 分支,d72bf58...e4bea1b
接近3年前推送了新的提交到 master 分支,644dbbb...d72bf58
接近3年前推送了新的提交到 master 分支,a50eac5...644dbbb
接近3年前推送了新的提交到 master 分支,31db6c6...a50eac5
加载更多
不能加载更多了
马建仓 AI 助手
尝试更多
代码解读
代码找茬
代码优化
Java
1
https://gitee.com/hehe8/myblog.git
git@gitee.com:hehe8/myblog.git
hehe8
myblog
前后端分离的个人博客管理系统
master

搜索帮助