[JAVA]-Axis-Webservice-Demo资源-CSDN文库

共2470个文件

html：1796个

class：297个

java：138个

Java

Axis

Webservice

wsdl

3星 · 超过75%的资源需积分: 10 157 浏览量 2013-03-15 14:24:37 上传评论收藏 10.18MB RAR 举报

【JAVA】Axis Webservice Demo详解在Java开发中， Axis是一个强大的开源工具，它用于创建和部署Web服务。本文将详细介绍如何使用Axis进行Web服务的发布与调用，以及涉及的相关知识点。一、Axis简介 Axis是Apache软件基金会的一个项目，主要用于处理基于SOAP的Web服务。它提供了一种简单的方法来构建和部署Web服务，使得开发者可以快速地创建出符合WS-I（Web Services Interoperability）标准的服务。Axis支持多种语言，包括Java，且与JAX-RPC（Java API for XML-based Remote Procedure Calls）紧密集成。二、发布Web服务 1. 创建服务接口与实现：你需要定义一个Java接口，这个接口将作为Web服务的契约。接口中定义的方法将成为Web服务可供调用的操作。然后，实现该接口，编写具体的服务逻辑。 2. 使用Axis发布服务：有了接口和实现后，使用Axis的`wsdl2java`工具生成服务端代码。这个工具会根据你的接口生成相应的ServerStub和服务部署文件。然后，将服务部署到Axis服务器上，通常是在Tomcat或Jetty等Servlet容器中。 3. 部署服务：修改服务部署文件（一般为`.aar`格式），添加到Axis的webapps目录下的`WEB-INF/services`目录中，重启服务器，Web服务就会被发布并可以供外部调用。三、调用Web服务 1. 通过WSDL获取客户端代理类：对于远程调用Web服务，我们需要先使用`wsdl2java`工具从Web服务的WSDL（Web Service Description Language）文件生成客户端的代理类。这些代理类包含了调用Web服务所需的所有方法。 2. 使用客户端代码调用：生成的客户端代码包含了一个服务代理对象，通过这个对象，我们可以直接调用Web服务的方法。例如，在本示例中，可能有一个名为`CalculateService`的接口，我们可以通过实例化这个接口的代理类并调用其方法来执行计算操作。四、Axis1.4安装文件 `axis-1_4`文件夹可能包含了Axis1.4的完整版本，其中包括了Axis的库文件、文档、示例和工具等。要使用Axis，需要将其配置到你的开发环境中，通常是将lib目录下的jar文件添加到项目的类路径中，并确保服务器环境中也包含了这些依赖。五、`calculateservice-src` `calculateservice-src`可能是Web服务的源代码，包含了服务接口、实现以及可能的测试代码。你可以从中学习如何设计和实现一个简单的Web服务。通过阅读和理解这些代码，可以加深对Axis工作原理的理解。总结： Java Axis Web服务示例（`[JAVA]-Axis-Webservice-Demo`）提供了发布和调用Web服务的实际操作步骤。通过学习和实践这个示例，开发者可以更好地掌握使用Axis创建Web服务的技术，理解Web服务的基本原理，以及如何通过WSDL进行互操作。同时，熟悉 Axis 的安装和配置过程也是提升开发效率的关键。在实际工作中，这种技能对于构建可扩展、跨平台的分布式系统至关重要。

资源推荐

资源详情

资源评论

收起资源包目录

[JAVA]-Axis-Webservice-Demo （2470个子文件）

wsdl2java.bat 349B

generate-server-config.bat 152B

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

AddressBookServiceLocator.class 5KB

PerfService_ServiceLocator.class 5KB

AddressBookServiceLocator.class 5KB

PerfService_ServiceLocator.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

共 2470 条

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

评论收藏

内容反馈

zhblxm

2013-04-25

axis-1_4 文件怎么加载不进去啊，狂晕。
yhcelebrite

2014-04-13

参数传不过去 xfire就可以了
woshipark

2013-04-15

axis-1_4 文件怎么加载不进去啊，狂晕。
天翔ljsongcn

2014-08-26

有点问题不能用！
Alex-Lee

2013-03-28

可惜我的10分，估计是来骗分的。一点用处都没有。

前往

页

BossFriday

粉丝: 5329
资源: 13

[JAVA]-Axis-Webservice-Demo

基于Axis2的WebService的实例demo(包含jar包)

axis2客户端调用webService的DEMO

AXIS2作为客户端调用webService的demo

java axis2框架搭建和demo

Java Axis 直接调用webservice 接口工具类

java axis调用第三方webservice程序demo

webserviceClient-axis2.rar

axis2请求.Net webservice接口Demo

Axis1发布webservice服务

java调用webservice axis方式

axis2动态调用SAP C4C CRM webservice（JAVA版本）

webservice-demo:Axis2 Web服务演示

初学调用webservice的demo，适合初学者入门，资源包括axis2的库文件，以及org.apache.mina等库文件

通过axis使用网上天气预报服务的demo

webServiceDemo-java开发源代码

基于spring boot的小区物业管理系统源码+论文+答辩ppt

tomcat 8.5.100

RocketMQ 可视化工具 Dashboard下载

最新Java JDK 8安装版（Windows 64位）

自主研发的软著申请代码文档整理输出工具

Java 面经手册·小傅哥.pdf

BurpLoaderKeygen.jar.zip

java-11 windows-x64 安装包

Java面试八股文2023最新版

2024最强Java面试八股文

JDK1.8 windows 64位

JavaWeb仿小米在线商城ShoppingMall

ide-eval-resetter-2.3.5.jar,重新定义idea使用时间

最新资源