yejunhui2008的专栏

iBatis是又一个O/R Mapping解决方案，j2ee的O/R方案真是多，和Hibernate相比，iBatis最大的特点就是小巧，上手很快。如果你不需要太多复杂的功能，iBatis是能满足你的要求又足够灵活的最简单的解决方案。

《Java设计模式》面向有一定Java语言基础和一定编程经验的读者，重点探讨在Java程序设计中怎样使用著名的23个设计模式。《Java设计模式》的目的是让读者不仅学习怎样在软件设计中使用好设计模式，更重要的是让读者通过学习使用设计模式深刻地理解面向对象的设计思想，以便更好地使用面向对象语言解决设计中的诸多问题。

Apache,Tomcat集群和负载均衡

关于java开发中经常可能会碰到的一些疑惑。本书作一一详解。

J2EE provides many architectural choices. J2EE also offers many component types (such as servlets, EJBs, JSP pages, and servlet filters), and J2EE application servers provide many additional services. While this array of options enables us to design the best solution for each problem, it also poses dangers. J2EE developers can be overwhelmed by the choices on offer, or can be tempted to use infrastructure inappropriate to the problem in hand, simply because it's available. In this book I aim to help professional J2EE developers and architects make the appropriate choices to deliver high-quality solutions on time and within budget. I'll focus on those features of J2EE that have proven most useful for solving the commonest problems in enterprise software development. In this chapter, we discuss the high-level choices in developing a J2EE architecture, and how to decide which parts of J2EE to use to solve real problems. We'll look at: ❑ Distributed and non-distributed applications, and how to choose which model is appropriate ❑ The implications for J2EE design of changes in the EJB 2.0 specification and the emergence of web services ❑ When to use EJB ❑ Data access strategies for J2EE applications ❑ Four J2EE architectures, and how to choose between them ❑ Web tier design ❑ Portability issues

J2EE provides many architectural choices. J2EE also offers many component types (such as servlets, EJBs, JSP pages, and servlet filters), and J2EE application servers provide many additional services. While this array of options enables us to design the best solution for each problem, it also poses dangers. J2EE developers can be overwhelmed by the choices on offer, or can be tempted to use infrastructure inappropriate to the problem in hand, simply because it's available. In this book I aim to help professional J2EE developers and architects make the appropriate choices to deliver high-quality solutions on time and within budget. I'll focus on those features of J2EE that have proven most useful for solving the commonest problems in enterprise software development. In this chapter, we discuss the high-level choices in developing a J2EE architecture, and how to decide which parts of J2EE to use to solve real problems. We'll look at: ❑ Distributed and non-distributed applications, and how to choose which model is appropriate ❑ The implications for J2EE design of changes in the EJB 2.0 specification and the emergence of web services ❑ When to use EJB ❑ Data access strategies for J2EE applications ❑ Four J2EE architectures, and how to choose between them ❑ Web tier design ❑ Portability issues

J2EE provides many architectural choices. J2EE also offers many component types (such as servlets, EJBs, JSP pages, and servlet filters), and J2EE application servers provide many additional services. While this array of options enables us to design the best solution for each problem, it also poses dangers. J2EE developers can be overwhelmed by the choices on offer, or can be tempted to use infrastructure inappropriate to the problem in hand, simply because it's available. In this book I aim to help professional J2EE developers and architects make the appropriate choices to deliver high-quality solutions on time and within budget. I'll focus on those features of J2EE that have proven most useful for solving the commonest problems in enterprise software development. In this chapter, we discuss the high-level choices in developing a J2EE architecture, and how to decide which parts of J2EE to use to solve real problems. We'll look at: ❑ Distributed and non-distributed applications, and how to choose which model is appropriate ❑ The implications for J2EE design of changes in the EJB 2.0 specification and the emergence of web services ❑ When to use EJB ❑ Data access strategies for J2EE applications ❑ Four J2EE architectures, and how to choose between them ❑ Web tier design ❑ Portability issues

J2EE provides many architectural choices. J2EE also offers many component types (such as servlets, EJBs, JSP pages, and servlet filters), and J2EE application servers provide many additional services. While this array of options enables us to design the best solution for each problem, it also poses dangers. J2EE developers can be overwhelmed by the choices on offer, or can be tempted to use infrastructure inappropriate to the problem in hand, simply because it's available. In this book I aim to help professional J2EE developers and architects make the appropriate choices to deliver high-quality solutions on time and within budget. I'll focus on those features of J2EE that have proven most useful for solving the commonest problems in enterprise software development. In this chapter, we discuss the high-level choices in developing a J2EE architecture, and how to decide which parts of J2EE to use to solve real problems. We'll look at: ❑ Distributed and non-distributed applications, and how to choose which model is appropriate ❑ The implications for J2EE design of changes in the EJB 2.0 specification and the emergence of web services ❑ When to use EJB ❑ Data access strategies for J2EE applications ❑ Four J2EE architectures, and how to choose between them ❑ Web tier design ❑ Portability issues

mod_jk-1.2.28-httpd-2.2.3.so

apache_2.2.4-win32-x86-no_ssl.msi

J2EE provides many architectural choices. J2EE also offers many component types (such as servlets, EJBs, JSP pages, and servlet filters), and J2EE application servers provide many additional services. While this array of options enables us to design the best solution for each problem, it also poses dangers. J2EE developers can be overwhelmed by the choices on offer, or can be tempted to use infrastructure inappropriate to the problem in hand, simply because it's available. In this book I aim to help professional J2EE developers and architects make the appropriate choices to deliver high-quality solutions on time and within budget. I'll focus on those features of J2EE that have proven most useful for solving the commonest problems in enterprise software development. In this chapter, we discuss the high-level choices in developing a J2EE architecture, and how to decide which parts of J2EE to use to solve real problems. We'll look at: ❑ Distributed and non-distributed applications, and how to choose which model is appropriate ❑ The implications for J2EE design of changes in the EJB 2.0 specification and the emergence of web services ❑ When to use EJB ❑ Data access strategies for J2EE applications ❑ Four J2EE architectures, and how to choose between them ❑ Web tier design ❑ Portability issues

Apache,Tomcat集群和负载均衡包括了apache-tomcat-5.5.29.zip，apache_2.2.4-win32-x86-no_ssl.msi，mod_jk-1.2.28-httpd-2.2.3.so，ApacheTomcat整合文档.doc，Apache,Tomcat集群和负载均衡教程.doc，Tomcat负载均衡.pdf