1.什么是registry?
From a business analyst’s perspective, it is similar to an Internet search engine
for business processes. From a developers perspective, they use the registry to
publish services and query the registry to discover services matching various
criteria.
2.什么是jbossESB?
In keeping with SOA principles, everything within JBossESB is considered to be
either a service or a message. Services encapsulate the business logic or points of
integration with legacy systems. Messages are the way in which clients and services
communicate with each other.
In the following sections we shall look at how Services and Messages are supported
within JBossESB.
3.什么是service?
A “Service” in JBossESB is defined as a list of “Action” classes that process
an ESB Message in a sequential manner (see below). This list of Action classes is
referred to as an “Action Pipeline”. A Service can define a list of “Listeners”
, which act as inbound routers for the Service, routing messages to the Action
Pipeline.
<?xml version = "1.0" encoding = "UTF-8"?>
<jbossesb
xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jb
ossesb-1.0.1.xsd" invmScope="GLOBAL">
<services>
<service category="Retail" name="ShoeStore" description="Acme Shoe Store
Service">
<actions>
<action name="println" class="org.jboss.soa.esb.actions.SystemPrintln"
/>
</actions>
</service>
</services>
</jbossesb>
As you can see from the above example, a Service has “category” and “name”
attributes. When JBossESB deploys the Service, it uses these attributes to register
the Service endpoints (listeners) in the Service Registry (see Registry Guide).
Clients can invoke the Service using the ServiceInvoker as follows.
ServiceInvoker invoker = new ServiceInvoker(Retail, ShoeStore);
Message message = MessageFactory.getInstance().getMessage();
message.getBody().add(Hi there!);
invoker.deliverAsync(message);
The ServiceInvoker uses the Service Registry (see ServicesGuide) to lookup the
available Endpoint addresses for the “Retail:ShoeStore” Service. It takes care of
all the transport details of getting the message from the Client to one of the
available Service Endpoints (JMS, FTP, HTTP etc), hiding all of the lower level
details from the Client.
解密UDDI
我们首先来看看UDDI代表什么?UDDI是Universal Description, Discovery and
Integration(统一描述、发现和集成)的缩写。UDDI的意图是作为一个注册簿,就象黄页是一
个地区企业的注册簿一样。象在黄页中那样,在UDDI注册簿中,企业将在不同的目录下注册它
们自己或其服务。通过浏览一个UDDI注册簿,开发人员能够查找一种服务或一个公司,并发现
如何调用该服务。
除了黄页外,UDDI还使用了白页和绿页。白页是企业实体列表,绿页是调用一项服务所必
需的文档。
UDDI的定义非常全面,足以适应不同种类的服务。一个UDDI服务定义可能代表一个传真服务或
电话服务。作为一种注册簿,UDDI一般使用数据库一类的软件来实现,在该数据库中,存在一
个允许发布或查询服务的有关信息。
UDDI数据模型
UDDI数据模型包括下面的主要元素:
·businessEntity:表示一个实际的企业。
·businessService:表示一个企业提供的服务。
·bindingTemplate:如何调用服务的说明。
http://www.yesky.com/351/1626851
From a business analyst’s perspective, it is similar to an Internet search engine
for business processes. From a developers perspective, they use the registry to
publish services and query the registry to discover services matching various
criteria.
2.什么是jbossESB?
In keeping with SOA principles, everything within JBossESB is considered to be
either a service or a message. Services encapsulate the business logic or points of
integration with legacy systems. Messages are the way in which clients and services
communicate with each other.
In the following sections we shall look at how Services and Messages are supported
within JBossESB.
3.什么是service?
A “Service” in JBossESB is defined as a list of “Action” classes that process
an ESB Message in a sequential manner (see below). This list of Action classes is
referred to as an “Action Pipeline”. A Service can define a list of “Listeners”
, which act as inbound routers for the Service, routing messages to the Action
Pipeline.
<?xml version = "1.0" encoding = "UTF-8"?>
<jbossesb
xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml/jb
ossesb-1.0.1.xsd" invmScope="GLOBAL">
<services>
<service category="Retail" name="ShoeStore" description="Acme Shoe Store
Service">
<actions>
<action name="println" class="org.jboss.soa.esb.actions.SystemPrintln"
/>
</actions>
</service>
</services>
</jbossesb>
As you can see from the above example, a Service has “category” and “name”
attributes. When JBossESB deploys the Service, it uses these attributes to register
the Service endpoints (listeners) in the Service Registry (see Registry Guide).
Clients can invoke the Service using the ServiceInvoker as follows.
ServiceInvoker invoker = new ServiceInvoker(Retail, ShoeStore);
Message message = MessageFactory.getInstance().getMessage();
message.getBody().add(Hi there!);
invoker.deliverAsync(message);
The ServiceInvoker uses the Service Registry (see ServicesGuide) to lookup the
available Endpoint addresses for the “Retail:ShoeStore” Service. It takes care of
all the transport details of getting the message from the Client to one of the
available Service Endpoints (JMS, FTP, HTTP etc), hiding all of the lower level
details from the Client.
解密UDDI
我们首先来看看UDDI代表什么?UDDI是Universal Description, Discovery and
Integration(统一描述、发现和集成)的缩写。UDDI的意图是作为一个注册簿,就象黄页是一
个地区企业的注册簿一样。象在黄页中那样,在UDDI注册簿中,企业将在不同的目录下注册它
们自己或其服务。通过浏览一个UDDI注册簿,开发人员能够查找一种服务或一个公司,并发现
如何调用该服务。
除了黄页外,UDDI还使用了白页和绿页。白页是企业实体列表,绿页是调用一项服务所必
需的文档。
UDDI的定义非常全面,足以适应不同种类的服务。一个UDDI服务定义可能代表一个传真服务或
电话服务。作为一种注册簿,UDDI一般使用数据库一类的软件来实现,在该数据库中,存在一
个允许发布或查询服务的有关信息。
UDDI数据模型
UDDI数据模型包括下面的主要元素:
·businessEntity:表示一个实际的企业。
·businessService:表示一个企业提供的服务。
·bindingTemplate:如何调用服务的说明。
http://www.yesky.com/351/1626851