王一生 的个人资料王一生日志列表留言簿 工具 帮助
2006/4/25

XFire

Codehaus XFire is a next-generation java SOAP framework. Codehaus XFire makes service oriented development approachable through its easy to use API and support for standards. It is also highly performant since it is built on a low memory StAX based model.

Above introduction comes from http://xfire.codehaus.org/,and at the same time I searched the keyword XFire with the Google search engine,I found few Chinese information about XFire(related to SOAP ).

From my first experience of the XFire,I think it's good and convenient for Web Service construction and development though I'm not familiar with Apache's Axis,and there are comparison data showing the completeness support and powerful functionalities of XFire.

It seems some people in China are devoting themselves to the applying of XFire,the http://www.kuaff.com address is good for XFire learners,it provides some materials on XFire.Certainly,the best way is to learn from http://xfire.codehaus.org/.

If time allowed ,I'll provide some information or experience on the using of XFire later.


2006/4/20

Integrated Process Improvement Principles

1. Maintain executive support.Strong consistent support is crucial.

2. Pick your targets carefully.Don't underestimate the effort needed,because process improvement is hard work.

3. Leverage best practices.Use what is available and "steal with pride."

4. Align process improvement with your business objectives.Leverage existing objectives or create new ones to support process improvement.
2006/4/11

something about Web Service|一些关于Web服务的信息/新闻

    On the day of 4 April 2006,  W3C(http://www.w3c.org/) announces the opening of the W3C China Office (http://www.chinaw3c.org/). The chinaw3c's announcement says it marks that China has more voice on the international standards in the web industry though the W3C Office in Hong Kong(http://www.w3c.org.hk/index.html) was inaugurated on 13 November 1998.The opening ceremonies will be held on 27-28 April 2006.

    After entering the 2006 ,some specifications have come to the publication,such as:

1. 2006-03-27: The Web Services Description Working Group published updated drafts of the Web Services Description Language (WSDL) Version 2.0 specifications: Part 0: Primer(http://www.w3.org/TR/2006/CR-wsdl20-primer-20060327/), Part 1: Core Language and Part 2: Adjuncts have been republished with minor modifications as W3C Candidate Recommendations.


2. Members Approve WS-Security v1.1 as OASIS Standard(http://www.oasis-open.org/news/oasis-news-06-02-15.php),and the specification can be downloaded from the http://www.oasis-open.org/committees/download.php/16790/wss-v1.1-spec-os-SOAPMessageSecurity.pdf address.

 


 

2006/4/5

XML命名空间

    XML命名空间声明中所用的URI必须和XML模式声明中的目标命名空间相匹配.

例如,XML模式声明的目标命名空间
<?xml version='1.0' encoding='UTF-8' ?>
<schema xmlns="
http://www.w3.org/2001/XMLSchema" targetNamespace="http://www.malcolm.com/Address" >
 <complexType name="AddressType" >
  <sequence>
   <element name="street" type="string" />
    ...
  </sequence>
 </complexType>
</schema>

例如,XML命名空间
<?xml version='1.0' encoding='UTF-8' ?>
 <res:reservation xmlns:res="
http://www.malcolm.com/Reservation" >
  ...
   <addr:address xmlns:addr="
http://www.malcolm.com/Address" >
    <addr:street>...</addr:street>
    ...
   </addr:address>
  ...
</res:reservation>
    默认命名空间是一个没有前缀的XML命名空间声明(xmlns="URI" ),其作用域仅应用于声明此默认命名空间的元素,以及在该元素之下嵌套的无前缀元素.默认命名空间不作用于属性.默认命名空间不应用于属性,唯一例外的是XML语言本身所定义的属性,例如xmlns属性.
    如果希望指出与一个XML命名空间相关联的XML模式的位置,从而使解析器可以将其上载,并用于验证中,可以通过schemaLocation属性完成.元素以命名空间-位置值对出现.第一个值是XML命名空间的URI;第二个值是XML模式的物理位置.例如如下:

<?xml version='1.0' encoding='UTF-8' ?>
 <reservation xmlns="
http://www.malcolm.com/Reservation"
    xmlns:xsi="
http://www.w3c.org/2001/XMLSchema-Instance"
    xsi:schemaLocation="
http://www.malcolm.com/Reservation
                        http://www.malcolm.com/schemas/reservation.xsd"  >

    XML模式也使用XML命名空间,例如如下:

<?xml version='1.0' encoding='UTF-8' ?>
 <schema
   xmlns="
http://www.malcolm.com/Reservation"
   targetNamespace="
http://www.malcolm.com/Address"
   xmlns:addr="
http://www.malcolm.com/Address" >
...

   第一个命名空间指出默认命名空间,第二个指出XML模式的目标命名空间是Address标记的命名空间,第三个对目标命名空间指定了前缀.

 

 

2006/4/3

Use Case: generalization

In the book of "The Unified Modeling Language User Guide" (8th
Printing April 2001 ,ADDISON-WESLEY),there's one paragraph(Page 226)
like this: "Generalization among use cases is just like
generalizations among classes.Here it means that the child use case
inherits the behavior and meaning of the parent use case;the child
may add to or override the behavior of its parent;and the child
may be substituted any place the parent appears(both the parent and
the child may have concrete instances)."

I'm confused about the meaning of '... the child may be substituted
any place the parent appears ...'.It seems that the child use case
can be replaced by something else.But from the context of the
paragraph,it seems that the child use case can replace the parent
use case any place where the parent use case appears.So,here's
the problem ,who replaces who ?Child use case replaces parent
,or parent replaces child ?

I have to refer to the dictionary (Oxford Advanced Learner's
Dictionary of Current English,seventh Edition,2005,OXFORD
UNIVERSITY PRESS).On page 1476,the dictionary provides some
information on the word substitute for me .

The word substitute can be used as phrases as below:
substitute A (for B) | substitute B (with/by A) | substitute for sb/sth
It means that we use A as a replacement of B.But I can not find any
similar phrase structure in the above paragraph. Luckily,the
dictionary gives us the HELP hint:

"HELP:when for,with or by are not used,as in the last
example,it can be difficult to tell whether the person or thing
mentioned is being used,or has been replaced by something or
something else.The context will usually make this clear."

The last example is this sentence:
Beckham was substituted in
the second half after a knee injury(= somebody else played
instead of Beckham in the second half).

So,here comes the clear view of the meaning of the '... the
child may be substituted any place the parent appears ...'.Because
of no prepositions as for ,with or by used,we can only make a
judgement from the detailed context of the paragraph.In the
paragraph,we see that the child use case inherits the behavior
and meaning of the parent use case and can add to or override
the behavior of its parent,so the child use case can be a
replacement of parent use case.

To dismiss the misapprehension ,I think the best way is to modify
the sentence like this ,'... the child may replace the parent any
place the parent appears ...'.