自己找到答案了:
[直接将规范提供的wsdl连接到?wsdl]已经调查清楚了,参见“Axis Reference
Guide”,在Axis doc中有具体如下:
Individual Service Configuration
Here is a service element with examples of the current set of options you
can set. More may exists (consult the source, as usual).
<service name="MyServiceName"
provider="java:RPC"
style="rpc|document|wrapped"
use="encoded|literal"
streaming="off|on"
attachment="MIME|DIME|NONE"> <parameter name="className" value="org.apache.mystuff.MyService"/>
<parameter name="allowedMethods" value="method1 method2 method3"/>
<parameter name="wsdlTargetNamespace"
value="http://mystuff.apache.org/MyService"/>
<parameter name="wsdlServiceElement" value="MyService"/>
<parameter name="wsdlServicePort" value="MyServicePort"/>
<parameter name="wsdlPortType" value="MyPort"/>
<parameter name="wsdlSoapActionMode" value="NONE|DEFAULT|OPERATION"/> <parameter name="SingleSOAPVersion" value="1.1|1.2/> <documentation>Service level info</documentation>
<endpointURL>http://example.com:5050/my/custom/url/to/service</endpointURL>
<wsdlFile>/path/to/wsdl/file</wsdlFile>
<namespace>http://my.namespace.com/myservice</namespace>
<handlerInfoChain>handlerChainName</handlerInfoChain> <operation ... /> <typeMapping ... /> <beanMapping ... /></service>Service Element Attributes
name
The name of the service.
provider
The provider for the service. The recognized providers are: java:RPC,
java:MSG, java:EJB, java:COM, java:BSF, java:CORBA, java:RMI and "Handler"
where xmlns:java="http://xml.apache.org/axis/wsdd/providers/java". The RPC
provider supports both rpc/encoded, document/literal and wrapped/literal
services. the MSG provider supports the 'fixed signature' service which
takes XML in and returns XML our directly. The other providers must be built
in to Axis. See the code in org.apache.axis.providers.
style
The style of the service. "rpc" uses the RPC style of wrapping the parts of
the message an element that has the same name as the operation. "document"
style means the messages in and out of the service are exactly as they are
describe by the XML Schema in the WSDL. "wrapped" is a subset of the
document style. The arguments to the operation are wrapped up in and element
that has the same name as the operation. This is the style of service .NET
generates by default. The generated WSDL specifies document style (and
literal use) but Axis will 'unwrapped' the parts of the message for the Axis
service at the back end.
use
This can be either "encoded" or "literal". Encoded means the SOAP 1.1
"Section 5 Encoding" is used to encode the data structures returned by the
service and incoming XML is decoded using the same rules. Literal use means
no such encoding is performed.
streaming
Valid values are "on" or "off". This turns on or off the streaming mode of
the XML deserializer. The default is currently off. Certain Axis
functionality may not function properly if this is turned on. Use with
caution.
attachment
Valied values are "MIME" for SOAP with attachements (SwA), "DIME" for DIME
support and "NONE" for no attachement support at all. The default mode of
Axis is to use MIME attachements (SwA).
Elements allowed in the Service element
<wsdlFile>
The path to a WSDL File; can be an absolute path or a resource that axis.jar
can load. Useful to export your custom WSDL file. When specify a path to a
resource, place a forward slash to start at the beginning of the classpath
(e.g "/org/someone/res/mywsdl.wsdl"). How does Axis know whether to return a
file or resource? It looks for a file first, if that is missing a resource
is returned.<documentation>
Documentation text that will get inserted in to the document element of the
WSDL for the service<endpointURL>
Specify the endpoint URL of the service, which will override the transport
level URL created by the Axis servlet. This is usefull if you have a proxy
handling requests and you need the endpoint URL to reflect a different
hostname than the one Axis is executing on.<namespace>
Specify the default namespace for the service.<handlerInfoChain>
Specify the JAX RPC handler chain for this service.In addition, as described above, the <requestFlow> and/or <responseFlow>
elements are also allowed in the service element.
Service Level Parameters
The following parameters can be set on a service wide basis using the
<parameter> tag. There may be more than those documented here, but this list
should be almost complete.
className The fully qualified name of the implemenation class of the
service. allowedMethods A space or comma seperated list of method names, or "*"
for all methods in the service class. If this parameter isn't specified, all
methods ("*") is the default.
wsdlPortType The name of the portType element in the generated WSDL
for the service.
wsdlServiceElement The name of the Service element in the generated
WSDL for the service.
wsdlServicePort The name of the port in the generated WSDL for the
service.
wsdlTargetNamespace The target namespace in the generated WSDL for the
service.
wsdlInputSchema A comma separated list of of input Schema for the
generated WSDL for the service.
wsdlSoapActionMode Values are DEFAULT, OPERATION or NONE. OPERATION
forces soapAction to the name of the operation. DEFAULT causes the
soapAction to be set according to the operations meta data, specifically the
soapAction attribute of the operation in the deployment information. NONE
forces the soapAction to "". The default is DEFAULT.
SingleSOAPVersion When set to either "1.1" or "1.2", this configures a
service to only accept the specified SOAP version. Attempts to connect to
the service using another version will result in a fault.
[直接将规范提供的wsdl连接到?wsdl]已经调查清楚了,参见“Axis Reference
Guide”,在Axis doc中有具体如下:
Individual Service Configuration
Here is a service element with examples of the current set of options you
can set. More may exists (consult the source, as usual).
<service name="MyServiceName"
provider="java:RPC"
style="rpc|document|wrapped"
use="encoded|literal"
streaming="off|on"
attachment="MIME|DIME|NONE"> <parameter name="className" value="org.apache.mystuff.MyService"/>
<parameter name="allowedMethods" value="method1 method2 method3"/>
<parameter name="wsdlTargetNamespace"
value="http://mystuff.apache.org/MyService"/>
<parameter name="wsdlServiceElement" value="MyService"/>
<parameter name="wsdlServicePort" value="MyServicePort"/>
<parameter name="wsdlPortType" value="MyPort"/>
<parameter name="wsdlSoapActionMode" value="NONE|DEFAULT|OPERATION"/> <parameter name="SingleSOAPVersion" value="1.1|1.2/> <documentation>Service level info</documentation>
<endpointURL>http://example.com:5050/my/custom/url/to/service</endpointURL>
<wsdlFile>/path/to/wsdl/file</wsdlFile>
<namespace>http://my.namespace.com/myservice</namespace>
<handlerInfoChain>handlerChainName</handlerInfoChain> <operation ... /> <typeMapping ... /> <beanMapping ... /></service>Service Element Attributes
name
The name of the service.
provider
The provider for the service. The recognized providers are: java:RPC,
java:MSG, java:EJB, java:COM, java:BSF, java:CORBA, java:RMI and "Handler"
where xmlns:java="http://xml.apache.org/axis/wsdd/providers/java". The RPC
provider supports both rpc/encoded, document/literal and wrapped/literal
services. the MSG provider supports the 'fixed signature' service which
takes XML in and returns XML our directly. The other providers must be built
in to Axis. See the code in org.apache.axis.providers.
style
The style of the service. "rpc" uses the RPC style of wrapping the parts of
the message an element that has the same name as the operation. "document"
style means the messages in and out of the service are exactly as they are
describe by the XML Schema in the WSDL. "wrapped" is a subset of the
document style. The arguments to the operation are wrapped up in and element
that has the same name as the operation. This is the style of service .NET
generates by default. The generated WSDL specifies document style (and
literal use) but Axis will 'unwrapped' the parts of the message for the Axis
service at the back end.
use
This can be either "encoded" or "literal". Encoded means the SOAP 1.1
"Section 5 Encoding" is used to encode the data structures returned by the
service and incoming XML is decoded using the same rules. Literal use means
no such encoding is performed.
streaming
Valid values are "on" or "off". This turns on or off the streaming mode of
the XML deserializer. The default is currently off. Certain Axis
functionality may not function properly if this is turned on. Use with
caution.
attachment
Valied values are "MIME" for SOAP with attachements (SwA), "DIME" for DIME
support and "NONE" for no attachement support at all. The default mode of
Axis is to use MIME attachements (SwA).
Elements allowed in the Service element
<wsdlFile>
The path to a WSDL File; can be an absolute path or a resource that axis.jar
can load. Useful to export your custom WSDL file. When specify a path to a
resource, place a forward slash to start at the beginning of the classpath
(e.g "/org/someone/res/mywsdl.wsdl"). How does Axis know whether to return a
file or resource? It looks for a file first, if that is missing a resource
is returned.<documentation>
Documentation text that will get inserted in to the document element of the
WSDL for the service<endpointURL>
Specify the endpoint URL of the service, which will override the transport
level URL created by the Axis servlet. This is usefull if you have a proxy
handling requests and you need the endpoint URL to reflect a different
hostname than the one Axis is executing on.<namespace>
Specify the default namespace for the service.<handlerInfoChain>
Specify the JAX RPC handler chain for this service.In addition, as described above, the <requestFlow> and/or <responseFlow>
elements are also allowed in the service element.
Service Level Parameters
The following parameters can be set on a service wide basis using the
<parameter> tag. There may be more than those documented here, but this list
should be almost complete.
className The fully qualified name of the implemenation class of the
service. allowedMethods A space or comma seperated list of method names, or "*"
for all methods in the service class. If this parameter isn't specified, all
methods ("*") is the default.
wsdlPortType The name of the portType element in the generated WSDL
for the service.
wsdlServiceElement The name of the Service element in the generated
WSDL for the service.
wsdlServicePort The name of the port in the generated WSDL for the
service.
wsdlTargetNamespace The target namespace in the generated WSDL for the
service.
wsdlInputSchema A comma separated list of of input Schema for the
generated WSDL for the service.
wsdlSoapActionMode Values are DEFAULT, OPERATION or NONE. OPERATION
forces soapAction to the name of the operation. DEFAULT causes the
soapAction to be set according to the operations meta data, specifically the
soapAction attribute of the operation in the deployment information. NONE
forces the soapAction to "". The default is DEFAULT.
SingleSOAPVersion When set to either "1.1" or "1.2", this configures a
service to only accept the specified SOAP version. Attempts to connect to
the service using another version will result in a fault.
解决方案 »
免费领取超大流量手机卡,每月29元包185G流量+100分钟通话, 中国电信官方发货