普元EOS7.5生成入参为数组的WebService接口

最新推荐文章于 2022-05-05 10:28:32 发布

试着奔跑的菜鸟

最新推荐文章于 2022-05-05 10:28:32 发布

阅读量1.1k

点赞数 1

分类专栏：普元EOS 文章标签： webservice 普元EOS

本文链接：https://blog.csdn.net/qq_28194001/article/details/113485097

版权

普元EOS 专栏收录该内容

4 篇文章 0 订阅

订阅专栏

项目场景：

普元EOS7.5开发工具（本文简称为EOS）提供便捷的一键生成WebService接口服务。

虽然也支持生成HTTP的接口，但是这个旧工具还是生成WebService方便且不会有什么接收参数的问题，生成RestFul方式的接口请看另一篇文章

普元EOS7.5生成RestFul接口服务

我们平时生成的WebService入参多数时候使用DataObject的格式或者直接的基本类型入参，但是当我们需要用对象数组时，使用DataObject就无法实现我们的需求了

问题描述：

当我第一时间接到用对象数组作为入参时，我第一时间就想到使用DataObject实体对象数组，结果在我耗费了好几个小时的情况下还是失败了，这才想起以前自己和同时也曾在这里踩过坑，竟然忘记了。具体的使用数据实体过程就不详细描述了，大家可以看官方文档来操作。

首先在使用DataObject[]作为入参时，虽然生成WebService会成功，但是客户端调用时会出现下面的问题

<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
   <soapenv:Body>
      <soapenv:Fault>
         <faultcode>soapenv:Server</faultcode>
         <faultstring>java.lang.IllegalStateException: Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE</faultstring>
         <detail>
            <Exception>org.apache.axis2.AxisFault: java.lang.IllegalStateException: Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE
	at org.apache.axis2.AxisFault.makeFault(AxisFault.java:417)
	at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:204)
	at org.apache.axis2.receivers.AbstractInOutSyncMessageReceiver.invokeBusinessLogic(AbstractInOutSyncMessageReceiver.java:42)
	at org.apache.axis2.receivers.AbstractMessageReceiver.receive(AbstractMessageReceiver.java:96)
	at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:145)
	at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)
	at org.apache.axis2.transport.http.AxisServlet.doPost(AxisServlet.java:120)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:727)
	at com.primeton.sca.host.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:102)
	at com.primeton.sca.host.webapp.SCAWebServiceServletFilter.doIntercept(SCAWebServiceServletFilter.java:117)
	at com.primeton.access.http.impl.WebInterceptorChainImpl.doIntercept(WebInterceptorChainImpl.java:56)
	at com.eos.access.http.InterceptorFilter.doFilter(InterceptorFilter.java:120)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:220)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:122)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:501)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:171)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:950)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:408)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1040)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:607)
	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
	at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:895)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:918)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:662)
Caused by: org.osoa.sca.ServiceRuntimeException: java.lang.IllegalStateException: Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE
	at org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:119)
	at org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:85)
	at org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:79)
	at org.apache.tuscany.sca.core.assembly.RuntimeWireImpl.invoke(RuntimeWireImpl.java:138)
	at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceProvider.invokeTarget(Axis2ServiceProvider.java:709)
	at org.apache.tuscany.sca.binding.ws.axis2.Axis2ServiceInOutSyncMessageReceiver.invokeBusinessLogic(Axis2ServiceInOutSyncMessageReceiver.java:113)
	... 28 more
Caused by: java.lang.IllegalStateException: Current state not START_ELEMENT, END_ELEMENT or ENTITY_REFERENCE
	at com.ctc.wstx.sr.BasicStreamReader.getLocalName(BasicStreamReader.java:713)
	at com.primeton.ext.infra.xsd.xmlser.StreamReader.getLocalName(StreamReader.java:79)
	at com.primeton.data.sdo.impl.serialize.DataObjectConverter.unmarshal(DataObjectConverter.java:138)
	at com.primeton.infra.xsd.impl.xmlser.UnmarshallingContext.unmarshal(UnmarshallingContext.java:138)
	at com.primeton.infra.xsd.impl.xmlser.UnmarshallingContext.unmarshal(UnmarshallingContext.java:129)
	at com.primeton.ext.infra.xsd.xmlser.XMLSerializer.unmarshal(XMLSerializer.java:435)
	at com.primeton.ext.infra.xsd.xmlser.XMLSerializer.unmarshal(XMLSerializer.java:355)
	at com.primeton.ext.infra.xsd.xmlser.XMLSerializer.unmarshal(XMLSerializer.java:328)
	at com.primeton.sca.serialize.sdo.DataObjectTransformer.unmarshall(DataObjectTransformer.java:32)
	at com.primeton.ext.sca.serialize.DataTransformer.unmarshallServerReceive(DataTransformer.java:205)
	at com.primeton.sca.xmltransformer.OMElementTransformer.transforInputOmelement(OMElementTransformer.java:68)
	at com.primeton.sca.transformer.Input2InputTransformer.transform(Input2InputTransformer.java:267)
	at com.primeton.sca.transformer.Input2InputTransformer.transform(Input2InputTransformer.java:51)
	at org.apache.tuscany.sca.databinding.impl.MediatorImpl.mediate(MediatorImpl.java:81)
	at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.transform(DataTransformationInterceptor.java:200)
	at org.apache.tuscany.sca.core.databinding.wire.DataTransformationInterceptor.invoke(DataTransformationInterceptor.java:80)
	at org.apache.tuscany.sca.core.invocation.RuntimeWireInvoker.invoke(RuntimeWireInvoker.java:110)
	... 33 more</Exception>
         </detail>
      </soapenv:Fault>
   </soapenv:Body>
</soapenv:Envelope>

原因分析：

相关的逻辑流和实体配置如下图，可以看到我们生成的wsdl在SoapUI的解析下，param1和param2缺少了命名空间前缀，调用之后也没有进入到我们的逻辑流，并且返回了异常信息。当我们需要使用对象数组作为入参时，不能使用DataObject类型，需要自己定义java bean类作为入参，否则使用EOS自带的生成WebService功能无法生成对应的接口。
数据实体配置

逻辑流参数
SoapUI访问情况

解决方案：

使用自定义的bean类ImportParam作为入参，并在逻辑流中设置为数组类型

package com.eos.test;

public class ImportParam {
	private String param1;
	private String param2;

	public String getParam1() {
		return param1;
	}

	public void setParam1(String param1) {
		this.param1 = param1;
	}

	public String getParam2() {
		return param2;
	}

	public void setParam2(String param2) {
		this.param2 = param2;
	}
}