axis1.4源码包_axis源码资源-CSDN文库

5星 · 超过95%的资源需积分: 10 31 浏览量 2012-05-02 17:38:13 上传评论收藏 16.25MB GZ 举报

共4137个文件

html：1797个

java：1393个

class：297个

Axis1.4是Apache软件基金会开发的一个开源Web服务框架，主要用于构建和部署SOAP（Simple Object Access Protocol）服务。这个源码包提供了 Axis1.4 的完整源代码，使得开发者能够深入理解其工作原理，同时也方便进行二次开发和定制。下面我们将详细探讨 Axis1.4 的核心概念、功能和相关知识点。 1. **SOAP与Web服务**： SOAP 是一种基于XML的协议，用于在分布式环境中交换结构化和类型化的信息。Axis1.4 将Java对象转化为SOAP消息，并将SOAP消息转换回Java对象，从而实现Web服务的调用。通过SOAP，不同平台和语言的应用程序可以相互通信。 2. **WSDL（Web Services Description Language）**： WSDL 文件描述了Web服务的接口，包括服务的位置、提供的操作以及这些操作的消息格式。Axis1.4 使用WSDL来生成客户端和服务端的代理类，简化了Web服务的开发和调用。 3. **JAX-RPC（Java API for XML-Based RPC）**： Axis1.4 基于JAX-RPC规范，它提供了一套API，使得开发者可以用Java编写Web服务和客户端。JAX-RPC将XML-RPC转换为Java方法调用，反之亦然。 4. **部署描述符**：在Axis1.4中，服务可以通过部署描述符文件（如services.xml）来配置。这些文件定义了服务的元数据，包括服务的类、操作和绑定信息。 5. **模块和处理链**： Axis1.4支持模块化架构，允许开发者创建自定义模块来扩展其功能。处理链（Handler Chains）允许用户定义处理消息的顺序和逻辑，增强了服务的灵活性。 6. **消息传递模型**： Axis1.4遵循WS-I Basic Profile的传输层模型，支持HTTP、HTTPS等多种传输协议。它还支持MTOM（Message Transmission Optimization Mechanism）和SWA（SOAP with Attachments），以优化传输包含二进制数据的SOAP消息。 7. **安全性**： Axis1.4 提供了基本的安全特性，如SOAP消息加密和签名，以及WS-Security规范的支持。开发者可以通过配置安全策略来保护Web服务免受攻击。 8. **国际化和本地化**： Axis1.4 支持多语言环境，可以处理不同地区的日期、货币和其他格式。 9. **调试和日志**：开发者可以通过Axis1.4的调试模式和详细的日志记录来追踪问题，提高开发效率。 10. **客户端API**： Axis1.4 提供了客户端API，使得开发者可以轻松地调用远程Web服务。通过使用Stub和Skeleton类，开发者可以像调用本地方法一样调用Web服务。通过分析和研究Axis1.4的源码，开发者可以深入了解其内部工作机制，包括SOAP消息的构建和解析、WSDL的处理、服务的部署和调用流程等。这对于提升Web服务开发技能、解决实际问题以及贡献开源社区都是非常有益的。同时，了解源码也有助于学习和理解其他Web服务框架的工作原理，例如JAX-WS（Java API for XML Web Services）和Spring Web Services等。

资源推荐

资源详情

资源评论

收起资源包目录

axis1.4 源码包（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

评论收藏

内容反馈

zero1814

2013-04-08

非常给力啊，使用了，修该了一下，把我遇到的难题解决了。
yesingle

2013-03-12

非常给力啊，使用了，修该了一下
x45224446

2012-07-31

这个包好用，支持下载。
wayang84

2013-04-19

这个包，找到的链接都不好用，就这个可以。csdn这好呀
pp8231017

2014-07-14

对我做webservice接口提供便利了。哈哈

前往

页

toolkit1216

粉丝: 2
资源: 3

axis1.4 源码包

axis 1.3 完整源码

axis1.4源码

axis.jar源码

axis1.4-1.6总包_源码jar包帮助文档

axis1.4开发webservice详细实例

联通vac割接 用axis1.4生成客户端源码

axis1.4部署webSevice项目测试(已有所相关的jar包)+开发指南+源码+部署相关配置wsdd文件，内有说明

xml执行java源码-Axis-1.4-RCE-Poc:Axis&lt;=1.4远程命令执行（RCE）POC

axis1.4 心得

基于axis的webservice项目示例源码

axis发布webservice教程源代码

axis1.4完整包下载

AXIS工具包源文件及使用配置说明

axis1.4

wsdl2java源码-axis14_on_wildfly_swarm:该项目是我使用WildflySwarm捆绑ApacheAxis1.4S

Web Service通用客户端和测试工具wsCaller1.1

wsdl2java源码-Axis1WebService:Axis1WebService例子，通过wsdl文件生成服务器端代码并部署

birt4.3.0编译时所需要的部分依赖包

axis-1.4_1.jar.zip

axis2-1.7.4-src.zip 源码

AxisLib1.4.rar(包括wsdl4j)

axis1.4.rar

axis整合web.rar

java开源包8

java开源包4

java开源包1

java开源包2

最新资源

联通vac割接用axis1.4生成客户端源码

xml执行java源码-Axis-1.4-RCE-Poc:Axis<=1.4远程命令执行（RCE）POC