Axis2 响应中丢失附件

发布于 2024-12-06 17:53:23 字数 2274 浏览 0 评论 0原文

我正在尝试从 Axis2 Web 服务向客户端发送附件。问题在于,客户端从服务接收的消息上下文不包含任何附件,尽管最后一个似乎添加了附件。 这是双方的简要代码。 服务:

MessageContext inMC = MessageContext.getCurrentMessageContext();
OperationContext operationContext = inMC.getOperationContext();
MessageContext outMC = operationContext.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
DataHandler handler = new DataHandler (new FileDataSource("C://goods.xml"));
String attachID = outMC.addAttachment(handler);
OMElement idElem = factory.createOMElement("doc", ns);
idElem.addAttribute("href", "cid:" + attachID, ns);

客户端(尝试接收附件):

MessageContext mcResponse = operationClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
SOAPBody body = mcResponse.getEnvelope().getBody();
OMElement attachElem = body.getFirstChildWithName (new QName("doc"));
String attachID = attachElem.getAttributeValue (new QName("href"));
attachID = attachID.replaceFirst("cid:", "");
DataHandler dataHandler = mcResponse.getAttachment(attachID);

getAttachment() 方法返回 null。在调试客户端应用程序时,IDE 显示输入消息上下文中的附件映射不包含任何元素 (size=0)。包含附件 id 的 OMElement 对象 (idElem) 被客户端正常接收和读取(调试显示 cid)。参数enableSwA、cacheAttachments、attachmentDIR、sizeThreshold 均在services.xml 和客户端的编程部分中设置。消息上下文有什么问题? 非常感谢您的任何建议。

更新:TCPmon 显示以下内容。 服务请求:

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><getXMLFile xmlns="http://axis2.apache.org"><filename>goods.xml</filename></getXMLFile></soapenv:Body></soapenv:Envelope>

我想没问题:)

服务响应:

109
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><doc href="cid:[email protected]"></doc></soapenv:Body></soapenv:Envelope>
0

对于一些简单的问题我深表歉意,但是附件应该反映在哪里?我想,如果服务发送附件,则 SOAP 消息包含二进制数据,不是吗? 我还检查了是否将附件放入服务端的消息上下文中 - 没关系,添加后我可以从上下文中将其返回。

I'm trying to send an attachment to client from Axis2 web service. The problem is that the message context, which client receives from the service, does not contain any attachments, though the last one seems to add it.
Here is the brief code of both sides.
Service:

MessageContext inMC = MessageContext.getCurrentMessageContext();
OperationContext operationContext = inMC.getOperationContext();
MessageContext outMC = operationContext.getMessageContext(WSDLConstants.MESSAGE_LABEL_OUT_VALUE);
DataHandler handler = new DataHandler (new FileDataSource("C://goods.xml"));
String attachID = outMC.addAttachment(handler);
OMElement idElem = factory.createOMElement("doc", ns);
idElem.addAttribute("href", "cid:" + attachID, ns);

Client (trying to receive attachment):

MessageContext mcResponse = operationClient.getMessageContext(WSDLConstants.MESSAGE_LABEL_IN_VALUE);
SOAPBody body = mcResponse.getEnvelope().getBody();
OMElement attachElem = body.getFirstChildWithName (new QName("doc"));
String attachID = attachElem.getAttributeValue (new QName("href"));
attachID = attachID.replaceFirst("cid:", "");
DataHandler dataHandler = mcResponse.getAttachment(attachID);

getAttachment() method returns null. In case of debugging the client application, IDE shows, that attachment map in input message context does not contain any elements (size=0). The OMElement object (idElem), which contains attachment id, is received and read by client normally (debug showed cid). The parameters enableSwA, cacheAttachments, attachmentDIR, sizeThreshold are set both in services.xml and programming part of client. What is wrong with the message context?
Thanks a lot for any suggestions.

Upd: TCPmon showed the following content.
Request to service:

<?xml version="1.0" encoding="UTF-8"?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><getXMLFile xmlns="http://axis2.apache.org"><filename>goods.xml</filename></getXMLFile></soapenv:Body></soapenv:Envelope>

I guess it's ok :)

Response from service:

109
<?xml version='1.0' encoding='UTF-8'?><soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"><soapenv:Body><doc href="cid:[email protected]"></doc></soapenv:Body></soapenv:Envelope>
0

I apologize for a bit simple questions, but where the attachment should be reflected? I guess, if the service send an attachment, the SOAP message contains binary data, isn't it?
I checked also for putting the attachment into message context on service side - it's OK, I can get it there back from context after adding.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

幸福还没到 2024-12-13 17:53:23

您可以使用 tcpmon[1] 跟踪 http 消息并隔离问题。

无论如何,处理附件的更好方法是使用 MTOM。它可以与 ADB[2] 等数据绑定框架一起使用,也可以与 POJO 一起使用。

谢谢,
阿米拉。

[1] http://ws.apache.org/commons/tcpmon/

[2] http://amilachinthaka.blogspot.com/2009/01/using-mtom-with-axis2.html

you can use tcpmon[1] to trace the http message and isolate the problem.

Anyway the better method for handling attachments is to use MTOM. Which can be used with data binding frameworks like ADB[2], or with POJO as well.

thanks,
Amila.

[1] http://ws.apache.org/commons/tcpmon/

[2] http://amilachinthaka.blogspot.com/2009/01/using-mtom-with-axis2.html

神经暖 2024-12-13 17:53:23

问题解决了。问题出在服务方面。 TCPmon 显示响应消息中没有附件。但是,相同的示例服务工作正常。在检查和比较我的服务上的每个操作后,发现编程部分也不是原因。只剩下一项了——服务设置。因此,原因是服务上的 service.xml 文件中的设置字段需要布尔类型,不允许任何附加符号。我的错误:

错误:

    <parameter name="enableSwA">
        true
    </parameter>

正确:

<parameter name="enableSwA">true</parameter>

The problem was solved. The trouble was on the service side. TCPmon showed there was no attachments in responce message. However, the same example service works fine. After checking and comparing every operation on my service, it came out that programming part is not the reason either. The only one was left - service settings. So, the reason is that settings fields in service.xml file on the service, which require boolean type, does not allow any additional symbols. My mistake:

Incorrect:

    <parameter name="enableSwA">
        true
    </parameter>

Correct:

<parameter name="enableSwA">true</parameter>
~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文