亚洲黄色在线视频,国产精品久久久久久免费观看 ,91精品综合久久久久久五月天

tips悬停

Rabbit — Wed, 07 May 2014 14:23:00 GMT

http://www.php100.com/html/program/jquery/2013/0905/5970.html

http://vadikom.com/demos/poshytip/

http://www.cnblogs.com/best/archive/2011/09/27/2193572.html

JQuery插�gTipsWindown 1.1

一个基于jQuery的弹出层。支持拖拽，支持内容为文字，囄��Q�URL�{?至于兼容性。在IE6下，弹出对像无法�l�对固定。其他应该没啥大问题�Q?/p>

最新更斎ͼ�(2010-08-12)�Q�修正IE6下不能遮住下拉菜单的BUG�Q�增加拖动时半透明效果�?/p>

应用演示

弹出文本信息提示�Q?

tipsWindown("提示","text:提示信息内容","250","150","true","","true","msg")
弹出��面中的某个ID的html�Q?

tipsWindown("标题","id:testID","300","200","true","","true","id")
弹出囄��Q?

tipsWindown("囄��","img:囄��路径","250","150","true","","true","img")
get加蝲一�?html文�g�Q�也可以�?php/.asp?id=4之类的）�Q?

tipsWindown("标题","url:get?test.html","250","150","true","","true","text");
加蝲一个页面到框架昄��Q?br />
tipsWindown("标题","iframe:http://www.nowamagic.net","900","580","true","","true","leotheme");
弹出一个不能拖动且没有遮罩背景的文本信息层�Q?

tipsWindown("提示","text:提示信息内容","250","150","false","","false","msg")
弹出一个不能拖动，三秒钟自动关闭的层：

tipsWindown("提示","text:提示信息内容","250","150","false","3000","true","msg")

参数说明

��序	参数	功能	备注
1	title	弹出层的标题	必填�Q�纯文本
2	content	弹出层的内容	text	文本内容
			id	��面里某id的子标签
			img	囄��
			url	get或post某一��面里的html�Q�该��面要求只包含body的子标签
			iframe	目标地址在框架显�C?/td>
3	width	弹出层的�?/td>	必填�Q�比�?#8220;200”。（不需要带px�Q?/td>
4	height	弹出层的�?/td>	�?width
5	drag	是否可拖�?/td>	必填�Q�可选参敎ͼ�true,false�Q?/td>
6	time	自动消失旉��	可不填，默认不自动关闭；参数可�ؓ�I?"")
7	showbg	是否昄��遮罩�?/td>	可不填，默认不显�C�（此项如填了，它前面的time也必��要填）
8	cssName	弹出层附加样式名	可不�?/td>

像这�U�弹出透明背景层效果很常见了，除部分区域可以操作外其他区域不能操作�Q�目前有提供插�g�Q�完全可以实现此�U�效果�?/p>

查看本页源代码可获取所有所需的代码�?/p>

Rabbit 2014-05-07 22:23 发表评论

Rabbit — Tue, 15 Apr 2014 13:38:00 GMT

<insert id="insertData" parameterType="java.util.List" >
INSERT INTO EMP(EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,DEPTNO) (
<foreach collection="list" item="item" index="index" separator="union all">
select
#{item.EMPNO,jdbcType=VARCHAR},
#{item.ENAME,jdbcType=VARCHAR},
#{item.JOB,jdbcType=VARCHAR},
#{item.MGR,jdbcType=NUMERIC},
#{item.MGR,jdbcType=NUMERIC},
TO_DATE(#{item.HIREDATE,jdbcType=VARCHAR},'yyyy-mm-dd')
from dual
foreach>
)

insert>

=====================================================================

declare

type t_array is table of t_target%rowtype;

t_data t_array;

cursor c is

select null id, owner, object_name, null object_id, null xx, null yy

from dba_objects;

begin

open c;

loop

fetch c bulk collect

into t_data limit 100;

forall i in 1 .. t_data.count

insert into t_target values t_data (i);

exit when c%notfound;

end loop;

close c;

commit;

end;

<insert id="insertByProc" statementType="CALLABLE">         
{call insertPro(#{name},#{age},#{sex},#{password},#{num})}     
insert>

1 CREATE DEFINER = `root`@`localhost` PROCEDURE `NewProc`(IN `name_in` varchar(255),IN `age_in` int,IN `sex_in` varchar(255),IN `password_in` varchar(255),IN `num_in` int)  2 BEGIN  3     SET @a=0;  4 Label:LOOP  5     SET @a=@a+1;  6     INSERT INTO person ( name, age, sex, password) VALUES (name_in,age_in,sex_in,password_in);  7      IF @a=num_in THEN  8             LEAVE Label;  9         END IF; 10 END LOOP Label; 11 END;

Rabbit 2014-04-15 21:38 发表评论

Oracle中Hint深入理解

Rabbit — Fri, 08 Nov 2013 06:44:00 GMT

Hint概述
��Z��代�h的优化器是很聪明的，在绝大多数情况下它会选择正确的优化器�Q�减��M��DBA的负担。但有时它也聪明反被聪明误，选择了很差的执行计划�Q��某个语句的执行变得奇慢无比�?/font>

此时��需要DBA�q�行��Zؓ的干预，告诉优化器��用我们指定的存取路径或连接类型生成执行计划，从而��语句高效的运行。例如，如果我们认�ؓ对于一个特定的语句�Q�执行全表扫描要比执行烦引扫描更有效�Q�则我们��可以指�C�Z��化器使用全表扫描。在Oracle 中，是通过��句添�?Hints(提示)来实现干预优化器优化的目的�?br />不徏议在代码中��用hint�Q�在代码使用hint使得CBO无法�Ҏ��实际的数据状态选择正确的执行计划。毕�?/font> 数据是不断变化的�Q?/font> 10g以后的CBO也越来越完善�Q�大多数情况下我们该让Oracle自行军_��采用什么执行计划�?/font>

Oracle Hints是一�U�机�Ӟ��用来告诉优化器按照我们的告诉它的方式生成执行计划。我们可以用Oracle Hints来实玎ͼ�
1) 使用的优化器的类�?br />2) ��Z��代�h的优化器的优化目标，是all_rows�q�是first_rows�?br />3) 表的讉K��路径�Q�是全表扫描�Q�还是烦引扫描，�q�是直接利用rowid�?br />4) 表之间的�q�接�c�d��
5) 表之间的�q�接��序
6) 语句的�ƈ行程�?/font>

除了”RULE”提示外，一旦��用的别的提示�Q�语句就会自动的改�ؓ使用CBO优化器，此时如果你的数据字典中没有统计数据，��׃��使用�~�省的统计数据。所以徏议大家如果��用CBO或Hints提示�Q�则最好对表和索引�q�行定期的分析�?/font>

如何使用Hints:

Hints只应用在它们所在sql语句�?statement block�Q�由select、update、delete关键字标�?上，对其它SQL语句或语句的其它部分没有影响。如�Q�对于��用union操作�?个sql语句�Q�如果只在一个sql语句上有Hints�Q�则该Hints不会影响另一个sql语句�?/font>

我们可以使用注释(comment)来�ؓ一个语句添加Hints�Q�一个语句块只能有一个注释，而且注释只能攑֜�SELECT, UPDATE, or DELETE关键字的后面

使用Oracle Hints的语法：

{DELETE|INSERT|SELECT|UPDATE} /*+ hint [text] [hint[text]]... */

{DELETE|INSERT|SELECT|UPDATE} --+ hint [text] [hint[text]]...

注解�Q?br />1) DELETE、INSERT、SELECT和UPDATE是标识一个语句块开始的关键字，包含提示的注释只能出现在�q�些关键字的后面�Q�否则提�C�无效�?br />2) “+”可��C��注释是一个Hints�Q�该加号必须立即跟在”/*”的后面，中间不能有空根{�?br />3) hint是下面介�l�的具体提示之一�Q�如果包含多个提�C�，则每个提�C�Z��间需要用一个或多个�I�格隔开�?br />4) text 是其它说明hint的注释性文�?/font>

5)使用表别名。如果在查询中指定了表别名，那么提示必须也��用表别名。例如：select /*+ index(e,dept_idx) */ * from emp e;
6)不要在提�C�Z��使用模式名称�Q�如果在提示中指定了模式的所有者，那么提示��被忽略。例如：
select /*+ index(scott.emp,dept_idx) */ * from emp

注意�Q�如果你没有正确的指定Hints�Q�Oracle��忽略该Hints�Q��ƈ且不会给��Z�Q何错误�?br />hint被忽�?/strong>

如果CBO认�ؓ使用hint会导致错误的�l�果�Ӟ��hint��被忽略�Q�详见下�?br />SQL> select /*+ index(t t_ind) */ count(*) from t;
Execution Plan
----------------------------------------------------------
Plan hash value: 2966233522
-------------------------------------------------------------------
| Id | Operation          | Name | Rows | Cost (%CPU)| Time     |
-------------------------------------------------------------------
|   0 | SELECT STATEMENT   |      |     1 |    57   (2)| 00:00:01 |
|   1 | SORT AGGREGATE    |      |     1 |            |          |
|   2 |   TABLE ACCESS FULL| T    | 50366 |    57   (2)| 00:00:01 |
-------------------------------------------------------------------

因�ؓ我们是对记录求��L��Q�且我们�q�没有在建立索引时指定不能�ؓ�I�，索引如果CBO选择在烦引上�q�行count�Ӟ��但烦引字�D�上的��gؓ�I�时�Q�结果将不准��，故CBO没有选择索引�?/font>
SQL> select /*+ index(t t_ind) */ count(id) from t;
Execution Plan
----------------------------------------------------------
Plan hash value: 646498162
--------------------------------------------------------------------------
| Id | Operation        | Name | Rows | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------
|   0 | SELECT STATEMENT |       |     1 |     5 |   285   (1)| 00:00:04 |
|   1 | SORT AGGREGATE |       |     1 |     5 |            |          |
|   2 |   INDEX FULL SCAN| T_IND | 50366 |   245K|   285   (1)| 00:00:04 |
--------------------------------------------------------------------------

因�ؓ我们只对id�q�行count�Q�这个动作相当于count索引上的所有id��|��q�个操作和对表上的id字段�q�行count是一��L��(�l�函��C��忽略null�?

Hint的具体用�?br />

和优化器相关的hint

1�?*+ ALL_ROWS */
表明对语句块选择��Z��开销的优化方�?�q�获得最佛_��吐量,使资源消耗最��化.
SELECT /*+ ALL+_ROWS*/ EMP_NO,EMP_NAM,DAT_IN FROM BSEMPMS WHERE EMP_NO='SCOTT';
2�?*+ FIRST_ROWS(n) */
表明对语句块选择��Z��开销的优化方�?�q�获得最佛_��应时�?使资源消耗最��化.
SELECT /*+FIRST_ROWS(20) */ EMP_NO,EMP_NAM,DAT_IN FROM BSEMPMS WHERE EMP_NO='SCOTT';
3�?*+ RULE*/
表明对语句块选择��Z��规则的优化方�?
SELECT /*+ RULE */ EMP_NO,EMP_NAM,DAT_IN FROM BSEMPMS WHERE EMP_NO='SCOTT';
和访问�\径相关的hint

1�?*+ FULL(TABLE)*/
表明对表选择全局扫描的方�?
SELECT /*+FULL(A)*/ EMP_NO,EMP_NAM FROM BSEMPMS A WHERE EMP_NO='SCOTT';
2�?*+ INDEX(TABLE INDEX_NAME) */
表明对表选择索引的扫描方�?
SELECT /*+INDEX(BSEMPMS SEX_INDEX) */ * FROM BSEMPMS WHERE SEX='M';
5�?*+ INDEX_ASC(TABLE INDEX_NAME)*/
表明对表选择索引升序的扫描方�?
SELECT /*+INDEX_ASC(BSEMPMS PK_BSEMPMS) */ * FROM BSEMPMS WHERE DPT_NO='SCOTT';
6�?*+ INDEX_COMBINE*/
为指定表选择位图讉K��路经,如果INDEX_COMBINE中没有提供作为参数的索引,��选择��Z��囄��引的布尔�l�合方式.
SELECT /*+INDEX_COMBINE(BSEMPMS SAL_BMI HIREDATE_BMI) */ * FROM BSEMPMS
WHERE SAL<5000000 AND HIREDATE
7�?*+ INDEX_JOIN(TABLE INDEX_NAME1 INDEX_NAME2) */
当谓词中引用的列都有索引的时候，可以通过指定采用索引兌��的方式，来访问数�?br />select /*+ index_join(t t_ind t_bm) */ id from t where id=100 and object_name='EMPLOYEES'
8�?*+ INDEX_DESC(TABLE INDEX_NAME)*/
表明对表选择索引降序的扫描方�?

SELECT /*+INDEX_DESC(BSEMPMS PK_BSEMPMS) */ * FROM BSEMPMS WHERE DPT_NO='SCOTT';
9�?*+ INDEX_FFS(TABLE INDEX_NAME) */
�Ҏ��定的表执行快速全索引扫描,而不是全表扫描的办法.
SELECT /* + INDEX_FFS(BSEMPMS IN_EMPNAM)*/ * FROM BSEMPMS WHERE DPT_NO='TEC305';

10�?*+ INDEX_SS(T T_IND) */
�?i开始，oracle引入了这�U�烦引访问方式。当在一个联合烦引中�Q�某些谓词条件�ƈ不在联合索引的第一列时�Q�可以通过Index Skip Scan来访问烦引获得数据。当联合索引�W�一列的唯一��g��数很��时�Q��用这�U�方式比全表扫描效率高�?/font>

SQL> create table t as select 1 id,object_name from dba_objects;
Table created.
SQL> insert into t select 2,object_name from dba_objects;
50366 rows created.
SQL> insert into t select 3,object_name from dba_objects;
50366 rows created.
SQL> insert into t select 4,object_name from dba_objects;
50366 rows created.
SQL> commit;
Commit complete.
SQL> create index t_ind on t(id,object_name);
Index created.
SQL> exec dbms_stats.gather_table_stats('HR','T',cascade=>true);
PL/SQL procedure successfully completed.
执行全表扫描
SQL> select /*+ full(t) */ * from t where object_name='EMPLOYEES';
6 rows selected.
Execution Plan
----------------------------------------------------------
Plan hash value: 1601196873
--------------------------------------------------------------------------
| Id | Operation         | Name | Rows | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------
|   0 | SELECT STATEMENT |      |     5 |   135 |   215   (3)| 00:00:03 |
|* 1 | TABLE ACCESS FULL| T    |     5 |   135 |   215   (3)| 00:00:03 |
--------------------------------------------------------------------------
Predicate Information (identified by operation id):
---------------------------------------------------
   1 - filter("OBJECT_NAME"='EMPLOYEES')
Statistics
----------------------------------------------------------
          0 recursive calls
          0 db block gets
        942 consistent gets
          0 physical reads
          0 redo size
        538 bytes sent via SQL*Net to client
        385 bytes received via SQL*Net from client
          2 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
          6 rows processed
不采用hint
SQL> select * from t where object_name='EMPLOYEES';
6 rows selected.
Execution Plan
----------------------------------------------------------
Plan hash value: 2869677071
--------------------------------------------------------------------------
| Id | Operation        | Name | Rows | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------
|   0 | SELECT STATEMENT |       |     5 |   135 |     5   (0)| 00:00:01 |
|* 1 | INDEX SKIP SCAN | T_IND |     5 |   135 |     5   (0)| 00:00:01 |
--------------------------------------------------------------------------
Predicate Information (identified by operation id):
---------------------------------------------------
   1 - access("OBJECT_NAME"='EMPLOYEES')
       filter("OBJECT_NAME"='EMPLOYEES')
Statistics
----------------------------------------------------------
          1 recursive calls
          0 db block gets
         17 consistent gets
          1 physical reads
          0 redo size
        538 bytes sent via SQL*Net to client
        385 bytes received via SQL*Net from client
          2 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
          6 rows processed
当全表扫描扫描了942个块�Q�联合烦引只扫描�?7个数据块。可以看到联合烦引的�W�一个字�D늚�值重复率很高�Ӟ��即��谓词中没有联合烦引的�W�一个字�D�，依然会��用index_ss方式�Q�效率远�q�高于全表扫描效率。但�?/font> �W�一个字�D늚�值重复率很低�Ӟ��使用 index_ss的效率要低于全表扫描�Q�读者可以自行实�?/font>
和表的关联相关的hint

/*+ leading(table_1,table_2) */

在多表关联查询中�Q�指定哪个表作�ؓ驱动表，卛_��诉优化器首先要访问哪个表上的数据�?/span>
select /*+ leading(t,t1) */ t.* from t,t1 where t.id=t1.id;
/*+ order */

让Oracle�Ҏ��from后面表的��序来选择驱动表，oracle��使用leading�Q�他更�ؓ灉|��
select /*+ order */ t.* from t,t1 where t.id=t1.id;
/*+ use_nl(table_1,table_2) */
在多表关联查询中�Q�指定��用nest loops方式�q�行多表兌��?/span>

select /*+ use_nl(t,t1) */ t.* from t,t1 where t.id=t1.id;

/*+ use_hash(table_1,table_2) */
在多表关联查询中�Q�指定��用hash join方式�q�行多表兌��?/span>

select /*+ use_hash(t,t1) */ t.* from t,t1 where t.id=t1.id;

在多表关联查询中�Q�指定��用hash join方式�q�行多表兌��Q��ƈ指定表t为驱动表�?/font>

select /*+ use_hash(t,t1) leading(t,t1) */ t.* from t,t1 where t.id=t1.id;

/*+ use_merge(table_1,table_2) */
在多表关联查询中�Q�指定��用merge join方式�q�行多表兌��?/span>

select /*+ use_merge(t,t1) */ t.* from t,t1 where t.id=t1.id;

/*+ no_use_nl(table_1,table_2) */
在多表关联查询中�Q�指定不使用nest loops方式�q�行多表兌��?/span>

select /*+ no_use_nl(t,t1) */ t.* from t,t1 where t.id=t1.id;

/*+ no_use_hash(table_1,table_2) */
在多表关联查询中�Q�指定不使用hash join方式�q�行多表兌��?/span>

select /*+ no_use_hash(t,t1) */ t.* from t,t1 where t.id=t1.id;

/*+ no_use_merge(table_1,table_2) */
在多表关联查询中�Q�指定不使用merge join方式�q�行多表兌��?/span>

select /*+ no_use_merge(t,t1) */ t.* from t,t1 where t.id=t1.id;

其他常用的hint

/*+ parallel(table_name n) */

在sql中指定执行的�q�行度，�q�个值将会覆盖自�w�的�q�行�?br />

select /*+ parallel(t 4) */ count(*) from t;

/*+ no_parallel(table_name) */

在sql中指定执行的不��用�ƈ�?br />

select /*+ no_parallel(t) */ count(*) from t;

/*+ append */以直接加载的方式��数据加载入�?

insert into t /*+ append */ select * from t;

/*+ dynamic_sampling(table_name n) */

讄��sql执行时动态采用的�U�别�Q�这个��别�ؓ0~10
select /*+ dynamic_sampling(t 4) */ * from t where id > 1234

/*+ cache(table_name) */
�q�行全表扫描时将table�|�于LRU列表的最�z�跃端，�c�M��于table的cache属�?br />

select /*+ full(employees) cache(employees) */ last_name from employees
附录hint表格

Hints for Optimization Approaches and Goals

ALL_ROWS The ALL_ROWS hint explicitly chooses the cost-based approach to optimize a statement block with a goal of best throughput (that is, minimum total resource consumption).

FIRST_ROWS The FIRST_ROWS hint explicitly chooses the cost-based approach to optimize a statement block with a goal of best response time (minimum resource usage to return first row). In newer Oracle version you should give a parameter with this hint: FIRST_ROWS(n) means that the optimizer will determine an executionplan to give a fast response for returning the first n rows.

CHOOSE The CHOOSE hint causes the optimizer to choose between the rule-based approach and the cost-based approach for a SQL statement based on the presence of statistics for the tables accessed by the statement

RULE The RULE hint explicitly chooses rule-based optimization for a statement block. This hint also causes the optimizer to ignore any other hints specified for the statement block. The RULE hint does not work any more in Oracle 10g.

Hints for Access Paths

FULL The FULL hint explicitly chooses a full table scan for the specified table. The syntax of the FULL hint is FULL(table) where table specifies the alias of the table (or table name if alias does not exist) on which the full table scan is to be performed.

ROWID The ROWID hint explicitly chooses a table scan by ROWID for the specified table. The syntax of the ROWID hint is ROWID(table) where table specifies the name or alias of the table on which the table access by ROWID is to be performed. (This hint depricated in Oracle 10g)

CLUSTER The CLUSTER hint explicitly chooses a cluster scan to access the specified table. The syntax of the CLUSTER hint is CLUSTER(table) where table specifies the name or alias of the table to be accessed by a cluster scan.

HASH The HASH hint explicitly chooses a hash scan to access the specified table. The syntax of the HASH hint is HASH(table) where table specifies the name or alias of the table to be accessed by a hash scan.

HASH_AJ The HASH_AJ hint transforms a NOT IN subquery into a hash anti-join to access the specified table. The syntax of the HASH_AJ hint is HASH_AJ(table) where table specifies the name or alias of the table to be accessed.(depricated in Oracle 10g)

INDEX The INDEX hint explicitly chooses an index scan for the specified table. The syntax of the INDEX hint is INDEX(table index) where:table specifies the name or alias of the table associated with the index to be scanned and index specifies an index on which an index scan is to be performed. This hint may optionally specify one or more indexes:

NO_INDEX The NO_INDEX hint explicitly disallows a set of indexes for the specified table. The syntax of the NO_INDEX hint is NO_INDEX(table index)

INDEX_ASC The INDEX_ASC hint explicitly chooses an index scan for the specified table. If the statement uses an index range scan, Oracle scans the index entries in ascending order of their indexed values.

INDEX_COMBINE If no indexes are given as arguments for the INDEX_COMBINE hint, the optimizer will use on the table whatever boolean combination of bitmap indexes has the best cost estimate. If certain indexes are given as arguments, the optimizer will try to use some boolean combination of those particular bitmap indexes. The syntax of INDEX_COMBINE is INDEX_COMBINE(table index).

INDEX_JOIN Explicitly instructs the optimizer to use an index join as an access path. For the hint to have a positive effect, a sufficiently small number of indexes must exist that contain all the columns required to resolve the query.

INDEX_DESC The INDEX_DESC hint explicitly chooses an index scan for the specified table. If the statement uses an index range scan, Oracle scans the index entries in descending order of their indexed values.

INDEX_FFS This hint causes a fast full index scan to be performed rather than a full table.

NO_INDEX_FFS Do not use fast full index scan (from Oracle 10g)

INDEX_SS Exclude range scan from query plan (from Oracle 10g)

INDEX_SS_ASC Exclude range scan from query plan (from Oracle 10g)

INDEX_SS_DESC Exclude range scan from query plan (from Oracle 10g)

NO_INDEX_SS The NO_INDEX_SS hint causes the optimizer to exclude a skip scan of the specified indexes on the specified table. (from Oracle 10g)

Hints for Query Transformations

NO_QUERY_TRANSFORMATION Prevents the optimizer performing query transformations. (from Oracle 10g)

USE_CONCAT The USE_CONCAT hint forces combined OR conditions in the WHERE clause of a query to be transformed into a compound query using the UNION ALL set operator. Normally, this transformation occurs only if the cost of the query using the concatenations is cheaper than the cost without them.

NO_EXPAND The NO_EXPAND hint prevents the optimizer from considering OR-expansion for queries having OR conditions or IN-lists in the WHERE clause. Usually, the optimizer considers using OR expansion and uses this method if it decides that the cost is lower than not using it.

REWRITE The REWRITE hint forces the optimizer to rewrite a query in terms of materialized views, when possible, without cost consideration. Use the REWRITE hint with or without a view list. If you use REWRITE with a view list and the list contains an eligible materialized view, then Oracle uses that view regardless of its cost.

NOREWRITE / NO_REWRITE In Oracle 10g renamed to NO_REWRITE. The NOREWRITE/NO_REWRITE hint disables query rewrite for the query block, overriding the setting of the parameter QUERY_REWRITE_ENABLED.

MERGE The MERGE hint lets you merge views in a query.

NO_MERGE The NO_MERGE hint causes Oracle not to merge mergeable views. This hint is most often used to reduce the number of possible permutations for a query and make optimization faster.

FACT The FACT hint indicated that the table should be considered as a fact table. This is used in the context of the star transformation.

NO_FACT The NO_FACT hint is used in the context of the star transformation to indicate to the transformation that the hinted table should not be considered as a fact table.

STAR_TRANSFORMATION The STAR_TRANSFORMATION hint makes the optimizer use the best plan in which the transformation has been used. Without the hint, the optimizer could make a query optimization decision to use the best plan generated without the transformation, instead of the best plan for the transformed query.

NO_STAR_TRANSFORMATION Do not use star transformation (from Oracle 10g)

UNNEST The UNNEST hint specifies subquery unnesting.

NO_UNNEST Use of the NO_UNNEST hint turns off unnesting for specific subquery blocks.

Hints for Join Orders

LEADING Give this hint to indicate the leading table in a join. This will indicate only 1 table. If you want to specify the whole order of tables, you can use the ORDERED hint. Syntax: LEADING(table)

ORDERED The ORDERED hint causes Oracle to join tables in the order in which they appear in the FROM clause. If you omit the ORDERED hint from a SQL statement performing a join , the optimizer chooses the order in which to join the tables. You may want to use the ORDERED hint to specify a join order if you know something about the number of rows selected from each table that the optimizer does not. Such information would allow you to choose an inner and outer table better than the optimizer could.

Hints for Join Operations

USE_NL The USE_NL hint causes Oracle to join each specified table to another row source with a nested loops join using the specified table as the inner table. The syntax of the USE_NL hint is USE_NL(table table) where table is the name or alias of a table to be used as the inner table of a nested loops join.

NO_USE_NL Do not use nested loop (from Oracle 10g)

USE_NL_WITH_INDEX Specifies a nested loops join. (from Oracle 10g)

USE_MERGE The USE_MERGE hint causes Oracle to join each specified table with another row source with a sort-merge join. The syntax of the USE_MERGE hint is USE_MERGE(table table) where table is a table to be joined to the row source resulting from joining the previous tables in the join order using a sort-merge join.

NO_USE_MERGE Do not use merge (from Oracle 10g)

USE_HASH The USE_HASH hint causes Oracle to join each specified table with another row source with a hash join. The syntax of the USE_HASH hint is USE_HASH(table table) where table is a table to be joined to the row source resulting from joining the previous tables in the join order using a hash join.

NO_USE_HASH Do not use hash (from Oracle 10g)

Hints for Parallel Execution

PARALLEL The PARALLEL hint allows you to specify the desired number of concurrent query servers that can be used for the query. The syntax is PARALLEL(table number number). The PARALLEL hint must use the table alias if an alias is specified in the query. The PARALLEL hint can then take two values separated by commas after the table name. The first value specifies the degree of parallelism for the given table, the second value specifies how the table is to be split among the instances of a parallel server. Specifying DEFAULT or no value signifies the query coordinator should examine the settings of the initialization parameters (described in a later section) to determine the default degree of parallelism.

NOPARALLEL / NO_PARALLEL The NOPARALLEL hint allows you to disable parallel scanning of a table, even if the table was created with a PARALLEL clause. In Oracle 10g this hint was renamed to NO_PARALLEL.

PQ_DISTRIBUTE The PQ_DISTRIBUTE hint improves the performance of parallel join operations. Do this by specifying how rows of joined tables should be distributed among producer and consumer query servers. Using this hint overrides decisions the optimizer would normally make.

NO_PARALLEL_INDEX The NO_PARALLEL_INDEX hint overrides a PARALLEL attribute setting on an index to avoid a parallel index scan operation.

Additional Hints

APPEND When the APPEND hint is used with the INSERT statement, data is appended to the table. Existing free space in the block is not used. If a table or an index is specified with nologging, this hint applied with an insert statement produces a direct path insert which reduces generation of redo.

NOAPPEND Overrides the append mode.

CACHE The CACHE hint specifies that the blocks retrieved for the table in the hint are placed at the most recently used end of the LRU list in the buffer cache when a full table scan is performed. This option is useful for small lookup tables. In the following example, the CACHE hint overrides the table default caching specification.

NOCACHE The NOCACHE hint specifies that the blocks retrieved for this table are placed at the least recently used end of the LRU list in the buffer cache when a full table scan is performed. This is the normal behavior of blocks in the buffer cache.

PUSH_PRED The PUSH_PRED hint forces pushing of a join predicate into the view.

NO_PUSH_PRED The NO_PUSH_PRED hint prevents pushing of a join predicate into the view.

PUSH_SUBQ The PUSH_SUBQ hint causes nonmerged subqueries to be evaluated at the earliest possible place in the execution plan.

NO_PUSH_SUBQ The NO_PUSH_SUBQ hint causes non-merged subqueries to be evaluated as the last step in the execution plan.

QB_NAME Specifies a name for a query block. (from Oracle 10g)

CURSOR_SHARING_EXACT Oracle can replace literals in SQL statements with bind variables, if it is safe to do so. This is controlled with the CURSOR_SHARING startup parameter. The CURSOR_SHARING_EXACT hint causes this behavior to be switched off. In other words, Oracle executes the SQL statement without any attempt to replace literals by bind variables.

DRIVING_SITE The DRIVING_SITE hint forces query execution to be done for the table at a different site than that selected by Oracle

DYNAMIC_SAMPLING The DYNAMIC_SAMPLING hint lets you control dynamic sampling to improve server performance by determining more accurate predicate selectivity and statistics for tables and indexes. You can set the value of DYNAMIC_SAMPLING to a value from 0 to 10. The higher the level, the more effort the compiler puts into dynamic sampling and the more broadly it is applied. Sampling defaults to cursor level unless you specify a table.

SPREAD_MIN_ANALYSIS This hint omits some of the compile time optimizations of the rules, mainly detailed dependency graph analysis, on spreadsheets. Some optimizations such as creating filters to selectively populate spreadsheet access structures and limited rule pruning are still used. (from Oracle 10g)

Hints with unknown status

MERGE_AJ The MERGE_AJ hint transforms a NOT IN subquery into a merge anti-join to access the specified table. The syntax of the MERGE_AJ hint is MERGE_AJ(table) where table specifies the name or alias of the table to be accessed.(depricated in Oracle 10g)

AND_EQUAL The AND_EQUAL hint explicitly chooses an execution plan that uses an access path that merges the scans on several single-column indexes. The syntax of the AND_EQUAL hint is AND_EQUAL(table index index) where table specifies the name or alias of the table associated with the indexes to be merged. and index specifies an index on which an index scan is to be performed. You must specify at least two indexes. You cannot specify more than five. (depricated in Oracle 10g)

STAR The STAR hint forces the large table to be joined last using a nested loops join on the index. The optimizer will consider different permutations of the small tables. (depricated in Oracle 10g)

BITMAP Usage: BITMAP(table_name index_name) Uses a bitmap index to access the table. (depricated ?)

HASH_SJ
Use a Hash Anti-Join to evaluate a NOT IN sub-query. Use this hint in the sub-query, not in the main query. Use this when your high volume NOT IN sub-query is using a FILTER or NESTED LOOPS join. Try MERGE_AJ if HASH_AJ refuses to work.(depricated in Oracle 10g)

NL_SJ Use a Nested Loop in a sub-query. (depricated in Oracle 10g)

NL_AJ Use an anti-join in a sub-query. (depricated in Oracle 10g)

ORDERED_PREDICATES (depricated in Oracle 10g)

EXPAND_GSET_TO_UNION (depricated in Oracle 10g)

参考至�Q�《让Oracle跑得更快》�K怀�q�著

Rabbit 2013-11-08 14:44 发表评论

Rabbit — Tue, 05 Nov 2013 06:31:00 GMT
Oracle中的锁定可以分�ؓ几类�Q?/span>
1、DML lock�Q�data lock�Q�，
2、DDL lock�Q�dictionary lock)
3、internal lock/latch�?/span>

DML lock又可以分为row lock和table lock。row lock在select.. for update/insert/update/delete旉��式自动��生，而table lock除了隐式产生�Q�也可以调用lock table in name来显�C�锁定�?/span>

如果不希望别的session lock/insert/update/delete表中��L��一行，只允许查询，可以用lock table table_name in exclusive mode�?X)�q�个锁定模式�U�别最高，�q�发度最��?/span>

如果允许别的session查询或用select for update锁定记录�Q�不允许insert/update/delete�Q�可以用
lock table table_name in share row exclusive mode�?SRX)

如果允许别的session查询或select for update以及lock table table_name in share mode�Q�只是不允许insert/update/delete�Q�可以用
lock table table_name in share mode�?share mode和share row exclusive mode的区别在于一个是非抢占式的而另一个是抢占式的。进入share row exclusive mode后其他session不能��L��你insert/update/delete�Q�而进入share mode后其他session也同样可以进入share mode�Q�进而阻止你对表的修攏V�?S)

�q�有两种锁定模式�Q�row share(RS)和row exclusive(RX)。他们允许的�q�发操作更多�Q�一般直接用DML语句自动获得�Q�而不用lock语句�?/span>
详细参考concepts文档中的"Type Of Locks"�Q?/span>
http://download-uk.oracle.com/docs/cd/B10501_01/server.920/a96524/c21cnsis.htm#2937

-------------------------------------
怎么unlock table 解锁

�Ҏ��一、kill session�Q?/span>

SQL> select object_id,session_id from v$locked_object; //注意session_id ��是上锁�?session标志
SQL> select username,sid,SERIAL# from v$session where sid=。�?      //�q�里的SID = session_id
SQL> alter system kill session 'id,serial#';     //杀死该session

�Ҏ��二、rollback/commit �l�止事务处理

ORACLE 大表建立索引的一些考虑

首先�Q?/span>应当考虑表空间和��盘�I�间是否��_��。我们知道烦引也是一�U�数据，在徏立烦引的时候势必也会占用大量表�I�间。因此在对一张大表徏立烦引的时候首先应当考虑的是�I�间定w��问题�?/span>
其次�Q�在对徏立烦引的时候要对表�q�行加锁�Q�因此应当注�?/span>操作在业务空闲的时候进�?/strong>�?/span>
性能调整�Ҏ��Q?/em>
首先应考虑IO�Q?物理上，应当��量把烦引与数据分散��C��同的��盘上�?逻辑上，数据表空间与索引表空间分开。这是在建烦引时应当��守的基本原�?/font>�?/span>
其次�Q?/span>在徏立烦引的时候要对表�q�行全表的扫描工�?/font>�Q�因此，应当考虑调大初始化参�?/span>db_file_multiblock_read_count的倹{��一般设�|��ؓ16或更�?/font>�?/span>
�?�ơ，建立索引除了要进行全表扫描外同时�q�要�Ҏ��据进行大量的排序操作�Q�因此，应当调整排序区的大小。在9I之前�Q?可以在SESSION�U�别上加大sort_area_size 的大��，比如讄��?00M或者更大�?I 以后�Q?如果初始化参数workarea_size_policy的��gؓTRUE�Q?则排序区从PGA_AGGREGATE_TARGET里自动分配获�?/font>

Rabbit 2013-11-05 14:31 发表评论

使用 EclEmma �q�行覆盖��试

Rabbit — Fri, 01 Nov 2013 01:43:00 GMT

覆盖��试是衡量测试质量的一个重要指标。在对一个��Y件��品进行了单元��试、组装测试、集成测试以及接受测试等�J�多的测试之后，我们能不能就此对软�g的质量��生一定的信心呢？�q�就需要我们对��试的质量进行考察。如果测试仅覆盖了代码的一��部分，那么不管我们写了多少��试用例�Q�我们也不能�怿�软�g质量是有保证的。相反，如果��试覆盖��C��软�g的绝大部分代码，我们��p��对��Y件的质量有一个合理的信心。本文将介绍一个优�U�的开源��Y件测试工�?EclEmma�Q�它能够对由 Java 语言�~�写的程序进行覆盖测试，从而对�E�序�q�行的结果生成详��的覆盖��试报告�?/p>
2007 �q?5 �?10 �?/p>

介绍

现在 IT 开发�h员比以往��M��时候都更加��x��试的重要性，没有�l�过良好��试的代码更�Ҏ��出问题。在极限�~�程中，��试驱动开发已�l�被证明是一�U�有效提高��Y件质量的�Ҏ��。在��试驱动的开发方式中�Q��Y件工�E�师在编写功能代码之前首先编写测试代码，�q�样能从最开始保证程序代码的正确性，�q�且能够在程序的每次演进时进行自动的回归��试。测试对于��Y件��品的成��|��L��臛_��重要的作用，在极限编�E�领域，甚至有�h提议��M��未经��试的代码都应该自动从发布的产品中删除。作者�ƈ不确信这个观�Ҏ��正确的，但是��试本��n的质量确实是一个需要高度关注的问题。测试的覆盖率是��试质量的一个重要指标，我们需要工��h��帮助我们�q�行对��Y件测试覆盖的考察�?/p>
EclEmma ��是�q�样一个能帮助开发�h员考察��试覆盖率的优秀�?Eclipse 开源插件。EclEmma 在覆盖测试领域是如此的优�U��Q�以致于它在�q�去不久�?2006 �q�成��Z�� Eclipse Community Awards Winners 册��选手。虽然最�?Eclipse Checkstyle Plugin 取得�?Best Open Source Eclipse-based Developer tool 的称��P��但我们也可以由此看到 EclEmma 对开发�h员的帮助是巨大的�Q�Eclipse Community Award 的具体信息可以参�?参考资�?/a>�Q��?/p>
提到 EclEmma 首先��p��说到著名�?Java 覆盖��试工具 Emma。Emma 是一个在 SourceForge 上进行的开源项目（参阅参考资�?/a>�Q�。从某种�E�度上说�Q�EclEmma 可以看作�?Emma 的一个图形界面。在本文�?a >参考文�?/a>中，可以看到专门讲述使用 Emma 的技术文章�?/p>
Emma 的作者开�?Emma 之初�Q�程序员已经有了各种各样优秀的开�?Java 开发工兗��D例来��_��我们有优�U�的集成开发环�?Eclipse�Q�有开源的 JDK�Q�有单元��试工具 JUnit�Q�有 Ant �q�样的项目管理工��P��我们�q�可以用 CVS �?SubVersion 来进行源代码版本的维护。当时看来，也许唯一�~�少的就是一个开源的覆盖��试工具了。Emma ��是��Z��填补�q�项�I�白而生的。现在的情况已经�?Emma 诞生的时候不一��L��。时至今日，我们已经有了不少的覆盖测试工兗��例�?Coverlipse 是一个基�?Eclipse 的覆盖测试插件。其他还�?Cobertura�Q�Quilt �?JCoverage �{�。但�?Emma ��h��一些非�怼��U�的特性��得它更适合被广泛的使用。和 Coverlipse �{�工��h��h��Q�Emma 是开源的�Q�同时它对应用程序执行速度的媄响非常小�?/p>
EclEmma 的出现��I补了 Emma 用户一个大的遗�?---- �~�Z��囑�Ş界面以及寚w��成开发环境的支持。将 Eclipse �?Emma �q�两个在各自领域最��Z��U�的工��L��合�v来，�q�就�?EclEmma 为我们提供的。接下来�Q�我们就要在后箋章节中和读者朋友一��L��?EclEmma 为开发�h员提供了什么�?/p>

回页�?/a>

安装 EclEmma 插�g

安装 EclEmma 插�g的过�E�和大部�?Eclipse 插�g相同�Q�我们既可以通过 Eclipse 标准�?Update 机制来远�E�安�?EclEmma 插�g�Q?a >�?1�Q�，也可以从站点�Q�参�?参考资�?/a>�Q�下�?zip 文�g�q�解压到 eclipse 所在的目录中�?/p>
�?1 ��d�� EclEmma 更新站点

不管采用何种方式来安�?EclEmma�Q�安装完成�ƈ重新启动 Eclipse 之后�Q�工��h��上应该出��C��个新的按钮：

�?2 新增的覆盖测试按�?/h5>

回页�?/a>

使用 EclEmma ��试 Java �E�序

��Z��实验 EclEmma 的特性，我们首先�?Eclipse �?Workspace 中徏立一个名�U�Cؓ test.emma 的新 Java ��目。接下来�Q�我们在其中建立一�?HelloWorld �c�，其代码如下所�C�：

清单 1 用于��试 EclEmma 的代�?/h5>
package test.emma; public class HelloWorld { /** * @param args */ public static void main(String[] args) { int rand = (int) (Math.random()*100); if(rand%2==0){ System.out.println( "Hello, world! 0"); } else System.out.println("Hello, world! 1"); int result = rand%2==0? rand+rand:rand*rand; System.out.println(result); } }

接下来，我们通过 EclEmma �q�行 HelloWorld.main() 函数�?/p>
�?3 �?Java 应用�E�序�q�行覆盖��试

执行完毕之后�Q�我们正在编�?HelloWorld.java 的窗口将会变成如下所�C�：

�?4 �q�行覆盖��试的结�?/h5>
�?Java �~�辑器中�Q�EclEmma 用不同的色彩标示了源代码的测试情��c��其中，�l�色的行表示该行代码被完整的执行�Q�红色部分表�C��行代码根本没有被执行�Q�而黄色的行表明该行代码部分被执行。黄色的行通常出现在单行代码包含分支的情况�Q�例�?�?4 中的 16 行就昄��为黄艌Ӏ�由于程序中有一个随机确定的分支�Q�因此读者的�H�口可能与这里稍有不同（11 行或�?14 行中有且只有一个红色的行）�?/p>
除了在源代码�~�辑�H�口直接�q�行着色之外，EclEmma �q�提供了一个单独的视图来统计程序的覆盖��试率�?/p>
�?5 察看�E�序的覆盖测试率

EclEmma 提供�?Coverage 视图能够分层的显�C�Z��码的覆盖��试率，�?5 中的信息表明我们�?HelloWorld 的一�ơ运行覆盖了大约 68.6% 的代码�?/p>
惛_��一�ơ运行中覆盖所有的代码通常比较困难�Q�如果能把多�ơ测试的覆盖数据�l�合��h��q�行察看�Q�那么我们就能更方便的掌握多�ơ测试的��试效果。EclEmma 提供了这��L��功能。现在，让我们重复数�ơ对 HelloWorld 的覆盖测试。我们注意到 Coverage 视图��L��昄��最新完成的一�ơ覆盖测试。事实上�Q�EclEmma 为我们保存了所有的��试�l�果。接下来�Q�我们将通过 Coverage 视图的工��h��钮来�l�合多次覆盖��试的结果�?/p>
�?6 用于�l�合多次覆盖��试�l�果的工��h��按钮

当我们多�ơ运�?Coverage 之后�Q�我们可以单�?�?6 所�C�工��h��按钮。之后，一个对话框��被弹出以供用户选择需要合�q�的覆盖��试�?/p>
�?7 选择需要合�q�的覆盖��试�l�果

在合�q�完成之后，我们可以观察�?Java �~�辑器和 Coverage 视图中都昄��了合�q�之后的�l�果�Q?/p>
�?8 察看合�ƈ后的覆盖��试�l�果

�?8 中，我们可以看到�Q�通过多次�q�行覆盖��试�Q�最�l�我们的代码辑ֈ��?91.4% 的测试覆盖率。有��的是，图中�W�三行代码被标记为红�Ԍ��而此行代码实际上是不可执行的。奥妙在于，我们没有生成��M�� HelloWorld �cȝ��实例�Q�因此缺省构造函数没有被调用�Q��?EclEmma ��这个特�D�代码的覆盖状态标记在�c�d��明的�W�一行�?/p>

回页�?/a>

EclEmma 的高�U�特�?/h2>
如果 EclEmma 只能��试 Java Application 的测试覆盖率�Q�那么它相对命��o行版本的 Emma 来说�Q�提供的增强��׃��多了。相反，EclEmma 提供了很多与 Eclipse 紧密�l�合的功能。它不仅能测�?Java Application�Q�还能计��?JUnit 单元��试�Q�对 Eclipse 插�g��试的覆盖率。从 �?9 中我们可以看�?EclEmma 目前支持四种�c�d��的程序�?/p>
�?9 EclEmma 的配�|�页�?/h5>
��Z��了解 EclEmma 是如何获得覆盖测试数据的�Q�我们需要先�?Emma 有初步的了解。通常代码覆盖��试工具都需要对被执行的代码�q�行修改。�?Emma 提供了两�U�方式来完成�q��g事�?/p>
预插入模式：对程序进行测量之前，需要采�?Emma 提供的工具对 class 文�g或�?jar 文�g�q�行修改。修改完成之后的代码可以立刻被执行。覆盖测试的�l�果��会被存攑ֈ�指定的文件中�?/li>
��x��插入模式�Q?/strong>��x��插入模式不需要事先对代码�q�行修改。相反，对代码的修改是通过一�?Emma 定制�?Class loader�Q�类载入器）�q�行的。这�U�方式的优点很明显，我们不需要对 class 或�?jar 文�g�q�行��M��修改。缺�Ҏ��我们��Z��获得��试的结果，需要用 Emma 提供的命�?emmarun 来执�?Java 应用�E�序�?/li>

使用��x��插入模式的优点很明显�Q�class 文�g�?jar 文�g不会被修攏V��而预插入模式的应用范围更为广泛，对于某些需要嵌入到框架中运行的代码来说�Q�例�?EJB�Q�，我们只能使用预插入模式。EclEmma 仅仅使用�?Emma 的预插入模式来工作，不过 EclEmma �~�省会在临时目录中创�?class 文�g�?jar 文�g的副本来�q�行修改�Q�因此在 workspace �?class �?jar 文�g仍然保持原样。虽然听上去很好�Q�但是由于需要修�?classpath 来��用修改过�?class �?jar 文�g�Q�对于不能修�?classpath 的应用（例如 Eclipse RCP �?JUnit Plugin Test�Q�来��_��我们�q�是只能选择修改 workspace 中的 class 文�g�?jar 文�g。对�?Java Application �?JUnit �c�d��的覆盖测试，我们可以在配�|�对话框中选中“In-place instrumentation”��Ҏ��指定直接修改 Workspace 中的 .class 文�g�?.jar 文�g�?/p>

Rabbit 2013-11-01 09:43 发表评论

��Z��Xfire SOAP Header的WebService安全验证教程 .

Rabbit — Thu, 24 Oct 2013 08:28:00 GMT

WebSerice是一�U�开攄��web服务�Q��Q何�h都可以访问，但我们有时候需要考虑只有付费用户才能使用WS,所以，我们��需要对WS加入安全验证机制�Q�当�Ӟ��可以利用防火墙的IP�q��o�Q�web应用的配�|�从最外层去隔��非法用��P��但在内层�Q�我们也可以使用SOAP Header的方式，由客��L��发送验证数据，服务端验通过后基WS讉K��权限

首先�Ҏ��我的�q�篇Blog

http://blog.csdn.net/daryl715/archive/2007/07/25/1707161.aspx

配置WS Server和WS Client�Q?font color="#ff0000">其中Client端的��试代码�c�d��由Client改�ؓClientTest,因�ؓ我们要用到Xfire的一个名为Client的类

首先我们�~�写服务端验证类�l�承AbstractHandler

package test;

import org.codehaus.xfire.MessageContext;
import org.codehaus.xfire.handler.AbstractHandler;
import org.jdom.Element;

public class AuthenticationHandler extends AbstractHandler ...{

    public void invoke(MessageContext cfx) throws Exception ...{
           if(cfx.getInMessage().getHeader() == null)
           ...{
               throw new org.codehaus.xfire.fault.XFireFault("��h��必须包含验证信息",org.codehaus.xfire.fault.XFireFault.SENDER);
           }
           Element token=cfx.getInMessage().getHeader().getChild("AuthenticationToken");
           if (token == null)
           ...{
            throw new org.codehaus.xfire.fault.XFireFault("��h��必须包含�w�䆾验证信息", org.codehaus.xfire.fault.XFireFault.SENDER);
           }

              String username = token.getChild("Username").getValue();
              String password = token.getChild("Password").getValue();
              try
              ...{
                  //�q�行�w�䆾验证 �Q�只有abcd@1234的用户�ؓ授权用户
                 if(username.equals("abcd") && password.equals("1234"))
                  //�q�语句不昄��
                  System.out.println("�w�䆾验证通过");
                 else throw new Exception();
              }
              catch (Exception e)
              ...{
                  throw new   org.codehaus.xfire.fault.XFireFault("非法的用户名和密�?/span>",   org.codehaus.xfire.fault.XFireFault.SENDER);
              }

          }

}

下面是Client发送授权信�?/p>

package test;

import org.codehaus.xfire.MessageContext;
import org.codehaus.xfire.handler.AbstractHandler;
import org.jdom.Element;

public class ClientAuthenticationHandler extends AbstractHandler ...{

     private String username = null;

     private String password = null;

     public ClientAuthenticationHandler() ...{

     }

     public ClientAuthenticationHandler(String username,String password) ...{

         this.username = username;

         this.password = password;
     }

     public void setUsername(String username) ...{

         this.username = username;

     }

     public void setPassword(String password) ...{

         this.password = password;

     }

     public void invoke(MessageContext context) throws Exception ...{

         //为SOAP Header构造验证信�?/span>
         Element el = new Element("header");
         context.getOutMessage().setHeader(el);
         Element auth = new Element("AuthenticationToken");
         Element username_el = new Element("Username");
         username_el.addContent(username);
         Element password_el = new Element("Password");
         password_el.addContent(password);
         auth.addContent(username_el);
         auth.addContent(password_el);
         el.addContent(auth);
     }

}

为ClientTest.java加入以下代码

XFireProxy proxy = (XFireProxy)Proxy.getInvocationHandler(service);
Client client = proxy.getClient();
client.addOutHandler(new ClientAuthenticationHandler("abcd1","1234"));

�{�等�Q�还没有完，修改Services.xm为WS�l�定Handler



xml version="1.0" encoding="UTF-8"?>

<beans>
<service xmlns="http://xfire.codehaus.org/config/1.0">
<name>HelloServicename>
<namespace>http://test/HelloServicenamespace>
<serviceClass>test.IHelloServiceserviceClass>
<implementationClass>test.HelloServiceImplimplementationClass>
<inHandlers>
<handler  handlerClass ="test.AuthenticationHandler" >handler >
inHandlers>
service>
beans>

�q�样我们��完成了�~�码�Q�下面启动tomcat�Q�运行客��L��代码�Q�本文�ؓabcd@1234位授权用��P��使用abcd@1234,可以正常讉K��WS,如果用错误帐��P��则会有以下异�?/font>

Exception in thread "main" org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: 非法的用户名和密�?br />org.codehaus.xfire.fault.XFireFault: 非法的用户名和密�?br />    at org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(Soap11FaultSerializer.java:31)
    at org.codehaus.xfire.fault.SoapFaultSerializer.readMessage(SoapFaultSerializer.java:28)
    at org.codehaus.xfire.soap.handler.ReadHeadersHandler.checkForFault(ReadHeadersHandler.java:111)
    at org.codehaus.xfire.soap.handler.ReadHeadersHandler.invoke(ReadHeadersHandler.java:67)
    at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
    at org.codehaus.xfire.client.Client.onReceive(Client.java:406)
    at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:139)
    at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
    at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
    at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
    at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
    at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
    at org.codehaus.xfire.client.Client.invoke(Client.java:336)
    at org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)
    at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
    at $Proxy0.getUser(Unknown Source)
    at test.ClientTest.main(ClientTest.java:39)

如果不在CientTest加以下增加Heade则会有以下异�?/p>
XFireProxy proxy = (XFireProxy)Proxy.getInvocationHandler(service);
Client client = proxy.getClient();
client.addOutHandler(new ClientAuthenticationHandler("abcd1","1234"));

Exception in thread "main" org.codehaus.xfire.XFireRuntimeException: Could not invoke service.. Nested exception is org.codehaus.xfire.fault.XFireFault: ��h��必须包含验证信息
org.codehaus.xfire.fault.XFireFault: ��h��必须包含验证信息
    at org.codehaus.xfire.fault.Soap11FaultSerializer.readMessage(Soap11FaultSerializer.java:31)
    at org.codehaus.xfire.fault.SoapFaultSerializer.readMessage(SoapFaultSerializer.java:28)
    at org.codehaus.xfire.soap.handler.ReadHeadersHandler.checkForFault(ReadHeadersHandler.java:111)
    at org.codehaus.xfire.soap.handler.ReadHeadersHandler.invoke(ReadHeadersHandler.java:67)
    at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
    at org.codehaus.xfire.client.Client.onReceive(Client.java:406)
    at org.codehaus.xfire.transport.http.HttpChannel.sendViaClient(HttpChannel.java:139)
    at org.codehaus.xfire.transport.http.HttpChannel.send(HttpChannel.java:48)
    at org.codehaus.xfire.handler.OutMessageSender.invoke(OutMessageSender.java:26)
    at org.codehaus.xfire.handler.HandlerPipeline.invoke(HandlerPipeline.java:131)
    at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:79)
    at org.codehaus.xfire.client.Invocation.invoke(Invocation.java:114)
    at org.codehaus.xfire.client.Client.invoke(Client.java:336)
    at org.codehaus.xfire.client.XFireProxy.handleRequest(XFireProxy.java:77)
    at org.codehaus.xfire.client.XFireProxy.invoke(XFireProxy.java:57)
    at $Proxy0.getUser(Unknown Source)
    at test.ClientTest.main(ClientTest.java:35)

Rabbit 2013-10-24 16:28 发表评论

java实现��单的单点��d��(转蝲)

Rabbit — Fri, 18 Oct 2013 01:44:00 GMT
     摘要: 摘要�Q�单点登录（SSO�Q�的技术被��来��广泛地�q�用到各个领域的软�g�pȝ��当中。本文从业务的角度分析了单点��d��的需求和应用领域�Q�从技术本�w�的角度分析了单点登录技术的内部机制和实现手�D�，�q�且�l�出Web-SSO和桌面SSO的实现、源代码和详�l�讲解；�q�从安全和性能的角度对现有的实现技术进行进一步分析，指出相应的风险和需要改�q�的斚w��。本文除了从多个斚w��和角度给��Z��对单点登录（SSO�Q�的全面分析...  阅读全文

Rabbit 2013-10-18 09:44 发表评论

解决IE下Iframe的Session丢失

Rabbit — Sun, 09 Jun 2013 07:57:00 GMT

�ȝ��面��用的是Iframe做的动态内容嵌�?需要登�?但是每次��h�� session 都失�?...
整个应用在FF下是正常的，但是在IE下每�ơ点��M��一��늚�时候都要重新登录。经�q�调试发现刷新后��h��采用了新�?sessionId�Q�于是怀疑到了是Iframe的问题。在�|�上搜了一下，果真是IE的Iframe问题。IE6/IE7支持的P3P(Platform for Privacy Preferences Project (P3P) specification)协议默认��L��W�三�Ҏ��隐私安全声明的cookie�Q�Firefox目前�q�不支持P3P安全�?性，firefox中不存在此问题�?br />具体的解��x��式是在登录的Action处理�Ҏ��?/span>加上
response.setHeader("P3P","CP=CAO PSA OUR IDC DSP COR ADM DEVi TAIi PSD IVAi IVDi CONi HIS IND CNT");
问题搞定�Q?/p>

Rabbit 2013-06-09 15:57 发表评论

struts 2标签样式问题

Rabbit — Wed, 05 Jun 2013 02:29:00 GMT

初学struts2�Q�在头脑中一直在想一个问题，��是对于struts2 �Q�当应用其自�w�的标签�Ӟ��例如�Q?/p>

当查看源代码时�ؓ�Q?/p>

自动��d��的table tr td 标签�Q�但如果�?一行显�C�多列怎么办？
�|�上查了查，有好多奇怪的解决办法�Q�比如说通过在页面上判断�Q�看什么时候输�?lt;tr> 标签�Q�但我认为，struts2�q�样做，那也太不人道了，后终于查到原因，现�ȝ��如下�Q?/p>
原理�Q�在struts2中加入了theme(主题�Q�的概念�Q�通过讄��不同的主题，可以让struts的代码输��Z��同的html代码�Q�你也就相应得到不同的布局效果�?/p>
问题一�Q�Struts2有哪些主题？
Struts2提供了三�U�主题，ajax, simple, xhtml�Q�它默认的是xhtml主题�Q�当然你可以写�Q意个你自��q��主题,我们�U�C��定义主题
问题二：Struts2怎么改？
有两�U�方法可以解�?
1.��单的�Ҏ��Q�也很实用）
在Struts.xml中，加上下一行代码就可以�?/p>
代表所有的��面采用的都�?simple主题了，�q�时它输出的��面�Q�不回添加�Q何多余的代码�Q�比�?table tr td �{�，我们��可以像其他�~�辑��面的方式编辑页面的风格�?/p>
或�?�?
struts2每个标签都有theme属�?/p>
2.在Struts.properties里改�Q?/p>
#讄��主题
struts.ui.theme=simple
可见另一��：struts.properties

Rabbit 2013-06-05 10:29 发表评论

Rabbit — Mon, 21 Jan 2013 07:51:00 GMT

ORACLE�?/span>Like�?/span>Instr模糊查询性能大比�?/span>

instr(title,'手册')>0  相当�?/span>  title like '%手册%'

instr(title,'手册')=1  相当�?/span>  title like '手册%'

instr(title,'手册')=0  相当�?/span>  title not like '%手册%'

t表中��近�?/span>1100万数据，很多时候，我们要进行字�W�串匚w��Q�在SQL语句中，我们通常使用like来达到我们搜索的目标。但�l�过实际��试发现�Q?/span>like的效率与instr函数差别相当大。下面是一些测试结果：
SQL> set timing on
SQL> select count(*) from t where instr(title,'手册')>0;
COUNT(*)
----------
     65881
Elapsed: 00:00:11.04
SQL> select count(*) from t where title like '%手册%';
COUNT(*)
----------
     65881
Elapsed: 00:00:31.47
SQL> select count(*) from t where instr(title,'手册')=0;
COUNT(*)
----------
11554580
Elapsed: 00:00:11.31
SQL> select count(*) from t where title not like '%手册%';
COUNT(*)
----------
11554580
另外�Q�我在结另外一�?/span>2亿多的表�Q��?/span>8个�ƈ行，使用like查询很久都不出来�l�果�Q�但使用instr,4分钟卛_��成查找，性能是相当的好。这些小技巧用好，工作效率提高不少。通过上面的测试说明，ORACLE内徏的一些函敎ͼ�是经�q�相当程度的优化的�?/span>

instr(title,’aaa’)>0 相当于like
instr(title,’aaa’)=0 相当于not like

�Ҏ��用法�Q?/span>

select   id, name from users where instr('101914, 104703', id) > 0;
  它等价于
select   id, name from users where id = 101914 or id = 104703;

使用Oracle�?/span>instr函数与烦引配合提高模�p�查询的效率
一般来��_��?/span>Oracle数据库中�Q�我们对tb表的name字段�q�行模糊查询会采用下面两�U�方式：
1.select * from tb where name like '%XX%';
2.select * from tb where instr(name,'XX')>0;

若是�?/span>name字段上没有加索引�Q�两者效率差不多�Q�基本没有区别�?/span>

为提高效率，我们�?/span>name字段上可以加上非唯一性烦引：
create index idx_tb_name on tb(name);

�q�样�Q�再使用
select * from tb where instr(name,'XX')>0;
�q�样的语句查询，效率可以提高不少�Q�表数据量越大时两者差别越大。但也要��֏��?/span>name字段加上索引�?/span>DML语句会��索引数据重新排序的媄响�?/span>

Rabbit 2013-01-21 15:51 发表评论

Hints for Optimization Approaches and Goals
ALL_ROWS	The ALL_ROWS hint explicitly chooses the cost-based approach to optimize a statement block with a goal of best throughput (that is, minimum total resource consumption).
FIRST_ROWS	The FIRST_ROWS hint explicitly chooses the cost-based approach to optimize a statement block with a goal of best response time (minimum resource usage to return first row). In newer Oracle version you should give a parameter with this hint: FIRST_ROWS(n) means that the optimizer will determine an executionplan to give a fast response for returning the first n rows.
CHOOSE	The CHOOSE hint causes the optimizer to choose between the rule-based approach and the cost-based approach for a SQL statement based on the presence of statistics for the tables accessed by the statement
RULE	The RULE hint explicitly chooses rule-based optimization for a statement block. This hint also causes the optimizer to ignore any other hints specified for the statement block. The RULE hint does not work any more in Oracle 10g.
Hints for Access Paths
FULL	The FULL hint explicitly chooses a full table scan for the specified table. The syntax of the FULL hint is FULL(table) where table specifies the alias of the table (or table name if alias does not exist) on which the full table scan is to be performed.
ROWID	The ROWID hint explicitly chooses a table scan by ROWID for the specified table. The syntax of the ROWID hint is ROWID(table) where table specifies the name or alias of the table on which the table access by ROWID is to be performed. (This hint depricated in Oracle 10g)
CLUSTER	The CLUSTER hint explicitly chooses a cluster scan to access the specified table. The syntax of the CLUSTER hint is CLUSTER(table) where table specifies the name or alias of the table to be accessed by a cluster scan.
HASH	The HASH hint explicitly chooses a hash scan to access the specified table. The syntax of the HASH hint is HASH(table) where table specifies the name or alias of the table to be accessed by a hash scan.
HASH_AJ	The HASH_AJ hint transforms a NOT IN subquery into a hash anti-join to access the specified table. The syntax of the HASH_AJ hint is HASH_AJ(table) where table specifies the name or alias of the table to be accessed.(depricated in Oracle 10g)
INDEX	The INDEX hint explicitly chooses an index scan for the specified table. The syntax of the INDEX hint is INDEX(table index) where:table specifies the name or alias of the table associated with the index to be scanned and index specifies an index on which an index scan is to be performed. This hint may optionally specify one or more indexes:
NO_INDEX	The NO_INDEX hint explicitly disallows a set of indexes for the specified table. The syntax of the NO_INDEX hint is NO_INDEX(table index)
INDEX_ASC	The INDEX_ASC hint explicitly chooses an index scan for the specified table. If the statement uses an index range scan, Oracle scans the index entries in ascending order of their indexed values.
INDEX_COMBINE	If no indexes are given as arguments for the INDEX_COMBINE hint, the optimizer will use on the table whatever boolean combination of bitmap indexes has the best cost estimate. If certain indexes are given as arguments, the optimizer will try to use some boolean combination of those particular bitmap indexes. The syntax of INDEX_COMBINE is INDEX_COMBINE(table index).
INDEX_JOIN	Explicitly instructs the optimizer to use an index join as an access path. For the hint to have a positive effect, a sufficiently small number of indexes must exist that contain all the columns required to resolve the query.
INDEX_DESC	The INDEX_DESC hint explicitly chooses an index scan for the specified table. If the statement uses an index range scan, Oracle scans the index entries in descending order of their indexed values.
INDEX_FFS	This hint causes a fast full index scan to be performed rather than a full table.
NO_INDEX_FFS	Do not use fast full index scan (from Oracle 10g)
INDEX_SS	Exclude range scan from query plan (from Oracle 10g)
INDEX_SS_ASC	Exclude range scan from query plan (from Oracle 10g)
INDEX_SS_DESC	Exclude range scan from query plan (from Oracle 10g)
NO_INDEX_SS	The NO_INDEX_SS hint causes the optimizer to exclude a skip scan of the specified indexes on the specified table. (from Oracle 10g)
Hints for Query Transformations
NO_QUERY_TRANSFORMATION	Prevents the optimizer performing query transformations. (from Oracle 10g)
USE_CONCAT	The USE_CONCAT hint forces combined OR conditions in the WHERE clause of a query to be transformed into a compound query using the UNION ALL set operator. Normally, this transformation occurs only if the cost of the query using the concatenations is cheaper than the cost without them.
NO_EXPAND	The NO_EXPAND hint prevents the optimizer from considering OR-expansion for queries having OR conditions or IN-lists in the WHERE clause. Usually, the optimizer considers using OR expansion and uses this method if it decides that the cost is lower than not using it.
REWRITE	The REWRITE hint forces the optimizer to rewrite a query in terms of materialized views, when possible, without cost consideration. Use the REWRITE hint with or without a view list. If you use REWRITE with a view list and the list contains an eligible materialized view, then Oracle uses that view regardless of its cost.
NOREWRITE / NO_REWRITE	In Oracle 10g renamed to NO_REWRITE. The NOREWRITE/NO_REWRITE hint disables query rewrite for the query block, overriding the setting of the parameter QUERY_REWRITE_ENABLED.
MERGE	The MERGE hint lets you merge views in a query.
NO_MERGE	The NO_MERGE hint causes Oracle not to merge mergeable views. This hint is most often used to reduce the number of possible permutations for a query and make optimization faster.
FACT	The FACT hint indicated that the table should be considered as a fact table. This is used in the context of the star transformation.
NO_FACT	The NO_FACT hint is used in the context of the star transformation to indicate to the transformation that the hinted table should not be considered as a fact table.
STAR_TRANSFORMATION	The STAR_TRANSFORMATION hint makes the optimizer use the best plan in which the transformation has been used. Without the hint, the optimizer could make a query optimization decision to use the best plan generated without the transformation, instead of the best plan for the transformed query.
NO_STAR_TRANSFORMATION	Do not use star transformation (from Oracle 10g)
UNNEST	The UNNEST hint specifies subquery unnesting.
NO_UNNEST	Use of the NO_UNNEST hint turns off unnesting for specific subquery blocks.
Hints for Join Orders
LEADING	Give this hint to indicate the leading table in a join. This will indicate only 1 table. If you want to specify the whole order of tables, you can use the ORDERED hint. Syntax: LEADING(table)
ORDERED	The ORDERED hint causes Oracle to join tables in the order in which they appear in the FROM clause. If you omit the ORDERED hint from a SQL statement performing a join , the optimizer chooses the order in which to join the tables. You may want to use the ORDERED hint to specify a join order if you know something about the number of rows selected from each table that the optimizer does not. Such information would allow you to choose an inner and outer table better than the optimizer could.
Hints for Join Operations
USE_NL	The USE_NL hint causes Oracle to join each specified table to another row source with a nested loops join using the specified table as the inner table. The syntax of the USE_NL hint is USE_NL(table table) where table is the name or alias of a table to be used as the inner table of a nested loops join.
NO_USE_NL	Do not use nested loop (from Oracle 10g)
USE_NL_WITH_INDEX	Specifies a nested loops join. (from Oracle 10g)
USE_MERGE	The USE_MERGE hint causes Oracle to join each specified table with another row source with a sort-merge join. The syntax of the USE_MERGE hint is USE_MERGE(table table) where table is a table to be joined to the row source resulting from joining the previous tables in the join order using a sort-merge join.
NO_USE_MERGE	Do not use merge (from Oracle 10g)
USE_HASH	The USE_HASH hint causes Oracle to join each specified table with another row source with a hash join. The syntax of the USE_HASH hint is USE_HASH(table table) where table is a table to be joined to the row source resulting from joining the previous tables in the join order using a hash join.
NO_USE_HASH	Do not use hash (from Oracle 10g)
Hints for Parallel Execution
PARALLEL	The PARALLEL hint allows you to specify the desired number of concurrent query servers that can be used for the query. The syntax is PARALLEL(table number number). The PARALLEL hint must use the table alias if an alias is specified in the query. The PARALLEL hint can then take two values separated by commas after the table name. The first value specifies the degree of parallelism for the given table, the second value specifies how the table is to be split among the instances of a parallel server. Specifying DEFAULT or no value signifies the query coordinator should examine the settings of the initialization parameters (described in a later section) to determine the default degree of parallelism.
NOPARALLEL / NO_PARALLEL	The NOPARALLEL hint allows you to disable parallel scanning of a table, even if the table was created with a PARALLEL clause. In Oracle 10g this hint was renamed to NO_PARALLEL.
PQ_DISTRIBUTE	The PQ_DISTRIBUTE hint improves the performance of parallel join operations. Do this by specifying how rows of joined tables should be distributed among producer and consumer query servers. Using this hint overrides decisions the optimizer would normally make.
NO_PARALLEL_INDEX	The NO_PARALLEL_INDEX hint overrides a PARALLEL attribute setting on an index to avoid a parallel index scan operation.
Additional Hints
APPEND	When the APPEND hint is used with the INSERT statement, data is appended to the table. Existing free space in the block is not used. If a table or an index is specified with nologging, this hint applied with an insert statement produces a direct path insert which reduces generation of redo.
NOAPPEND	Overrides the append mode.
CACHE	The CACHE hint specifies that the blocks retrieved for the table in the hint are placed at the most recently used end of the LRU list in the buffer cache when a full table scan is performed. This option is useful for small lookup tables. In the following example, the CACHE hint overrides the table default caching specification.
NOCACHE	The NOCACHE hint specifies that the blocks retrieved for this table are placed at the least recently used end of the LRU list in the buffer cache when a full table scan is performed. This is the normal behavior of blocks in the buffer cache.
PUSH_PRED	The PUSH_PRED hint forces pushing of a join predicate into the view.
NO_PUSH_PRED	The NO_PUSH_PRED hint prevents pushing of a join predicate into the view.
PUSH_SUBQ	The PUSH_SUBQ hint causes nonmerged subqueries to be evaluated at the earliest possible place in the execution plan.
NO_PUSH_SUBQ	The NO_PUSH_SUBQ hint causes non-merged subqueries to be evaluated as the last step in the execution plan.
QB_NAME	Specifies a name for a query block. (from Oracle 10g)
CURSOR_SHARING_EXACT	Oracle can replace literals in SQL statements with bind variables, if it is safe to do so. This is controlled with the CURSOR_SHARING startup parameter. The CURSOR_SHARING_EXACT hint causes this behavior to be switched off. In other words, Oracle executes the SQL statement without any attempt to replace literals by bind variables.
DRIVING_SITE	The DRIVING_SITE hint forces query execution to be done for the table at a different site than that selected by Oracle
DYNAMIC_SAMPLING	The DYNAMIC_SAMPLING hint lets you control dynamic sampling to improve server performance by determining more accurate predicate selectivity and statistics for tables and indexes. You can set the value of DYNAMIC_SAMPLING to a value from 0 to 10. The higher the level, the more effort the compiler puts into dynamic sampling and the more broadly it is applied. Sampling defaults to cursor level unless you specify a table.
SPREAD_MIN_ANALYSIS	This hint omits some of the compile time optimizations of the rules, mainly detailed dependency graph analysis, on spreadsheets. Some optimizations such as creating filters to selectively populate spreadsheet access structures and limited rule pruning are still used. (from Oracle 10g)
Hints with unknown status
MERGE_AJ	The MERGE_AJ hint transforms a NOT IN subquery into a merge anti-join to access the specified table. The syntax of the MERGE_AJ hint is MERGE_AJ(table) where table specifies the name or alias of the table to be accessed.(depricated in Oracle 10g)
AND_EQUAL	The AND_EQUAL hint explicitly chooses an execution plan that uses an access path that merges the scans on several single-column indexes. The syntax of the AND_EQUAL hint is AND_EQUAL(table index index) where table specifies the name or alias of the table associated with the indexes to be merged. and index specifies an index on which an index scan is to be performed. You must specify at least two indexes. You cannot specify more than five. (depricated in Oracle 10g)
STAR	The STAR hint forces the large table to be joined last using a nested loops join on the index. The optimizer will consider different permutations of the small tables. (depricated in Oracle 10g)
BITMAP	Usage: BITMAP(table_name index_name) Uses a bitmap index to access the table. (depricated ?)
HASH_SJ	Use a Hash Anti-Join to evaluate a NOT IN sub-query. Use this hint in the sub-query, not in the main query. Use this when your high volume NOT IN sub-query is using a FILTER or NESTED LOOPS join. Try MERGE_AJ if HASH_AJ refuses to work.(depricated in Oracle 10g)
NL_SJ	Use a Nested Loop in a sub-query. (depricated in Oracle 10g)
NL_AJ	Use an anti-join in a sub-query. (depricated in Oracle 10g)
ORDERED_PREDICATES	(depricated in Oracle 10g)
EXPAND_GSET_TO_UNION	(depricated in Oracle 10g)

亚洲黄色在线视频,国产精品久久久久久免费观看 ,91精品综合久久久久久五月天

tips悬停

JQuery插�gTipsWindown 1.1

应用演示

参数说明

Oracle中Hint深入理解

使用 EclEmma �q�行覆盖���试

介绍

安装 EclEmma 插�g

�?1 ��d�� EclEmma 更新站点

�?2 新增的覆盖测试按�?/h5>

使用 EclEmma ���试 Java �E�序

�?3 �?Java 应用�E�序�q�行覆盖���试

�?5 察看�E�序的覆盖测试率

�?6 用于�l�合多次覆盖���试�l�果的工��h��按钮

�?7 选择需要合�q�的覆盖���试�l�果

�?8 察看合�ƈ后的覆盖���试�l�果

��Z��Xfire SOAP Header的WebService安全验证教程 .

java实现���单的单点��d��(转蝲)

解决IE下Iframe的Session丢失

struts 2标签 样式问题

使用 EclEmma �q�行覆盖��试

使用 EclEmma ��试 Java �E�序

�?3 �?Java 应用�E�序�q�行覆盖��试

�?6 用于�l�合多次覆盖��试�l�果的工��h��按钮

�?7 选择需要合�q�的覆盖��试�l�果

�?8 察看合�ƈ后的覆盖��试�l�果

java实现��单的单点��d��(转蝲)

struts 2标签样式问题