??xml version="1.0" encoding="utf-8" standalone="yes"?>HSQL 学习(fn)W记
1.1. (tng) (tng) (tng) (tng) 学习(fn)目的
本文档是针对hSQL 数据库方面的基础学习(fn)Qؓ(f)?jin)ə目l成员能够达C用hSQL 数据库的目的?br />1.2. (tng) (tng) (tng) (tng) 培训对象
开发h?br />1.3. (tng) (tng) (tng) (tng) 常用词及(qing)W号说明
常用词:(x)
hsqlQ一U免费的跨^台的数据库系l?br />E:\hsqldbQ表C是在dos 命o(h)H口下面
1.4. (tng) (tng) (tng) (tng) 参考信?br />doc\guide\guide.pdf
2. (tng) (tng) (tng) (tng) HSQL
2.1. (tng) (tng) (tng) (tng) HSQL q行工具
java -cp ../lib/hsqldb.jar org.hsqldb.util.DatabaseManager
注意hsqldb.jar 文g的文件\?最好能攑ֈclasspath 里面,或者放到当前\径下.
java -cp hsqldb.jar org.hsqldb.util.DatabaseManager
2.2. (tng) (tng) (tng) (tng) q行数据?br />启动方式: Server Modes and
In-Process Mode (also called Standalone Mode).
一个test 数据库会(x)包含如下文g:
?test.properties
?test.script
?test.log
?test.data
?test.backup
test.properties 文g包含关于数据库的一般设|?
test.script (tng) (tng) 文g包含表和其它数据?插入没有~存表的数据.
test.log 文g包含当前数据库的变更.
test.data 文g包含~存表的数据
test.backup 文g是最q持久化状态的表的数据文g的压~备份文?br />所有以上这个文仉是必要的,不能被删?如果数据库没有缓存表,test.data 和test.backup 文g不?x)存?另外,除了(jin)以上文gHSQLDB 数据库可以链接到M文本文g,比如cvs 文g.
当操作test 数据库的时? test.log 用于保存数据的变? 当正常SHUTDOWN,q个文g被删除. 否则(不是正常shutdown),q个文g用于再ơ启动的时?重做q些变更.test.lck 文g也用于记录打开的数据库的事? 正常SHUTDOWN,文g也被删除.在一些情况下,test.data.old 文g?x)被创?q删除以前的.
2.3. (tng) (tng) (tng) (tng) Server Mode
java -cp ../lib/hsqldb.jar org.hsqldb.Server -database.0 file:mydb -dbname.0 xdb
命o(h)行方?
启动数据,数据库文件mydb,数据库名Uxdb
也可以在 server.properties 文g中定义启动的数据?最?0?br />例如: server.properties:
server.database.0=file:E:/hsqldb/data/mydb
server.dbname.0=xdb
server.database.1=file:E:/hsqldb/data/testdb
server.dbname.1=testdb
server.database.2=mem:adatabase
server.dbname.2=quickdb
启动命o(h): java -cp ../lib/hsqldb.jar org.hsqldb.Server
q行l果如下
java 试E序:
package test;
import junit.framework.TestCase;
import java.sql.Connection;
import java.sql.DriverManager;
import java.sql.ResultSet;
import java.sql.SQLException;
import java.sql.Statement;
public class TestConnect extends TestCase {
(tng) (tng) (tng) (tng) Connection connection;
(tng) (tng) (tng) (tng) protected void setUp()
(tng) (tng) (tng) (tng) { (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) try {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) Class.forName("org.hsqldb.jdbcDriver" );
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) connection = DriverManager.getConnection("jdbc:hsqldb:hsql://localhost/xdb","sa","");
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) } catch (Exception e) {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) // TODO Auto-generated catch block
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) e.printStackTrace();
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) }
(tng) (tng) (tng) (tng) }
(tng) (tng) (tng) (tng) public void testselect()
(tng) (tng) (tng) (tng) {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) Statement stmt=null;
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) ResultSet rs=null;
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) try {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) stmt = connection.createStatement();
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) String sql ="select * from test";
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) rs=stmt.executeQuery( sql);
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) while(rs.next() )
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) System.out.println("id="+rs.getString("id"));
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) System.out.println("name="+rs.getString("name"));
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) }
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) } catch (SQLException e) {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) // TODO Auto-generated catch block
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) e.printStackTrace();
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) }
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) finally
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) try {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) rs.close() ;
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) stmt.close();
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) } catch (SQLException e) {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) // TODO Auto-generated catch block
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) e.printStackTrace();
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) } (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) } (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) }
(tng) (tng) (tng) (tng) protected void tearDown()
(tng) (tng) (tng) (tng) {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) try {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) connection.close();
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) } catch (Exception e) {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) // TODO Auto-generated catch block
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) e.printStackTrace();
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) }
(tng) (tng) (tng) (tng) }
}
以上在eclipse 中测试通过.
2.4. (tng) (tng) (tng) (tng) In-Process (Standalone) Mode
不需要启动server
connection = DriverManager.getConnection("jdbc:hsqldb:file:E:/hsqldb/data/mydb","sa","");
q样可以连接数据库?br />只能在一个jvm 中用,不能在多个jvm 中用?br />q种模式是在相同的jvm 下作Z的应用程序的一部分Q运行数据库引擎。对大多数应用程序,q种模式q行?x)相当快Q作为数据,不需要{换和|络传输?br />
主要的缺点就是不可能从外面的应用E序讉K到默认数据库Q因此当你的应用q行时候,你不能通过别的工具(g)查数据库内容。在1.8.0 版本?你可以在相同jvm 中的U程中运行数据库初始化,q提供外面访问你的进E内数据库?br /> (tng) (tng) (tng) (tng) 推荐在开发应用中使用q种方式?br />q接Ԍ(x)
Windows: DriverManager.getConnection("jdbc:hsqldb:file:E:/hsqldb/data/mydb","sa","");
Unix: DriverManager.getConnection("jdbc:hsqldb:file:/opt/db/testdb","sa","");
2.5. (tng) (tng) (tng) (tng) Memory-Only Databases
当随卌问内存,数据库不固定Ӟ可以采用内存的方式运行数据库Q由于没有数据写到硬盘(sh)Q这U方式用在应用数据和applets 和特D应用的内部q程中用,URLQ?br />
Connection c = DriverManager.getConnection("jdbc:hsqldb:mem:aname", "sa", "");
2.6. (tng) (tng) (tng) (tng) Using Multiple Databases in One JVM
2.7. (tng) (tng) (tng) (tng) Different Types of Tables
HSQLDB 支持 TEMP 表和三种cd的持久表QMEMORY ? CACHED 表,TEXT表)(j)
当?CREATE TABLE (tng) (tng) 命o(h)ӞMemory 表时默认cdQ它们的数据整体保存在内存当中,但是M改变它们的结构或者内容,它们?x)被写?lt;dbname>.script 文g中。这个脚本文件在数据库下一ơ打开的时候被对出Q内存表重新被创建内容,根temp 表不同,内存表时持久化的?br />
CACHED 表通过CREATE CACHED TABLE 命o(h)建立. 只有部分的它们的数据或者烦(ch)引被保存在内存(sh)Q允许大表占用几癑օ的内存空间。例外一个优点,在数据库引擎中,启动大量数据的缓存表需要花费少量的旉Q缺Ҏ(gu)减慢?jin)运行和使用Hsqldb 的速度。表相对的时候,不要使用cache 表,在小表中使用内存数据库?br />
从版?1.7.0 以后Q支持text 表,使用 CSV (Comma Separated Value) (tng) (tng) 或者其它分隔符文本文g作ؓ(f)它们的数据源。你可以Ҏ(gu)指定一个存在的CSV 文gQ例如从其它的数据或者程序中导出文gQ作为TXT 表的数据源?同时,你可以指定一个空文gQ通过数据库引擎填充数据。TEXT 表将比cache 表更加效率高。Text 表可以指向不同的数据文g?br />
* memory-only databases 数据库只支持memory 表和cache 表,不支持text 表?br />2.8. (tng) (tng) (tng) (tng) U束和烦(ch)?br />HSQLDB 支持 PRIMARY KEY, NOT NULL, UNIQUE, CHECK and FOREIGN KEY U束.
3. (tng) (tng) (tng) (tng) sql 命o(h)
3.1. (tng) (tng) (tng) (tng) sql 支持
select top 1 * from test;
select limit 0 2 * from test;
DROP TABLE test IF EXISTS;
3.2. (tng) (tng) (tng) (tng) Constraints and Indexes
dU束QPRIMARY KEY
唯一U束Q?br />唯一索引Q?br />外健Q?br />CREATE TABLE child(c1 INTEGER, c2 VARCHAR, FOREIGN KEY (c1, c2) REFERENCES parent(p1, p2));
3.3. (tng) (tng) (tng) (tng) 索引和查询速度
索引提高查询速度Q比提高排序速度?br />d和唯一所列自动创建烦(ch)引,否则需要自己创建CREATE INDEX command?br />索引Q?唯一索引和非唯一索引
多列的烦(ch)引,如果只是使用后面的,不用第一个,不?x)条查询速度?br />
(TB is a very large table with only a few rows where TB.COL3 = 4)
SELECT * FROM TA JOIN TB ON TA.COL1 = TB.COL2 AND TB.COL3 = 4;
SELECT * FROM TB JOIN TA ON TA.COL1 = TB.COL2 AND TB.COL3 = 4;(faster)
原因?TB.COL3 可以被快速的估计,如果TB 表放到前?index on TB.COL3):
一般规则是把羃?yu)条件的列的表放在前?br />
3.4. (tng) (tng) (tng) (tng) 使用where q是join
使用 WHERE (tng) (tng) 条g链接表可能会(x)降低q行速度.
下面的例子将?x)比较?即使用?jin)?ch)?
(tng) (tng) (tng) (tng) SELECT ... FROM TA, TB, TC WHERE TC.COL3 = TA.COL1 AND TC.COL3=TB.COL2 AND TC.COL4 = 1
q个查询隐含TA.COL1 = TB.COL2 ,但是没有直接讑֮q个条g.如果 TA ?TB 每个表都包含100 条记?10000 l合和 TC 兌,用于TCq个列的条g,管有烦(ch)引在q个列上.使用JOIN 关键? 在组合TC 之前,TA.COL1 = TB.COL2 条g直接q羃?yu)组?TA ?TB 的行? 在运行大数据量的表的l果?会(x)很快:
(tng) (tng) (tng) (tng) SELECT ... FROM TA JOIN TB ON TA.COL1 = TB.COL2 JOIN TC ON TB.COL2 = TC.COL3 WHERE TC.COL4 = 1
q个查询可以提高?sh)大步,如果改变表的序, 所?TC.COL1 = 1 最先?q样更小的集合将l合在一?
(tng) (tng) (tng) (tng) SELECT ... FROM TC JOIN TB ON TC.COL3 = TB.COL2 JOIN TA ON TC.COL3 = TA.COL1 WHERE TC.COL4 = 1
以上例子,数据引擎自动应用于TC.COL4 = 1 l合的集合于其它表兌. Indexes TC.COL4, TB.COL2 (tng) (tng) TA.COL1 都将使用索引,提高查询速度.
3.5. (tng) (tng) (tng) (tng) Subqueries and Joins
使用join 和调整表的顺序提高效?
例如:, W二个查询的速度更快一?TA.COL1 和TB.COL3都有索引):
Example 2.2. Query comparison
(tng) (tng) (tng) (tng) SELECT ... FROM TA WHERE TA.COL1 = (SELECT MAX(TB.COL2) FROM TB WHERE TB.COL3 = 4)
(tng) (tng) (tng) (tng) SELECT ... FROM (SELECT MAX(TB.COL2) C1 FROM TB WHERE TB.COL3 = 4) T2 JOIN TA ON TA.COL1 = T2.C1
W二个查询将 MAX(TB.COL2) 与一个单记录表相兌. q用TA.COL1索引,q将变得非常? W一个查询是?TA 表中的每一条记录不断地与MAX(TB.COL2)匚w.
3.6. (tng) (tng) (tng) (tng) 数据cd
TINYINT, SMALLINT, INTEGER, BIGINT, NUMERIC and DECIMAL (without a decimal point) are supported integral types and map to byte, short, int, long and BigDecimal in Java.
Integral Types:
TINYINT, SMALLINT, INTEGER, BIGINT, NUMERIC and DECIMAL
Other Numeric Types:
REAL, FLOAT or DOUBLE
Bit and Boolean Types:
(tng) (tng) (tng) (tng) BOOLEAN: UNDEFINED,TRUE,FALSE (tng) (tng)
NULL values are treated as undefined.
Storage and Handling of Java Objects
Sequences and Identity
Identity Auto-Increment Columns:
The next IDENTITY value to be used can be set with the
ALTER TABLE ALTER COLUMN <column name> RESTART WITH <new value>;
Sequences:
SELECT NEXT VALUE FOR mysequence, col1, col2 FROM mytable WHERE ...
(tng) (tng) (tng) (tng)
3.7. (tng) (tng) (tng) (tng) 事务问题:
SET PROPERTY "sql.tx_no_multi_rewrite" TRUE
4. (tng) (tng) (tng) (tng) Connections
通用驱动jdbc:hsqldb: (tng) (tng) 下列协议标识(mem: file: res: hsql: http: hsqls: https:)
Table 4.1. Hsqldb URL Components
Driver and Protocol (tng) (tng) (tng) (tng) Host and Port (tng) (tng) (tng) (tng) Database
jdbc:hsqldb:mem:
(tng) (tng) (tng) (tng) not available (tng) (tng) (tng) (tng) accounts
jdbc:hsqldb:mem:.
jdbc:hsqldb:file:
(tng) (tng) (tng) (tng) not available (tng) (tng) (tng) (tng) mydb
/opt/db/accounts
C:/data/mydb
数据库\?
jdbc:hsqldb:res:
(tng) (tng) (tng) (tng) not available (tng) (tng) (tng) (tng) /adirectory/dbname
jars files are accessed in Java programs. The /adirectory above stands for a directory in one of the jars.
jdbc:hsqldb:hsql:
jdbc:hsqldb:hsqls:
jdbc:hsqldb:http:
jdbc:hsqldb:https:
(tng) (tng) (tng) (tng) //localhost
//192.0.0.10:9500
//dbserver.somedomain.com
(tng) (tng) (tng) (tng) /an_alias
/enrollments
/quickdb
别名在server.properties or webserver.properties文g中指?br /> (tng) (tng) (tng) (tng) database.0=file:/opt/db/accounts
(tng) (tng) (tng) (tng) dbname.0=an_alias
(tng) (tng) (tng) (tng) database.1=file:/opt/db/mydb
(tng) (tng) (tng) (tng) dbname.1=enrollments
(tng) (tng) (tng) (tng) database.2=mem:adatabase
(tng) (tng) (tng) (tng) dbname.2=quickdb
In the example below, the database files lists.* in the /home/dbmaster/ directory are associated with the empty alias:
(tng) (tng) (tng) (tng) database.3=/home/dbmaster/lists
(tng) (tng) (tng) (tng) dbname.3=
4.1. (tng) (tng) (tng) (tng) Connection properties
Connection properties are specified either by establishing the connection via the:
(tng) (tng) (tng) (tng) DriverManager.getConnection (String url, Properties info);
method call, or the property can be appended to the full Connection URL.
Table 4.2. Connection Properties
get_column_name (tng) (tng) (tng) (tng) true (tng) (tng) (tng) (tng) column name in ResultSet
This property is used for compatibility with other JDBC driver implementations. When true (the default), ResultSet.getColumnName(int c) returns the underlying column name
When false, the above method returns the same value as ResultSet.getColumnLabel(int column) Example below:
(tng) (tng) (tng) (tng) jdbc:hsqldb:hsql://localhost/enrollments;get_column_name=false
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng)
When a ResultSet is used inside a user-defined stored procedure, the default, true, is always used for this property.
ifexists (tng) (tng) (tng) (tng) false (tng) (tng) (tng) (tng) connect only if database already exists
Has an effect only with mem: and file: database. When true, will not create a new database if one does not already exist for the URL.
When false (the default), a new mem: or file: database will be created if it does not exist.
Setting the property to true is useful when troubleshooting as no database is created if the URL is malformed. Example below:
(tng) (tng) (tng) (tng) jdbc:hsqldb:file:enrollments;ifexists=true
shutdown (tng) (tng) (tng) (tng) false (tng) (tng) (tng) (tng) shut down the database when the last connection is closed
This mimics the behaviour of 1.7.1 and older versions. When the last connection to a database is closed, the database is automatically shut down. The property takes effect only when the first connection is made to the database. This means the connection that opens the database. It has no effect if used with subsequent, simultaneous connections.
This command has two uses. One is for test suites, where connections to the database are made from one JVM context, immediately followed by another context. The other use is for applications where it is not easy to configure the environment to shutdown the database. Examples reported by users include web application servers, where the closing of the last connection conisides with the web app being shut down.
4.2. (tng) (tng) (tng) (tng) Properties Files
大小写敏?(e.g. server.silent=FALSE will have no effect, but server.silent=false will work).
属性文件和讑֮存储如下 :
Table 4.3. Hsqldb Server Properties Files
File Name (tng) (tng) (tng) (tng) Location (tng) (tng) (tng) (tng) Function
server.properties (tng) (tng) (tng) (tng) the directory where the command to run the Server class is issued (tng) (tng) (tng) (tng) settings for running HSQLDB as a database server communicating with the HSQL protocol
webserver.properties (tng) (tng) (tng) (tng) the directory where the command to run the WebServer class is issued (tng) (tng) (tng) (tng) settings for running HSQLDB as a database server communicating with the HTTP protocol
<dbname>.properties (tng) (tng) (tng) (tng) the directory where all the files for a database are located (tng) (tng) (tng) (tng) settings for each particular database
Properties files for running the servers are not created automatically. You should create your own files that contain server.property=value pairs for each property.
4.2.1. (tng) (tng) (tng) (tng) Server and Web Server Properties
server.properties and webserver.properties 文g支持如下讑֮:
Table 4.4. Property File Properties
Value (tng) (tng) (tng) (tng) Default (tng) (tng) (tng) (tng) Description
server.database.0 (tng) (tng) (tng) (tng) test (tng) (tng) (tng) (tng) the path and file name of the first database file to use
server.dbname.0 (tng) (tng) (tng) (tng) "" (tng) (tng) (tng) (tng) lowercase server alias for the first database file
server.urlid.0 (tng) (tng) (tng) (tng) NONE (tng) (tng) (tng) (tng) SqlTool urlid used by UNIX init script. (This property is not used if your are running Server/Webserver on a platform other than UNIX, or of you are not using our UNIX init script).
server.silent (tng) (tng) (tng) (tng) true (tng) (tng) (tng) (tng) no extensive messages displayed on console
server.trace (tng) (tng) (tng) (tng) false (tng) (tng) (tng) (tng) JDBC trace messages displayed on console
In 1.8.0, 每个服务器支持同时启?0个不同的数据? The server.database.0 property defines the filename / path whereas the server.dbname.0 defines the lowercase alias used by clients to connect to that database. The digit 0 is incremented for the second database and so on. Values for the server.database.{0-9} property can use the mem:, file: or res: prefixes and properties as discussed above under CONNECTIONS. For example,
(tng) (tng) (tng) (tng) database.0=mem:temp;sql.enforce_strict_size=true;
Values specific to server.properties are:
Table 4.5. Server Property File Properties
Value (tng) (tng) (tng) (tng) Default (tng) (tng) (tng) (tng) Description
server.port (tng) (tng) (tng) (tng) 9001 (tng) (tng) (tng) (tng) TCP/IP port used for talking to clients. All databases are served on the same port.
server.no_system_exit (tng) (tng) (tng) (tng) true (tng) (tng) (tng) (tng) no System.exit() call when the database is closed
Values specific to webserver.properties are:
Table 4.6. WebServer Property File Properties
Value (tng) (tng) (tng) (tng) Default (tng) (tng) (tng) (tng) Description
server.port (tng) (tng) (tng) (tng) 80 (tng) (tng) (tng) (tng) TCP/IP port used for talking to clients
server.default_page (tng) (tng) (tng) (tng) index.html (tng) (tng) (tng) (tng) the default web page for server
server.root (tng) (tng) (tng) (tng) ./ (tng) (tng) (tng) (tng) the location of served pages
.<extension> (tng) (tng) (tng) (tng) ? (tng) (tng) (tng) (tng) multiple entries such as .html=text/html define the mime types of the static files served by the web server. See the source for WebServer.java for a list.
All the above values can be specified on the command line to start the server by omitting the server. prefix.
5. (tng) (tng) (tng) (tng) SqlTool
Mem 数据?
E:\hsqldb>java -jar ./lib/hsqldb.jar mem
Hsql Server:
(前提是xdb server 已经启动):
(java -cp ../lib/hsqldb.jar org.hsqldb.Server -database.0 file:mydb -dbname.0 xdb)
java -jar ./hsqldb.jar xdb
]]>
DbUnit?/strong>
Z赖于其他外部pȝQ如数据库或其他接口Q的代码~写单元试是一件很困难的工作。在q种情况下,有效的单元必隔L试对象和外部依赖Q以便管理测试对象的状态和行ؓ(f)?/p>
使用mock object对象Q是隔离外部依赖的一个有效方法。如果我们的试对象是依赖于DAO的代码,mock object技术很方便。但如果试对象变成?jin)DAO本nQ又如何q行单元试呢?
开源的DbUnit目Qؓ(f)以上的问题提供了(jin)一个相当优雅的解决Ҏ(gu)。用DbUnitQ开发h员可以控制测试数据库的状态。进行一个DAO单元试之前QDbUnit为数据库准备好初始化数据Q而在试l束ӞDbUnit?x)把数据库状态恢复到试前的状态?/p>
下面的例子用DbUnit为iBATIS SqlMap的DAO~写单元试?/p>
准备试数据
首先Q要为单元测试准备数据。用DbUnitQ我们可以用XML文g来准备测试数据集。下面的XML文gUCؓ(f)目标数据库的Seed FileQ代表目标数据库的表名和数据Q它为测试准备了(jin)两个Employee的数据。employee对应数据库的表名Qemployee_uid、start_date、first_name和last_name都是表employee的列名?/span>
<?xml version="1.0" encoding="GB2312"?>
<dataset>
(tng) (tng) (tng) <employee employee_uid="0001"
(tng) (tng) (tng) (tng) (tng) (tng) start_date="2001-01-01"
(tng) (tng) (tng) (tng) (tng) (tng) first_name="liutao"
(tng) (tng) (tng) (tng) (tng) (tng) last_name="liutao" />
(tng) (tng) (tng)
(tng) (tng) (tng) <employee employee_uid="0002"
(tng) (tng) (tng) (tng) (tng) (tng) start_date="2001-04-01"
(tng) (tng) (tng) (tng) (tng) (tng) first_name="wangchuang"
(tng) (tng) (tng) (tng) (tng) (tng) last_name="wangchuang" />
</dataset>
~省情况下,DbUnit在单元测试开始之前删除Seed File中所有表的数据,然后导入Seed File的测试数据。在Seed File中不存在的表QDbUnit则不处理?br />Seed File可以手工~写Q也可以用程序导出现有的数据库数据ƈ生成?br />
SqlMap代码
我们要测试的SqlMap映射文g如下所C:(x)
<select id="queryEmployeeById" parameterClass="java.lang.String"
(tng) (tng) (tng) resultClass="domain.Employee">
(tng) (tng) (tng) select employee_uid as userId,
(tng) (tng) (tng) (tng) (tng) (tng) start_date as startDate,
(tng) (tng) (tng) (tng) (tng) (tng) first_name as firstName,
(tng) (tng) (tng) (tng) (tng) (tng) last_name as lastName
(tng) (tng) (tng) from EMPLOYEE where employee_uid=#value#
</select>
<delete id="removeEmployeeById" parameterClass="java.lang.String">
(tng) (tng) (tng) delete from EMPLOYEE where employee_uid=#value#
</delete>
<update id="updateEmpoyee" parameterClass="domain.Employee">
(tng) (tng) (tng) update EMPLOYEE
(tng) (tng) (tng) set start_date=#startDate#,
(tng) (tng) (tng) first_name=#firstName#,
(tng) (tng) (tng) last_name=#lastName#
(tng) (tng) (tng) where employee_uid=#userId#
</update>
<insert id="insertEmployee" parameterClass="domain.Employee">
(tng) (tng) (tng) insert into employee (employee_uid,
(tng) (tng) (tng) (tng) (tng) (tng) start_date, first_name, last_name)
(tng) (tng) (tng) (tng) (tng) (tng) values (#userId#, #startDate#, #firstName#, #lastName#)
</insert>
~写DbUnit TestCase
Z(jin)方便试Q首先ؓ(f)SqlMap的单元测试编写一个抽象的试基类Q代码如下?/span>
public abstract class BaseSqlMapTest extends DatabaseTestCase {
(tng) (tng) (tng) protected static SqlMapClient sqlMap;
(tng) (tng) (tng) protected IDatabaseConnection getConnection() throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) return new DatabaseConnection(getJdbcConnection());
(tng) (tng) (tng) }
(tng) (tng) (tng) protected void setUp() throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) super.setUp();
(tng) (tng) (tng) (tng) (tng) (tng) init();
(tng) (tng) (tng) }
(tng) (tng) (tng) protected void tearDown() throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) super.tearDown();
(tng) (tng) (tng) (tng) (tng) (tng) getConnection().close();
(tng) (tng) (tng) (tng) (tng) (tng) if (sqlMap != null) {
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) DataSource ds = sqlMap.getDataSource();
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) Connection conn = ds.getConnection();
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) conn.close();
(tng) (tng) (tng) (tng) (tng) (tng) }
(tng) (tng) (tng) }
(tng) (tng) (tng) protected void init() throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) initSqlMap("sqlmap/SqlMapConfig.xml", null);
(tng) (tng) (tng) }
(tng) (tng) (tng) protected SqlMapClient getSqlMapClient() {
(tng) (tng) (tng) (tng) (tng) (tng) return sqlMap;
(tng) (tng) (tng) }
(tng) (tng) (tng) protected void initSqlMap(String configFile, Properties props)
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) Reader reader = Resources.getResourceAsReader(configFile);
(tng) (tng) (tng) (tng) (tng) (tng) sqlMap = SqlMapClientBuilder.buildSqlMapClient(reader, props);
(tng) (tng) (tng) (tng) (tng) (tng) reader.close();
(tng) (tng) (tng) }
(tng) (tng) (tng) protected void initScript(String script) throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) DataSource ds = sqlMap.getDataSource();
(tng) (tng) (tng) (tng) (tng) (tng) Connection conn = ds.getConnection();
(tng) (tng) (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) (tng) (tng) Reader reader = Resources.getResourceAsReader(script);
(tng) (tng) (tng) (tng) (tng) (tng) ScriptRunner runner = new ScriptRunner();
(tng) (tng) (tng) (tng) (tng) (tng) runner.setStopOnError(false);
(tng) (tng) (tng) (tng) (tng) (tng) runner.setLogWriter(null);
(tng) (tng) (tng) (tng) (tng) (tng) runner.setErrorLogWriter(null);
(tng) (tng) (tng) (tng) (tng) (tng) runner.runScript(conn, reader);
(tng) (tng) (tng) (tng) (tng) (tng) conn.commit();
(tng) (tng) (tng) (tng) (tng) (tng) conn.close();
(tng) (tng) (tng) (tng) (tng) (tng) reader.close();
(tng) (tng) (tng) }
(tng) (tng) (tng) private Connection getJdbcConnection() throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) Properties props = new Properties();
(tng) (tng) (tng) (tng) (tng) (tng) props.load(Resources.getResourceAsStream("sqlmap/SqlMapConfig.properties"));
(tng) (tng) (tng) (tng) (tng) (tng) Class driver = Class.forName(props.getProperty("driver"));
(tng) (tng) (tng) (tng) (tng) (tng) Connection conn = DriverManager.getConnection(props.getProperty("url"),
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) props.getProperty("username"), props.getProperty("password"));
(tng) (tng) (tng) (tng) (tng) (tng) return conn;
(tng) (tng) (tng) }
}
然后为每个SqlMap映射文g~写一个测试用例,extends上面的抽象类。如~写Employ.xml的测试用例如下,它覆盖了(jin)DbUnit的DatabaseTestCasecȝgetDataSetҎ(gu)?br />
public class EmployeeDaoTest extends BaseSqlMapTest {
(tng) (tng) (tng)
(tng) (tng) (tng) protected IDataSet getDataSet() throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) Reader reader = Resources.getResourceAsReader("config/employee_seed.xml");
(tng) (tng) (tng) (tng) (tng) (tng) return new FlatXmlDataSet(reader);
(tng) (tng) (tng) }
(tng) (tng) (tng) public void testQueryEmpoyeeById() throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) String id = "0001";
(tng) (tng) (tng) (tng) (tng) (tng) Employee emp = (Employee)sqlMap.queryForObject("queryEmployeeById", id);
(tng) (tng) (tng) (tng) (tng) (tng) assertNotNull(emp);
(tng) (tng) (tng) (tng) (tng) (tng) assertEquals("0001", emp.getUserId());
(tng) (tng) (tng) (tng) (tng) (tng) assertEquals("liutao", emp.getFirstName());
(tng) (tng) (tng) }
(tng) (tng) (tng) public void testRemoveEmployeeById() throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) String id = "0001";
(tng) (tng) (tng) (tng) (tng) (tng) int num = sqlMap.delete("removeEmployeeById", id);
(tng) (tng) (tng) (tng) (tng) (tng) assertEquals(1, num);
(tng) (tng) (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) (tng) (tng) // 注意q里, 认删除不能使用SqlMap的查? 很奇怪!
(tng) (tng) (tng) (tng) (tng) (tng) ITable table = getConnection().createQueryTable("removed",
(tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) (tng) "select * from employee where employee_uid='0001'");
(tng) (tng) (tng) (tng) (tng) (tng) assertEquals(0, table.getRowCount());
(tng) (tng) (tng) }
(tng) (tng) (tng) public void testUpdateEmployee() throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) String id = "0002";
(tng) (tng) (tng) (tng) (tng) (tng) Employee emp = (Employee)sqlMap.queryForObject("queryEmployeeById", id);
(tng) (tng) (tng) (tng) (tng) (tng) emp.setLastName("wch");
(tng) (tng) (tng) (tng) (tng) (tng) sqlMap.update("updateEmpoyee", emp);
(tng) (tng) (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) (tng) (tng) Employee emp1 = (Employee)sqlMap.queryForObject("queryEmployeeById", id);
(tng) (tng) (tng) (tng) (tng) (tng) assertEquals("wch", emp1.getLastName());
(tng) (tng) (tng) }
(tng) (tng) (tng) public void testInsertEmployee() throws Exception {
(tng) (tng) (tng) (tng) (tng) (tng) Employee emp = new Employee();
(tng) (tng) (tng) (tng) (tng) (tng) emp.setUserId("0005");
(tng) (tng) (tng) (tng) (tng) (tng) emp.setStartDate("2003-09-09");
(tng) (tng) (tng) (tng) (tng) (tng) emp.setFirstName("macy");
(tng) (tng) (tng) (tng) (tng) (tng) emp.setLastName("macy");
(tng) (tng) (tng) (tng) (tng) (tng) sqlMap.insert("insertEmployee", emp);
(tng) (tng) (tng) (tng) (tng) (tng)
(tng) (tng) (tng) (tng) (tng) (tng) Employee emp1 = (Employee)sqlMap.queryForObject("queryEmployeeById", "0005");
(tng) (tng) (tng) (tng) (tng) (tng) assertEquals(emp.getFirstName(), emp1.getFirstName());
(tng) (tng) (tng) (tng) (tng) (tng) assertEquals(emp.getStartDate(), emp1.getStartDate());
(tng) (tng) (tng) }
}
以上例子中的l色代码部分使用ITable接口来查询已删除的数据。因Z用SqlMapClient.queryForObjectҎ(gu)查询Q已删除的数据还存在Q真奇怪(有时间再研究Q?br />
DbUnit的断a
我们可以使用DbUnit的AssertioncȝҎ(gu)来比较数据是否相同?br />
public class Assertion {
(tng) (tng) (tng) public static void assertEquals(ITable expected, ITable actual)
(tng) (tng) (tng) public static void assertEquals(IDataSet expected, IDataSet actual)
}
DatabaseTestCase的getSetUpOperation和getTearDownOperationҎ(gu)
~省情况下,DbUnit执行每个试前,都会(x)执行CLEAN_INSERT操作Q删除Seed File中所有表的数据,q插入文件的试数据。你可以通过覆盖getSetUpOperation和getTearDownOperationҎ(gu)改变setUp和tearDown的行为?br />
protected DatabaseOperation getSetUpOperation() throws Exception {
(tng) (tng) (tng) return DatabaseOperation.REFRESH;
}
protected DatabaseOperation
getTearDownOperation()
throws Exception {
(tng) (tng) (tng)
return DatabaseOperation.NONE;
}
REFRESH操作执行试前ƈ不执行CLEAN操作Q只是导入文件中的数据,如果目标数据库数据已存在QDbUnit使用文g的数据来更新数据库?/span>
使用Ant
上面的方法通过extends DbUnit的DatabaseTestCase来控制数据库的状态。?/span>
使用DbUnit的Ant TaskQ完全可以通过Ant脚本的方式来实现?/span>
<taskdef name="dbunit" classname="org.dbunit.ant.DbUnitTask"/>
<!-- 执行set up 操作 -->
<dbunit driver="org.hsqldb.jdbcDriver"
(tng) (tng) (tng) (tng) (tng) (tng) (tng) url="jdbc:hsqldb:hsql://localhost/xdb"
(tng) (tng) (tng) (tng) (tng) (tng) (tng) userid="sa" password="">
(tng) (tng) (tng) <operation type="INSERT" src="employee_seed.xml"/>
</dbunit>
<!-- run all tests in the source tree -->
<junit printsummary="yes" haltonfailure="yes">
(tng) <formatter type="xml"/>
(tng) <batchtest fork="yes" todir="${reports.tests}">
(tng) (tng) (tng) <fileset dir="${src.tests}">
(tng) (tng) (tng) (tng) (tng) <include name="**/*Test*.java"/>
(tng) (tng) (tng) </fileset>
(tng) </batchtest>
</junit>
<!-- 执行tear down 操作 -->
<dbunit driver="org.hsqldb.jdbcDriver"
(tng) (tng) (tng) (tng) (tng) (tng) (tng) url="jdbc:hsqldb:hsql://localhost/xdb"
(tng) (tng) (tng) (tng) (tng) (tng) (tng) userid="sa" password="">
(tng) (tng) (tng) <operation type="DELETE" src="employee_seed.xml"/>
</dbunit>
以上的Ant脚本把junit task攑֜DbUnit的Task中间Q可以达到控制数据库状态的目标?br />
由此可知QDbUnit可以灉|控制目标数据库的试状态,从而ɾ~写SqlMap单元试变得更加L?br />
本文抄袭?jin)资源列表的“Effective Unit Test with DbUnit”,但重新编写了(jin)代码CZ?br />
|上资源
1?a >DbUnit Framework
2?a >Effective Unit Testing with DbUnit
3?a >Control your test-environement with DbUnit and Anthill
在我的经验里Qsessionq个词被滥用的程度大概仅ơ于transactionQ更加有的是transaction与session在某些语境下的含义是相同的?/p>
sessionQ中文经常翻译ؓ(f)?x)话Q其本来的含义是指有始有l的一pd动作/消息Q比如打?sh)话时从拿v?sh)话拨号到挂断?sh)话这中间的一pdq程可以UCZ个session。有时候我们可以看到这L(fng)话“在一个浏览器?x)话期间Q?..”,q里的会(x)话一词用的就是其本义Q是指从一个浏览器H口打开到关闭这个期间①。最混ؕ的是“用P客户端)(j)在一ơ会(x)话期间”这样一句话Q它可能指用L(fng)一pd动作Q一般情况下是同某个具体目的相关的一pd动作Q比如从d到选购商品到结账登?gu)样一个网上购物的q程Q有时候也被称Z个transactionQ,然而有时候也可能仅仅是指一ơ连接,也有可能是指含义①,其中的差别只能靠上下文来推断②?/p>
然而当session一词与|络协议相关联时Q它又往往隐含?jin)“面向连接”和/或“保持状态”这样两个含义,“面向连接”指的是在通信双方在通信之前要先建立一个通信的渠道,比如打电(sh)话,直到Ҏ(gu)接了(jin)?sh)话通信才能开始,与此相对的是写信Q在你把信发出去的时候你q不能确认对方的地址是否正确Q通信渠道不一定能建立Q但对发信h来说Q通信已经开始了(jin)。“保持状态”则是指通信的一方能够把一pd的消息关联v来,使得消息之间可以互相依赖Q比如一个服务员能够认出再次光(f)的老顾客ƈ且记得上ơ这个顾客还?gu)Ơ店里一块钱。这一cȝ例子有“一个TCP session”或者“一个POP3 session”③?/p>
而到?jin)web服务器蓬勃发展的时代Qsession在web开发语境下的语义又有了(jin)新的扩展Q它的含义是指一cȝ来在客户端与服务器之间保持状态的解决Ҏ(gu)④。有时候session也用来指q种解决Ҏ(gu)的存储结构,如“把xxx保存在session里”⑤。由于各U用于web开发的语言在一定程度上都提供了(jin)对这U解x(chng)案的支持Q所以在某种特定语言的语境下Qsession也被用来指代该语a的解x(chng)案,比如l常把Java里提供的javax.servlet.http.HttpSessionUCؓ(f)session⑥?/p>
鉴于q种混ؕ已不可改变,本文中session一词的q用也会(x)Ҏ(gu)上下文有不同的含义,请大家注意分辨?/p>
在本文中Q用中文“浏览器?x)话期间”来表达含义①,使用“session机制”来表达含义④,使用“session”表辑义⑤Q用具体的“HttpSession”来表达含义?/p>
二、HTTP协议与状态保?/p>
HTTP协议本n是无状态的Q这与HTTP协议本来的目的是相符的,客户端只需要简单的向服务器h下蝲某些文gQ无论是客户端还是服务器都没有必要纪录彼此过ȝ行ؓ(f)Q每一ơ请求之间都是独立的Q好比一个顾客和一个自动售货机或者一个普通的Q非?x)员Ӟ?j)大卖Z间的关系一栗?/p>
然而聪明(或者贪?j)?Q的Z很快发现如果能够提供一些按需生成的动态信息会(x)使web变得更加有用Q就像给有线?sh)视加上?gu)功能一栗这U需求一斚wqHTML逐步d?jin)表单、脚本、DOM{客L(fng)行ؓ(f)Q另一斚w在服务器端则出现?jin)CGI规范以响应客L(fng)的动态请求,作ؓ(f)传输载体的HTTP协议也添加了(jin)文g上蝲、cookieq些Ҏ(gu)。其中cookie的作用就是ؓ(f)?jin)解决HTTP协议无状态的~陷所作出的努力。至于后来出现的session机制则是又一U在客户端与服务器之间保持状态的解决Ҏ(gu)?/p>
让我们用几个例子来描qC下cookie和session机制之间的区别与联系。笔者曾l常ȝ一家咖啡店有喝5杯咖啡免费赠一杯咖啡的优惠Q然而一ơ性消?杯咖啡的Z(x)微乎其微Q这时就需要某U方式来U录某位֮的消Ҏ(gu)量。想象一下其实也无外乎下面的几种Ҏ(gu)Q?/p>
1、该店的店员很厉宻I能记住每位顾客的消费数量Q只要顾客一走进咖啡店,店员q道该怎么对待?jin)。这U做法就是协议本w支持状态?/p>
2、发l顾客一张卡片,上面记录着消费的数量,一般还有个有效期限。每ơ消Ҏ(gu)Q如果顾客出C张卡片,则此ơ消费就?x)与以前或以后的消费相联pv来。这U做法就是在客户端保持状态?/p>
3、发l顾客一张会(x)员卡Q除?jin)卡号之外什么信息也不纪录,每次消费Ӟ如果֮出示该卡片,则店员在店里的纪录本上找到这个卡号对应的U录d一些消费信息。这U做法就是在服务器端保持状态?/p>
׃HTTP协议是无状态的Q而出于种U考虑也不希望使之成ؓ(f)有状态的Q因此,后面两种Ҏ(gu)成为现实的选择。具体来说cookie机制采用的是在客L(fng)保持状态的Ҏ(gu)Q而session机制采用的是在服务器端保持状态的Ҏ(gu)。同时我们也看到Q由于采用服务器端保持状态的Ҏ(gu)在客L(fng)也需要保存(sh)个标识,所以session机制可能需要借助于cookie机制来达C存标识的目的Q但实际上它q有其他选择?/p>
三、理解cookie机制
cookie机制的基本原理就如上面的例子一L(fng)单,但是q有几个问题需要解冻I(x)“会(x)员卡”如何分发;“会(x)员卡”的内容Q以?qing)客户如何用“会(x)员卡”?/p>
正统的cookie分发是通过扩展HTTP协议来实现的Q服务器通过在HTTP的响应头中加上一行特D的指示以提C浏览器按照指示生成相应的cookie。然而纯_的客户端脚本如JavaScript或者VBScript也可以生成cookie?/p>
而cookie的用是由浏览器按照一定的原则在后台自动发送给服务器的。浏览器(g)查所有存储的cookieQ如果某个cookie所声明的作用范围大于等于将要请求的资源所在的位置Q则把该cookie附在h资源的HTTPh头上发送给服务器。意思是麦当劳的?x)员卡只能在麦当劳的店里出示Q如果某家分店还发行?jin)自q?x)员卡,那么q这家店的时候除?jin)要出示麦当劳的会(x)员卡,q要出示q家店的?x)员卡?/p>
cookie的内容主要包括:(x)名字Q|q期旉Q\径和域?/p>
其中域可以指定某一个域比如.google.comQ相当于d招牌Q比如宝z公司,也可以指定一个域下的具体某台机器比如www.google.com或者f(xi)roogle.google.comQ可以用飘柔来做比?/p>
路径是跟在域名后面的URL路径Q比?或?foo{等Q可以用某飘柔专柜做比?/p>
路径与域合在一起就构成?jin)cookie的作用范围?/p>
如果不设|过期时_(d)则表C个cookie的生命期为浏览器?x)话期间Q只要关闭浏览器H口Qcookie消׃(jin)。这U生命期为浏览器?x)话期的cookie被称Z(x)话cookie。会(x)话cookie一般不存储在硬盘(sh)而是保存在内存里Q当然这U行为ƈ不是规范规定的。如果设|了(jin)q期旉Q浏览器׃(x)把cookie保存到硬盘(sh)Q关闭后再次打开览器,q些cookie仍然有效直到过讑֮的过期时间?/p>
存储在硬盘(sh)的cookie可以在不同的览器进E间׃nQ比如两个IEH口。而对于保存在内存里的cookieQ不同的览器有不同的处理方式。对于IEQ在一个打开的窗口上按Ctrl-NQ或者从文g菜单Q打开的窗口可以与原窗口共享,而用其他方式新开的IEq程则不能共享已l打开的窗口的内存cookieQ对于Mozilla Firefox0.8Q所有的q程和标{N都可以共享同L(fng)cookie。一般来说是用javascript的window.open打开的窗口会(x)与原H口׃n内存cookie。浏览器对于?x)话cookie的这U只认cookie不认人的处理方式l常l采用session机制的web应用E序开发者造成很大的困扰?/p>
下面是一个goolge讄cookie的响应头的例?/p>
HTTP/1.1 302 Found
Location: http://www.google.com/intl/zh-CN/
Set-Cookie: PREF=ID=0565f77e132de138:NW=1:TM=1098082649:LM=1098082649:S=KaeaCFPo49RiA_d8; expires=Sun, 17-Jan-2038 19:14:07 GMT; path=/; domain=.google.com
Content-Type: text/html
q是使用HTTPLookq个HTTP Sniffer软g来俘L(fng)HTTP通讯U录的一部分
览器在再次讉Kgoolge的资源时自动向外发送cookie
使用Firefox可以很容易的观察现有的cookie的?/p>
使用HTTPLook配合F(tun)irefox可以很容易的理解cookie的工作原理?/p>
IE也可以设|在接受cookie前询?/p>
q是一个询问接受cookie的对话框?/p>
四、理解session机制
session机制是一U服务器端的机制Q服务器使用一U类g散列表的l构Q也可能是使用散列表)(j)来保存(sh)息?/p>
当程序需要ؓ(f)某个客户端的h创徏一个session的时候,服务器首先检查这个客L(fng)的请求里是否已包含了(jin)一个session标识 - UCؓ(f)session idQ如果已包含一个session id则说明以前已lؓ(f)此客L(fng)创徏qsessionQ服务器按照session id把这个session(g)索出来用(如果(g)索不刎ͼ可能?x)新Z个)(j)Q如果客L(fng)h不包含session idQ则为此客户端创Z个sessionq且生成一个与此session相关联的session idQsession id的值应该是一个既不会(x)重复Q又不容易被扑ֈ规律以仿造的字符Ԍq个session id被在本ơ响应中q回l客L(fng)保存?/p>
保存q个session id的方式可以采用cookieQ这样在交互q程中浏览器可以自动的按照规则把q个标识发挥l服务器。一般这个cookie的名字都是类gSEEESIONIDQ而。比如weblogic对于web应用E序生成的cookieQJSESSIONID=ByOK3vjFD75aPnrF7C2HmdnV6QZcEbzWoWiBYEnLerjQ99zWpBng!-145788764Q它的名字就是JSESSIONID?/p>
׃cookie可以被h为的止Q必L其他机制以便在cookie被禁止时仍然能够把session id传递回服务器。经常被使用的一U技术叫做URL重写Q就是把session id直接附加在URL路径的后面,附加方式也有两种Q一U是作ؓ(f)URL路径的附加信息,表现形式为http://...../xxx;jsessionid=ByOK3vjFD75aPnrF7C2HmdnV6QZcEbzWoWiBYEnLerjQ99zWpBng!-145788764另一U是作ؓ(f)查询字符串附加在URL后面Q表现Ş式ؓ(f)http://...../xxx?jsessionid=ByOK3vjFD75aPnrF7C2HmdnV6QZcEbzWoWiBYEnLerjQ99zWpBng!-145788764
q两U方式对于用h说是没有区别的,只是服务器在解析的时候处理的方式不同Q采用第一U方式也有利于把session id的信息和正常E序参数区分开来?/p>
Z(jin)在整个交互过E中始终保持状态,必d每个客户端可能请求的路径后面都包含这个session id?/p>
另一U技术叫做表单隐藏字Dc(din)就是服务器?x)自动修改表单,d一个隐藏字D,以便在表单提交时能够把session id传递回服务器。比如下面的表单
在被传递给客户端之前将被改写成
q种技术现在已较少应用Q笔者接触过的很古老的iPlanet6(SunONE应用服务器的前n)׃用了(jin)q种技术。实际上q种技术可以简单的用对action应用URL重写来代ѝ?/p>
在谈论session机制的时候,常常听到q样一U误解“只要关闭浏览器Qsession消׃(jin)”。其实可以想象一下会(x)员卡的例子,除非֮d对店家提出销卡,否则店家l对不会(x)L删除֮的资料。对session来说也是一L(fng)Q除非程序通知服务器删除一个sessionQ否则服务器?x)一直保留,E序一般都是在用户做log off的时候发个指令去删除session。然而浏览器从来不会(x)d在关闭之前通知服务器它?yu)要关闭Q因此服务器Ҏ(gu)不会(x)有机?x)知道浏览器已经关闭Q之所以会(x)有这U错觉,是大部分session机制都用会(x)话cookie来保存session idQ而关闭浏览器后这个session id消׃(jin)Q再ơ连接服务器时也无法找到原来的session。如果服务器讄的cookie被保存到盘?sh),或者用某U手D|写浏览器发出的HTTPh_(d)把原来的session id发送给服务器,则再ơ打开览器仍然能够找到原来的session?/p>
恰恰是由于关闭浏览器不会(x)Dsession被删除,q服务器ؓ(f)seesion讄?jin)一个失效时_(d)当距dL(fng)上一ơ用session的时间超q这个失效时间时Q服务器可以认为客L(fng)已经停止?jin)活动,才?x)把session删除以节省存储空间?/p>
五、理解javax.servlet.http.HttpSession
HttpSession是Javaq_对session机制的实现规范,因ؓ(f)它仅仅是个接口,具体到每个web应用服务器的提供商,除了(jin)对规范支持之外,仍然?x)有一些规范里没有规定的细微差异。这里我们以BEA的Weblogic Server8.1作ؓ(f)例子来演C?/p>
首先QW(xu)eblogic Server提供?jin)一pd的参数来控制它的HttpSession的实玎ͼ包括使用cookie的开关选项Q用URL重写的开关选项Qsession持久化的讄Qsession失效旉的设|,以及(qing)针对cookie的各U设|,比如讄cookie的名字、\径、域Qcookie的生存时间等?/p>
一般情况下Qsession都是存储在内存里Q当服务器进E被停止或者重启的时候,内存里的session也会(x)被清I,如果讄?jin)session的持久化Ҏ(gu),服务器就?x)把session保存到硬盘(sh)Q当服务器进E重新启动或q些信息能够被再次使用QW(xu)eblogic Server支持的持久性方式包括文件、数据库、客L(fng)cookie保存和复制?/p>
复制严格说来不算持久化保存,因ؓ(f)session实际上还是保存在内存里,不过同样的信息被复制到各个cluster内的服务器进E中Q这样即使某个服务器q程停止工作也仍然可以从其他q程中取得session?/p>
cookie生存旉的设|则?x)?jing)响浏览器生成的cookie是否是一个会(x)话cookie。默认是使用?x)话cookie。有兴趣的可以用它来试验我们在第四节里提到的那个误解?/p>
cookie的\径对于web应用E序来说是一个非帔R要的选项QW(xu)eblogic Server对这个选项的默认处理方式得它与其他服务器有明昄区别。后面我们会(x)专题讨论?/p>
关于session的设|参考[5] http://e-docs.bea.com/wls/docs70/webapp/weblogic_xml.html#1036869
六、HttpSession常见问题
Q在本小节中session的含义ؓ(f)⑤和⑥的混合Q?/p>
1、session在何时被创徏
一个常见的误解是以为session在有客户端访问时p创徏Q然而事实是直到某server端程序调用HttpServletRequest.getSession(true)q样的语句时才被创徏Q注意如果JSP没有昄的?<%@page session="false"%>关闭sessionQ则JSP文g在编译成Servlet时将?x)自动加上这样一条语句HttpSession session = HttpServletRequest.getSession(true);q也是JSP中隐含的session对象的来历?/p>
׃session?x)消耗内存资源,因此Q如果不打算使用sessionQ应该在所有的JSP中关闭它?/p>
2、session何时被删?/p>
l合前面的讨论,session在下列情况下被删除a.E序调用HttpSession.invalidate();或b.距离上一ơ收到客L(fng)发送的session id旉间隔过?jin)session的超时设|?或c.服务器进E被停止Q非持久sessionQ?/p>
3、如何做到在览器关闭时删除session
严格的讲Q做不到q一炏V可以做一点努力的办法是在所有的客户端页面里使用javascript代码window.oncolose来监视浏览器的关闭动作,然后向服务器发送一个请求来删除session。但是对于浏览器崩溃或者强行杀死进E这些非常规手段仍然无能为力?/p>
4、有个HttpSessionListener是怎么回事
你可以创L(fng)listenerȝ控session的创建和销毁事Ӟ使得在发生这L(fng)事g时你可以做一些相应的工作。注意是session的创建和销毁动作触发listenerQ而不是相反。类似的与HttpSession有关的listenerq有HttpSessionBindingListenerQHttpSessionActivationListener和HttpSessionAttributeListener?br />
(tng) (tng) (tng) (tng) (tng) (tng) (tng) 5、存攑֜session中的对象必须是可序列化的?/p>
不是必需的。要求对象可序列化只是ؓ(f)?jin)session能够在集中被复制或者能够持久保存或者在必要时server能够暂时把session交换出内存。在Weblogic Server的session中放|一个不可序列化的对象在控制C?x)收C个警告。我所用过的某个iPlanet版本如果session中有不可序列化的对象Q在session销毁时?x)有一个ExceptionQ很奇怪?/p>
6、如何才能正的应付客户端禁止cookie的可能?/p>
Ҏ(gu)有的URL使用URL重写Q包括超链接Qform的actionQ和重定向的URLQ具体做法参见[6]
http://e-docs.bea.com/wls/docs70/webapp/sessions.html#100770
7、开两个览器窗口访问应用程序会(x)使用同一个sessionq是不同的session
参见W三节对cookie的讨论,对session来说是只认id不认人,因此不同的浏览器Q不同的H口打开方式以及(qing)不同的cookie存储方式都会(x)对这个问题的{案有媄(jing)响?/p>
8、如何防止用h开两个览器窗口操作导致的session混ؕ
q个问题?sh)防止表单多ơ提交是cM的,可以通过讄客户端的令牌来解冟뀂就是在服务器每ơ生成一个不同的idq回l客L(fng)Q同时保存在session里,客户端提交表单时必须把这个id也返回服务器Q程序首先比较返回的id与保存在session里的值是否一_(d)如果不一致则说明本次操作已经被提交过?jin)。可以参看《J2EE核心(j)模式》关于表C层模式的部分。需要注意的是对于用javascript window.open打开的窗口,一般不讄q个idQ或者用单独的idQ以防主H口无法操作Q徏议不要再window.open打开的窗口里做修Ҏ(gu)作,q样可以不用设|?/p>
9、ؓ(f)什么在Weblogic Server中改变session的值后要重新调用一ơsession.setValue
做这个动作主要是Z(jin)在集环境中提示Weblogic Server session中的值发生了(jin)改变Q需要向其他服务器进E复制新的session倹{?/p>
10、ؓ(f)什么session不见?/p>
排除session正常失效的因素之外,服务器本w的可能性应该是微乎其微的,虽然W者在iPlanet6SP1加若q补丁的Solaris版本上倒也遇到q;览器插件的可能性次之,W者也遇到q?721插g造成的问题;理论上防火墙或者代理服务器在cookie处理上也有可能会(x)出现问题?/p>
出现q一问题的大部分原因都是E序的错误,最常见的就是在一个应用程序中去访问另外一个应用程序。我们在下一节讨个问题?/p>
七、跨应用E序的session׃n
常常有这L(fng)情况Q一个大目被分割成若干项目开发,Z(jin)能够互不q扰Q要求每个小目作ؓ(f)一个单独的web应用E序开发,可是C(jin)最后突然发现某几个项目之间需要共享一些信息,或者想使用session来实现SSO(single sign on)Q在session中保存login的用户信息,最自然的要求是应用E序间能够访问彼此的session?/p>
然而按照Servlet规范Qsession的作用范围应该仅仅限于当前应用程序下Q不同的应用E序之间是不能够互相讉KҎ(gu)的session的。各个应用服务器从实际效果上都遵守了(jin)q一规范Q但是实现的l节却可能各有不同,因此解决跨应用程序session׃n的方法也各不相同?/p>
首先来看一下Tomcat是如何实现web应用E序之间session的隔ȝQ从Tomcat讄的cookie路径来看Q它对不同的应用E序讄的cookie路径是不同的Q这样不同的应用E序所用的session id是不同的Q因此即使在同一个浏览器H口里访问不同的应用E序Q发送给服务器的session id也可以是不同的?br />
Ҏ(gu)q个Ҏ(gu),我们可以推测Tomcat中session的内存结构大致如下?br />
W者以前用q的iPlanet也采用的是同L(fng)方式Q估计SunONE与iPlanet之间不会(x)有太大的差别。对于这U方式的服务器,解决的思\很简单,实际实行h也不难。要么让所有的应用E序׃n一个session idQ要么让应用E序能够获得其他应用E序的session id?/p>
iPlanet中有一U很单的Ҏ(gu)来实现共享一个session idQ那是把各个应用程序的cookie路径都设?Q实际上应该?NASAppQ对于应用程序来讲它的作用相当于根)(j)?/p>
需要注意的是,操作׃n的session应该遵@一些编E约定,比如在session attribute名字的前面加上应用程序的前缀Q得setAttribute("name", "neo")变成setAttribute("app1.name", "neo")Q以防止命名I间冲突Q导致互相覆盖?/p>
在Tomcat中则没有q么方便的选择。在Tomcat版本3上,我们q可以有一些手D|׃nsession。对于版?以上的TomcatQ目前笔者尚未发现简单的办法。只能借助于第三方的力量,比如使用文g、数据库、JMS或者客L(fng)cookieQURL参数或者隐藏字D늭手段?/p>
我们再看一下Weblogic Server是如何处理session的?br />
从截屏画面上可以看到Weblogic ServerҎ(gu)有的应用E序讄的cookie的\径都?Q这是不是意味着在Weblogic Server中默认的可以共享session?jin)呢Q然而一个小实验卛_证明即不同的应用程序用的是同一个sessionQ各个应用程序仍然只能访问自己所讄的那些属性。这说明Weblogic Server中的session的内存结构可能如?br />
对于q样一U结构,在session机制本n上来解决session׃n的问题应该是不可能的?jin)。除?jin)借助于第三方的力量,比如使用文g、数据库、JMS或者客L(fng)cookieQURL参数或者隐藏字D늭手段Q还有一U较为方便的做法Q就是把一个应用程序的session攑ֈServletContext中,q样另外一个应用程序就可以从ServletContext中取得前一个应用程序的引用。示例代码如下,
应用E序A
context.setAttribute("appA", session);
应用E序B
contextA = context.getContext("/appA");
HttpSession sessionA = (HttpSession)contextA.getAttribute("appA");
值得注意的是q种用法不可ULQ因为根据ServletContext的JavaDocQ应用服务器可以处于安全的原因对于context.getContext("/appA");q回I|以上做法在Weblogic Server 8.1中通过?/p>
那么Weblogic ServerZ么要把所有的应用E序的cookie路径都设?呢?原来是ؓ(f)?jin)SSOQ凡是共享这个session的应用程序都可以׃n认证的信息。一个简单的实验可以证明这一点,修改首先d的那个应用程序的描述Wweblogic.xmlQ把cookie路径修改?appA讉K另外一个应用程序会(x)重新要求dQ即使是反过来,先访问cookie路径?的应用程序,再访问修改过路径的这个,虽然不再提示dQ但是登录的用户信息也会(x)丢失。注意做q个实验时认证方式应该用FORMQ因为浏览器和web服务器对basic认证方式有其他的处理方式Q第二次h的认证不是通过session来实现的。具体请参看[7] secion 14.8 AuthorizationQ你可以修改所附的CZE序来做q些试验?/p>
八、ȝ
session机制本nq不复杂Q然而其实现和配|上的灵zL却使得具体情况复杂多变。这也要求我们不能把仅仅某一ơ的l验或者某一个浏览器Q服务器的经验当作普遍适用的经验,而是始终需要具体情况具体分析?/p>