axis-src-1_4.tar.gz资源-CSDN文库

axis-src-1_4.tar.gz

5星 · 超过95%的资源需积分: 10 41 浏览量 2010-08-06 23:04:16 上传评论收藏 16.25MB GZ 举报

共4137个文件

html：1797个

java：1393个

class：297个

标题中的"axis-src-1_4.tar.gz"指的是Axis源代码的版本1.4的归档文件，它采用tar和gzip格式进行压缩。Axis是一个开放源码的Web服务开发工具包，主要用于创建和部署Web服务。这个压缩包是学习和理解Axis工作原理以及如何在项目中使用它的理想资源。描述中提到的“学习axis的好帮手，好工具”，暗示了这个压缩包包含的内容可能包括完整的源代码、构建脚本、示例项目、文档和可能的测试用例，这些都是深入学习和实践Axis功能的重要组成部分。标签"axis-src-1_4.tar.gz"再次强调了这个文件是关于Axis的源代码，版本号为1.4。通常，不同版本的软件会包含修复的错误、新增的功能或性能优化，因此学习旧版本的源代码有助于理解软件的发展历程。在“压缩包子文件的文件名称列表”中提到了"axis-1_4"，这可能是解压后得到的主目录名，里面包含了所有与Axis 1.4相关的源代码和其他资源。通常，这个目录下会有以下几个部分： 1. **src**：源代码目录，包含了Java源文件，分为不同的包（package），如com.sun.xmlrpc等，这些包组织了实现Axis功能的各种类。 2. **docs**：文档目录，可能包括用户手册、API参考、开发者指南等，帮助用户理解和使用Axis。 3. **build**：构建脚本和配置文件，比如Ant的build.xml，用于编译、打包和测试源代码。 4. **samples**：示例项目，提供了一些简单的Web服务应用，方便初学者快速上手。 5. **lib**：库文件夹，包含 Axis 运行时和编译时所需的JAR文件，可能包括Apache Commons库和其他依赖项。 6. **bin**：二进制脚本，例如启动和停止Web服务的脚本。 7. **conf**：配置文件，如server-config.wsdd，定义了服务器的配置信息和Web服务部署描述符。通过研究这个压缩包，你可以了解Axis如何处理SOAP消息，如何实现WSDL到Java或者Java到WSDL的绑定，以及如何部署和调试Web服务。此外，它还能帮助你掌握XML-RPC和HTTP协议在Web服务中的应用，以及如何利用Apache Ant工具进行自动化构建。 "axis-src-1_4.tar.gz"是一个学习Web服务开发，特别是Apache Axis框架的宝贵资源，包含了从源码学习、项目构建到实际应用的全套材料。通过深入研究这个压缩包，你不仅可以提升对Axis的理解，也能增进对Java编程、Web服务标准和XML处理的掌握。

资源推荐

资源详情

资源评论

收起资源包目录

axis-src-1_4.tar.gz （4137个子文件）

build._xml 3KB

axis-bibliography.bib 5KB

InteropTestSoapBindingStub.class 34KB

rfq.class 18KB

TestClient.class 15KB

EchoAttachment.class 13KB

SOAPMonitorApplet$SOAPMonitorPage.class 12KB

AddressBookSOAPBindingStub.class 10KB

TestRef.class 10KB

SwaBindingStub.class 9KB

PerfPortSoapBindingStub.class 9KB

AddressSoapBindingStub.class 9KB

v3.class 8KB

EchoAttachmentsService.class 7KB

InteropTestSoapBindingImpl.class 7KB

WidgetPriceSoapBindingStub.class 6KB

HelloBindingStub.class 6KB

SOAPMonitorApplet$SOAPMonitorTableModel.class 5KB

Address.class 5KB

SOAPMonitorApplet$SOAPMonitorFilter.class 5KB

SOAPMonitorApplet$ServiceFilterPanel.class 5KB

TestMsg.class 5KB

TestSer.class 5KB

GetQuote.class 5KB

SOAPArrayStruct.class 5KB

TCPListener$SocketHandler.class 5KB

WidgetPriceServiceLocator.class 5KB

AddressServiceServiceLocator.class 5KB

PerfService_ServiceLocator.class 5KB

AddressBookServiceLocator.class 5KB

PerfService_ServiceLocator.class 5KB

AddressBookServiceLocator.class 5KB

InteropTestServiceLocator.class 5KB

HelloWorldLocator.class 5KB

SOAPStructStruct.class 5KB

SwaServiceLocator.class 5KB

TestClient.class 5KB

GetQuote1.class 4KB

TCPListener.class 4KB

SOAPStruct.class 4KB

Main.class 4KB

Phone.class 4KB

EmployeeClient.class 4KB

RegistryService.class 4KB

DOMUtils.class 4KB

echoHeaderStructHandler.class 4KB

TCPSender.class 4KB

echoHeaderStringHandler.class 4KB

GetQuote.class 4KB

AddressBookSOAPBindingSkeleton.class 4KB

PerfService_ServiceTestCase.class 3KB

WidgetPriceSoapBindingSkeleton.class 3KB

Client.class 3KB

SwaBindingImpl.class 3KB

StateType.class 3KB

共 4137 条

Overview of the JMS Transport Layer

<author: Dave Chappell chappell@sonicsoftware.com>

The JMS transport layer allows SOAP messages to be carried over reliable messaging

between Axis clients and Axis services. As illustrated in figure 1, this transport layer can

be seamlessly plugged into the Axis engine as an alternative to HTTP. This allows an

axis developer to use normal Axis API’s to perform synchronous request/reply,

document-style message-based request/response, and one-way invocations across a

reliable delivery mechanism based on JMS messaging semantics.

Client

Sender

Axis

Engine

JMS

Sender

JMS

Listener

Axis

Engine

Service

JMS

Messaging

Figure 1: SOAP over JMS as an alternate transport to HTTP.

In addition to providing the base plug-in code for the transport, the JMS transport layer

also provides a subsystem that allows many conveniences when connecting to a JMS

provider, including:

• JMS provider-independent JNDI abstraction support for JMS Administered

objects i.e. ConnectionFactories and JMS destinations.

• A mechanism of bypassing JNDI and using direct instantiation of

ConnectionFactory and Topic and Queue destinations, for those JMS providers

that support such a capability.

• Generic Endpoint abstraction layer for managing Topic and Queue destinations.

• Thread pooling and Session management, providingthread-safe concurrent

sending and receiving.

• Automatic reconnect and send-retry based on configurable timeout and retry

intervals.

• Request/response management using temporary destinations, and JMSReplyTo

semantics.

• An encapsulation of JMS provider-specific information when necessary, such as

configuration information, direct instantiation of ConnectionFactories, and JMS

provider-specific exception handling details.

• A mechanism for setting JMS specific options as properties in the Call object, and

passing them through to the JMS provider during the invocation.

• Pub/Sub and point to point queueing support with durability and persistent send

options

As a beginning user of this subsystem, it is not necessary to be intimately aware of the

details of all of these capabilities. They are all hidden below the standard Axis Call and

Service interfaces, yet there when you need them. Just a few simple setup steps are all

you need to get started using the JMS transport layer. Details are provided below.

Setting up the JNDI store for JMS Administered objects

The JMS specification prescribes the use of JNDI for the discovery and instantiation of

ConnectionFactory objects, and Topic and Queue destinations. The configuration of the

JNDI access and the setup of Topic and Queue destinations is done in a JMS provider-

specific fashion. You MUST perform this step in order to proceed to running the

example.

In our example, the JNDI access makes use of the file-based FSContext version 1.2 beta

3 release, available from http://java.sun.com/products/jndi/index.html. The minimum

required objects to set up are listed in the jndi-connection-factory.properties located in

the samples/jms directory. The required fields to set up are:

java.naming.factory.initial=com.sun.jndi.fscontext.RefFSContextFactory

java.naming.provider.url=file:///c:/JNDIStore

The JNDI name used to access the ConnectionFactory is “MyCF”, and the lookup name

for the sample queue is “MyQ”.

For JMS provider-dependant instructions on how to set this up, see the “JMS Provider

Setup Instructions” section of this document.

Running the JMS sample

The JMS sample found in samples/jms, is an invocation of an external stock quote

service. For the purpose of keeping the example simple, it is a two-part invocation that

first sends the request across the JMS transport to a local JMS listener, which in turn

invokes another call to an external service across HTTP (see figure 2).

JMSTest

Client

Sender

Axis

Engine

JMS

Sender

JMS

Listener

Axis

Engine

Service

JMS

Messaging

Stock

Quote

Client

Axis

Engine

HTTP

Sender

HTTP

Listener

Axis

Engine

Stock

Quote

Service

HTTP

JMSSender

SimpleJMSListener

Figure 2: The JMSTest example.

Running the sample with a -? As a command line option will print a usage message

showing the different options available. To run the test with the supplied defaults:

From the samples directory, execute the following from the command line:

java samples.jms.JMSTest -c jndi-connection-factory.properties -d "MyQ" IBM PRGS

This will send the SOAP request across the JMS transport layer, to the local instance of

SimpleJMSListener. SimpleJMSListener is a JMS Listener that receives the SOAP

message, which in turn will invoke the Axis engine to call the StockQuote service. This

service will then in turn invoke samples.stock.StockQuoteService. The

StockQuoteService will make a HTTP request across the Internet to invoke a web service

that is hosted at an external web site.

If you do not have a live Internet connection, then specifying “XXX” as a ticker symbol.

This will skip the external invocation and return a hard-coded value. This is sufficient to

test the JMS transport aspect of the sample

By default, the conversation between JMSSender and SimpleJMSListener can be

executed on a local machine for testing purposes, as long as there is a JMS provider

installed somewhere that the sender and listener can connect to. However, there is

nothing to prevent them from being separated across machines or geographic locations.

Invoking the JMS Transport Across the Internet

评论收藏

内容反馈

eryun_hou

2011-11-08

安装通过，谢谢楼主分享

panyuwu

粉丝: 11
资源: 27

axis-src-1_4.tar.gz

axis2c-bin-1.6.0 axis2c-src-1.6.0

xerces-c-src1_6_0.tar.gz_ xerces_XML解析_apache_xerces_xml parser

axis2c-src-1.6.0

apache-cxf-3.2.4-src.tar.gz

webService-Axis-tomcat发布教程.docx编程资料

axis2/c linux 安装步骤

使用myEclipse,tomcat和Axis发布webService.pdf

webservice 学习资料

使用myEclipse，tomcat 和Axis发布webService

jpgraph-3.0.7.tar.gz

axis2c工具

axis2c linux下c客户端编程详解

Python库 | Kaggler-0.6.4.tar.gz

【linux-2.6.31】内核编译指南

java开源包10

java开源包1

java开源包4

java开源包101

java开源包11

java开源包2

java开源包3

java开源包6

java开源包5

java开源包8

java开源包7

java开源包9

Java资源包01

JAVA上百实例源码以及开源项目源代码

最新资源