axis-bin-1.4.zip资源-CSDN文库

共2000个文件

html：1796个

class：297个

java：128个

axis

webservice

5星 · 超过95%的资源需积分: 12 85 浏览量 2010-07-22 15:00:10 上传评论 4 收藏 10.69MB ZIP 举报

全称：Apache EXtensible Interaction System 阿帕奇可扩展交互系统　　Axis本质上就是一个SOAP引擎，提供创建服务器端、客户端和网关SOAP操作的基本框架。Axis目前版本是为Java编写的，不过为C++的版本正在开发中。但Axis并不完全是一个SOAP引擎，它还包括：　　是一个独立的SOAP服务器。　　是一个嵌入Servlet引擎（例如Tomcat）的服务器。　　支持WSDL。　　提供转化WSDL为Java类的工具。　　提供例子程序。　　提供TCP/IP数据包监视工具。　　apache wsAxis是第三代Apache SOAP，从2000年起，SOAP v2开发小组开始讨论如何让Axis更加灵活、可配置，以及能够处理SOAP和来自W3C的各种XML标准。通过不断地讨论和代码编写，Axis目前取得了如下成果：　　速度提高。 Axis通过基于事件的SAX对XML文档进行处理，从而在速度和效率上比Apache SOAP有所提高。　　灵活性提高。　　稳定性提高。　　提供面向组件的部署。　　提供一个简洁的传输抽象框架。其核心引擎完全于传输方式独立。从而使基于何种协议传输的选择更加灵活。　　支持WSDL。包括到处WSDL和客户代理生成等。　　在目前发行1.1版本中有什么东西？　　SOAP1.1/1.2引擎。　　灵活的配置和部署系统。　　支持及时自动生成SOAP服务（JWS）。　　支持所有的基本数据类型，为自定义串行操作提供类型映射系统。　　JavaBean的自动串行操作，包括将自定义属性类型映射到XML的属性和元素。　　RPC和基于消息的SOAP服务提供者。　　从部署好的服务自动生成WSDL。　　WSDL2Java工具可以从WSDL描述文件中产生相应的客户和服务器端SOAP操作框架。　　初步提供安全扩展，能够与Servlet2.2安全集成。　　通过HTTP Cookie和与传输无关的SOAP头信息提供会话跟踪。　　初步支持带附件的SOAP消息。　　在EJB方面提供把EJB作为Web服务的访问途经。　　基于Servlet的HTTP传输。　　基于JMS的传输。　　独立的服务器（但需要HTTP 服务器和Servlet容

资源推荐

资源详情

资源评论

收起资源包目录

axis-bin-1.4.zip （2000个子文件）

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

stylesheet.css 1KB

axis.css 761B

index-all.html 2.5MB

QName.html 493KB

constant-values.html 304KB

serialized-form.html 299KB

overview-tree.html 189KB

Constants.html 169KB

MessageElement.html 151KB

AxisFault.html 147KB

Call.html 141KB

Emitter.html 110KB

MessageContext.html 108KB

allclasses-frame.html 107KB

Handler.html 94KB

allclasses-noframe.html 93KB

SOAPPart.html 90KB

SOAPEnvelope.html 87KB

WSDDConstants.html 86KB

MessageContext.html 86KB

SOAPException.html 84KB

user-guide.html 82KB

DeserializationContext.html 81KB

Emitter.html 79KB

WSDDDeployment.html 78KB

SymbolTable.html 76KB

DeserializationContext.html 73KB

SOAPBody.html 72KB

SerializationContext.html 72KB

SOAPHeader.html 70KB

NodeImpl.html 68KB

reference.html 68KB

SerializationContext.html 65KB

ConfigurationException.html 65KB

TypeEntry.html 65KB

SOAPFault.html 63KB

JMSConstants.html 61KB

Types.html 61KB

WSDDService.html 60KB

Message.html 60KB

AxisEngine.html 59KB

SOAPHeaderElement.html 58KB

AxisFault.html 57KB

JavaGeneratorFactory.html 57KB

Service.html 57KB

package-use.html 56KB

XMLUtils.html 55KB

Utils.html 54KB

OperationDesc.html 54KB

SymbolTable.html 54KB

URI.html 54KB

DeserializerImpl.html 53KB

JavaServiceDesc.html 53KB

RB.html 52KB

HTTPConstants.html 51KB

developers-guide.html 51KB

RPCParam.html 50KB

SOAPHandler.html 49KB

integration-guide.html 49KB

SOAPElement.html 49KB

SOAPDocumentImpl.html 49KB

AttachmentPart.html 48KB

RPCElement.html 48KB

BindingEntry.html 48KB

TypeEntry.html 48KB

AttachmentsImpl.html 47KB

SOAPService.html 46KB

Generator.html 46KB

EngineConfiguration.html 45KB

WSDDDeployableItem.html 45KB

JavaBeanWriter.html 45KB

SOAPBodyElement.html 44KB

Call.html 44KB

SimpleProvider.html 44KB

BeanDeserializer.html 44KB

WSDDGlobalConfiguration.html 43KB

WSDDTypeMapping.html 43KB

Stub.html 43KB

Use.html 43KB

TypeMappingDelegate.html 43KB

WSDDTargetedChain.html 42KB

SOAPElement.html 42KB

EJBProvider.html 41KB

JavaUtils.html 41KB

共 2000 条

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

评论收藏

内容反馈

51future

2016-07-19

好东西，非常非常感谢。
zhaiwei_3000

2015-07-31

好东西，非常非常感谢。
Y2g_

2018-02-23

工作需要这个工具，谢谢了！
yyloveangela

2013-03-31

很好，安装包官方已经下载不了了，很珍贵。
路人haha

2013-06-06

这个jar包很好，axis1的

前往

页

zh272846193

粉丝: 3
资源: 22

axis-bin-1.4.zip

axis1.4完整包下载

axis1.3 axis1.4jar包

axis1.4完整JAR

axis-bin-1_4

axis-bin-1_4.zip

整合axis-bin1.4+activation.jar+mail.jar.zip

axis2-1.4.1-bin.zip 01

axis2包含axis2-1.4.1-war.zip和axis2-1.4.1-bin.zip

axis-bin-1_4.zip_Axis1.4-bin_axis 1.4_axis-1_4.rar_axis-bin-_axi

axis1.4所需全部jar包

axis1.4.1.zip

Axis1.4所需的Jar

axis1.4 源码包

axis1_4

axis2-1.4.1-bin.zip

axis-src-1_4.zip_axis 1 source_axis 1.4_axis src 1_axis-src_axis

axis1.4批量生成客户端代码

axis1.4 开发包

webservice axis1.4 开发资料

Apache Axis 1.2RC2 完整包

AXIS1全套JAR包

apache axis1.4 官网备份

axis-1.4.jar

axis1.4学习文档

axis1.4依赖包

web service axis1.4 jar

Springboot集成axis1.4的demo

axis2-1.7.zip

axis 1.4 .zip 运行包

最新资源