用JSR注解做的webservice，如下：
@WebService(targetNamespace = "http://xx.com")
public interface ICRMUserAuth {
@WebResult(name="CRMUserAuthResult", targetNamespace = "http://xx.com")
@WebMethod(action="http://xx.com", operationName="CRMUserAuth")
public CRMUserAuthResponse CRMUserAuth(
@WebParam(name = "SystemsID")
String SystemsID,
@WebParam(name = "AuthenName")
String AuthenName,
@WebParam(name = "AuthenType")
String AuthenType,
@WebParam(name = "CustType")
String CustType,
@WebParam(name = "Password")
String Password,
@WebParam(name = "AreaCode")
String AreaCode,
@WebParam(name = "ExtendField")
String ExtendField);
生成的wsdl中，所有参数的minOccurs都是1，如下：
&s:complexType&
&s:sequence&
&s:element minOccurs="1" maxOccurs="1" name="SystemsID" type="s:string" /&
&s:element minOccurs="1" maxOccurs="1" name="AuthenName" type="s:string" /&
&s:element minOccurs="1" maxOccurs="1" name="AuthenType" type="s:string" /&
&s:element minOccurs="1" maxOccurs="1" name="CustType" type="s:string" /&
&s:element minOccurs="1" maxOccurs="1" name="Password" type="s:string" /&
&s:element minOccurs="1" maxOccurs="1" name="AreaCode" type="s:string" /&
&s:element minOccurs="1" maxOccurs="1" name="ExtendField" type="s:string" /&
&/s:sequence&
&/s:complexType&
这样的话，客户端就必须传每一个参数，我如何设置这个值呢？
哥们问题解决了吗？我也碰到这个问题了
已解决问题
未解决问题java wsdl 中不显示参数属性类型的有关问题解决方案
&来源：读书人网&【读书人网()：综合教育门户网站】
java wsdl 中不显示参数属性类型的问题解决方案最近采用CXF写了webservice接口，但是生成的wsdl却没有参数。
java wsdl 中不显示参数属性类型的问题解决方案
最近采用CXF写了webservice接口，但是生成的wsdl却没有参数。 首先介绍一下JWS的注解： Java Web Service (JWS) 注释类型是 Web Service 的核心之一。 （一）类级别@javax.jws.WebService(targetNamespace = "", name = "",serviceName = "") targetNamespace :生成的 WSDL 中使用的名称空间name:Web Service 的名称，映射到 WSDL 文件中的 &wsdl:portType& 元素serviceName: Web Service 的服务名,映射到 WSDL 文件&wsdl:service&&& 元素。@javax.jws.soap.SOAPBinding(parameterStyle = javax.jws.soap.SOAPBinding.ParameterStyle.BARE) 用于指定 Web Service 到 SOAP 消息协议的映射。parameterStyle :确定方法参数是否表示整个消息正文，或者参数是否是包装在以操作命名的顶层元素中的元素。默认值：javax.jws.soap.SOAPBinding.ParameterStyle.WRAPPED （二）方法级别@javax.jws.WebResult(name = "", targetNamespace = "", partName = "") name:指定生成的 WSDL 中的操作结果的名称, 默认名称“return”。@javax.jws.WebMethod(operationName="") operationName: 指定方法公开的公共操作名，映射到 WSDL 文件中的 &wsdl:operation& 元素。没有这个属性的话，操作的公共名称将与方法名相同。@javax.jws.WebParam(name="",targetNamespace="") name: 指定输入参数名,而不是该参数的Java 名称“input”。注释描述部分转载至：/blog/692279========================================那么为什么参数类型不在wsdl上显示呢？原因就在targetNamespace上。增加webservice interface和webservice impl的@webservice注解的targetNamespace属性。同时接口方法参数前@WebParam注解。接口代码，实现类就不展示了<pre name="code" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://impl.service.bus./" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:ns2="http://schemas.xmlsoap.org/soap/http" xmlns:ns1="http://service.bus./" name="MsgBusServiceImpl" targetNamespace="http://impl.service.bus./"&
&wsdl:import location="http://localhost/ucp/webservice/msgBusService?wsdl=IMsgBusService.wsdl" namespace="http://service.bus./"&
&/wsdl:import&
&wsdl:binding name="MsgBusServiceImplSoapBinding" type="ns1:IMsgBusService"&
&soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/&
&wsdl:operation name="showMsg"&
&soap:operation soapAction="" style="document"/&
&wsdl:input name="showMsg"&
&soap:body use="literal"/&
&/wsdl:input&
&wsdl:output name="showMsgResponse"&
&soap:body use="literal"/&
&/wsdl:output&
&/wsdl:operation&
&/wsdl:binding&
&wsdl:service name="MsgBusServiceImpl"&
&wsdl:port binding="tns:MsgBusServiceImplSoapBinding" name="MsgBusServiceImplPort"&
&soap:address location="http://localhost/ucp/webservice/msgBusService"/&
&/wsdl:port&
&/wsdl:service&&/wsdl:definitions&<pre name="code" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="" xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:ns1="http://schemas.xmlsoap.org/soap/http" name="MsgBusServiceImpl" targetNamespace=""&
&wsdl:types&&xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:tns="" elementFormDefault="unqualified" targetNamespace="" version="1.0"&
&xs:element name="showMsg" type="tns:showMsg"/&
&xs:element name="showMsgResponse" type="tns:showMsgResponse"/&
&xs:complexType name="showMsg"&
&xs:sequence&
&xs:element minOccurs="0" name="username" type="xs:string"/&
&xs:element minOccurs="0" name="password" type="xs:string"/&
&xs:element minOccurs="0" name="msgsObj" type="tns:multiMessages"/&
&/xs:sequence&
&/xs:complexType&
&xs:complexType name="multiMessages"&
&xs:sequence&
&xs:element minOccurs="0" name="accessType" type="xs:string"/&
&xs:element minOccurs="0" name="id" type="xs:string"/&
&xs:element name="msgCount" type="xs:int"/&
&xs:element maxOccurs="unbounded" minOccurs="0" name="msgList" nillable="true" type="tns:multiMessage"/&
&/xs:sequence&
&/xs:complexType&
&xs:complexType name="multiMessage"&
&xs:sequence&
&xs:element minOccurs="0" name="content" type="xs:string"/&
&xs:element minOccurs="0" name="description" type="xs:string"/&
&!-- ... ... --&
&xs:element minOccurs="0" name="destAgentId" type="xs:string"/&
&xs:element minOccurs="0" name="destination" type="xs:string"/&
&/xs:sequence&
&/xs:complexType&
&xs:complexType name="showMsgResponse"&
&xs:sequence&
&xs:element minOccurs="0" name="return" type="tns:response"/&
&/xs:sequence&
&/xs:complexType&
&xs:complexType name="response"&
&xs:sequence&
&xs:element minOccurs="0" name="message" type="xs:string"/&
&xs:element minOccurs="0" name="status" type="xs:string"/&
&/xs:sequence&
&/xs:complexType&&/xs:schema&
&/wsdl:types&
&wsdl:message name="showMsg"&
&wsdl:part element="tns:showMsg" name="parameters"&
&/wsdl:part&
&/wsdl:message&
&wsdl:message name="showMsgResponse"&
&wsdl:part element="tns:showMsgResponse" name="parameters"&
&/wsdl:part&
&/wsdl:message&
&wsdl:portType name="IMsgBusService"&
&wsdl:operation name="showMsg"&
&wsdl:input message="tns:showMsg" name="showMsg"&
&/wsdl:input&
&wsdl:output message="tns:showMsgResponse" name="showMsgResponse"&
&/wsdl:output&
&/wsdl:operation&
&/wsdl:portType&
&wsdl:binding name="MsgBusServiceImplSoapBinding" type="tns:IMsgBusService"&
&soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/&
&wsdl:operation name="showMsg"&
&soap:operation soapAction="" style="document"/&
&wsdl:input name="showMsg"&
&soap:body use="literal"/&
&/wsdl:input&
&wsdl:output name="showMsgResponse"&
&soap:body use="literal"/&
&/wsdl:output&
&/wsdl:operation&
&/wsdl:binding&
&wsdl:service name="MsgBusServiceImpl"&
&wsdl:port binding="tns:MsgBusServiceImplSoapBinding" name="IMsgBusService"&
&soap:address location="http://localhost/ucp/webservice/msgBusService"/&
&/wsdl:port&
&/wsdl:service&&/wsdl:definitions&&soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"&
&soapenv:Header&
&ns1:SessionType soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns:ns1="/webservices"&Stateless&/ns1:SessionType&
&ns2:UsernameToken soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns:ns2="/webservices"&test&/ns2:UsernameToken&
&ns3:PasswordText soapenv:actor="http://schemas.xmlsoap.org/soap/actor/next" soapenv:mustUnderstand="0" xmlns:ns3="/webservices"&test&/ns3:PasswordText&
&/soapenv:Header&
&soapenv:Body&
&SessionAccessService_SessionAccessPing_Input xsi:nil="true" xmlns="/xml/SessionAccess"/&
&/soapenv:Body&
&/soapenv:Envelope&
我有如上的header需要在wsdl中描述，请问有谁知道该怎么做么？
目前还没有答案
已解决问题
未解决问题用CXF中的wsdl2java工具时抛出SAXParseException,提示accessExternalSchema属性设置的限制而不允许file访问
[问题点数：50分，结帖人tyBaoErGe]
用CXF中的wsdl2java工具时抛出SAXParseException,提示accessExternalSchema属性设置的限制而不允许file访问
[问题点数：50分，结帖人tyBaoErGe]
只显示楼主
取消只显示楼主
匿名用户不能发表回复！|
每天回帖即可获得10分可用分！小技巧：
你还可以输入10000个字符
(Ctrl+Enter)
请遵守CSDN，不得违反国家法律法规。
转载文章请注明出自“CSDN（www.csdn.net）”。如是商业用途请联系原作者。如何修改WCF中wsdl的targetNamespace_百度知道
如何修改WCF中wsdl的targetNamespace
提问者采纳
If you browse the service WSDL you will see tempuri.hiphotos://h.org you will need to declare it,Cs of WCF configuration are a little different.jpg" esrc=" This will allow you to set the properties of the service itself.For a Workflow Service the A.Step 2://g.baidu://a.& Typically basicHttpBindingC – Contract – use the interface name from the ServiceContractName property (without the namespace)Step 3.jpg" esrc="/zhidao/wh%3D450%2C600/sign=b103b9f7d9b44aed591bb6e0862cab37/738bfcf4d54c70ff216c://a.com/zhidao/wh%3D600%2C800/sign=6f57bc77818ba61edfbbc/acb7d0a2d296be20c8ef.hiphotos.baidu:///services}IService<img class="ikqb_img" src="http://c;service&gt.org from Workflow Services WSDLFor workflow services the process is slightly different.baidu: Declare a namespace for the Workflow ServiceOpen the Workflow Service and click in the designer outside of an activity. Here is a default WCF /zhidao/pic/item/dbb44aed2e738bd433be098ca28b87d.hiphotos.jpg" target="_blank" title="点击查看大图" class="ikqb_img_alink"><img class="ikqb_img" src="http://c.hiphotos.hiphotos.hiphotos.baidu://g.baidu://h://h.&/zhidao/wh%3D600%2C800/sign=d7ebab9296cad1c8d0eefb31/4a36acaf2edda3cc9b7c039d02ef7.hiphotos.&nbsp.&nbsp.Service Name – use the ConfigurationName property from the WorkflowServiceA – Address – should be blank when hosted in IIS / AppFabricB – Binding – use the binding of your choice.jpg" esrc="/zhidao/wh%3D600%2C800/sign=5788eedf5c09ad330b778d/dbb44aed2e738bd433be098ca28b87d://h: Declare a namespace on each receive activityI wish it were possible to use a constant here but sadly it is not: Declare a namespace on your service contractThe namespace can be anything. Workflow services do not have a contract (it is inferred from the activities) so here is the /zhidao/wh%3D600%2C800/sign=9e6cb69fb01bbe064af68c/738bfcf4d54c70ff216c.jpg" target="_blank" title="点击查看大图" class="ikqb_img_alink"><img class="ikqb_img" src="http.hiphotos.hiphotos://g; For each receive activity you must declare the namespace and contract name using a special syntax of {namespace}IContractName.&nbsp://h.jpg" />How to /zhidao/pic/item/4a36acaf2edda3cc9b7c039d02ef7.Step /zhidao/wh%3D450%2C600/sign=237dceb7a8fee4f88bb0/acb7d0a2d296be20c8ef.or In this example I’ve set the ServiceContractName property to {<a href="http
资深电脑人
其他类似问题
为您推荐：
wsdl的相关知识
等待您来回答
下载知道APP
随时随地咨询
出门在外也不愁