[JBossWS] - Re: BUG: MTOM with JBossWS 1.2.0SP1 server and Axis2 client - jboss-user

Tuesday, 27 March 2007

 Using SoapUI as client I collected the following trace at JBossWS side:

  |  2007-03-28 00:17:59,296 DEBUG [org.jboss.ws.core.server.ServiceEndpoint] BEGIN
handleRequest: jboss.ws:context=ETI-ETI_Framework,endpoint=ETI_ReceiverBean
  | 2007-03-28 00:17:59,296 DEBUG [org.jboss.ws.core.soap.MessageFactoryImpl]
createMessage: [contentType=multipart/related; type="application/xop+xml"; 
  | 	start=&quot;&lt;rootpart(a)soapui.org&gt;&quot;; startinfo="text/xml;
action=\"\""; 
  | 	boundary="----=_Part_16_1798874.1175033879281"]
  | 2007-03-28 00:17:59,312 DEBUG
[org.jboss.ws.core.soap.attachment.SwapableMemoryDataSource] Using memory buffer, size =
707
  | 2007-03-28 00:17:59,312 DEBUG
[org.jboss.ws.core.soap.attachment.SwapableMemoryDataSource] Using memory buffer, size =
81
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS]
callRequestHandlerChain: PRE
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
initHandlerChain: PRE
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
Clear handler map: {}
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
initHandlerChain: ENDPOINT
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
Clear handler map: {}
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
initHandlerChain: POST
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
Clear handler map: {}
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
getHandlerChain:
[type=PRE,info=[service={http://siemens.com/ws}ETI_ReceiverBeanService,por...]
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor]
Create a handler executor: []
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.SOAPMessageDispatcher]
getDispatchDestination: {http://siemens.com/ws}downloadRelationships
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.binding.SOAP11BindingJAXWS]
unbindRequestMessage: {http://siemens.com/ws}downloadRelationships
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.EndpointInvocation]
setRequestParamValue:
[name={http://siemens.com/ws/types}downloadRelationships,value=org.jboss.w...]
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS]
callRequestHandlerChain: ENDPOINT
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
initHandlerChain: PRE
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
Clear handler map: {}
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
initHandlerChain: ENDPOINT
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
Clear handler map: {}
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
initHandlerChain: POST
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
Clear handler map: {}
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
getHandlerChain:
[type=ENDPOINT,info=[service={http://siemens.com/ws}ETI_ReceiverBeanServic...]
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor]
Create a handler executor: []
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerDelegateJAXWS]
callRequestHandlerChain: POST
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
initHandlerChain: PRE
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
Clear handler map: {}
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
initHandlerChain: ENDPOINT
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
Clear handler map: {}
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
initHandlerChain: POST
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
Clear handler map: {}
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerResolverImpl]
getHandlerChain:
[type=POST,info=[service={http://siemens.com/ws}ETI_ReceiverBeanService,po...]
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.handler.HandlerChainExecutor]
Create a handler executor: []
  | 2007-03-28 00:17:59,312 DEBUG
[org.jboss.ws.integration.jboss42.ServiceEndpointInvokerEJB3] invokeServiceEndpoint:
downloadRelationships
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.EndpointInvocation]
getRequestPayload
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.EndpointInvocation]
getRequestParamValue: {http://siemens.com/ws/types}downloadRelationships
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.SOAPContentElement]
-----------------------------------
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.SOAPContentElement]
Transitioning from XML_VALID to OBJECT_VALID
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.XMLContent] getObjectValue
[xmlType={http://siemens.com/ws}downloadRelationships,javaType=class
com.siemens.icm.nm.rc.eti.framework.common.generated.wsdl.DownloadRelationshipsType]
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialize:
[xmlName={http://siemens.com/ws/types}downloadRelationships,xmlType={http:...]
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxws.JAXBDeserializer] deserialized:
com.siemens.icm.nm.rc.eti.framework.common.generated.wsdl.DownloadRelationshipsType
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.XMLContent] objectValue:
com.siemens.icm.nm.rc.eti.framework.common.generated.wsdl.DownloadRelationshipsType
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.soap.SOAPContentElement]
-----------------------------------
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.EndpointInvocation]
transformPayloadValue: org.jboss.ws.core.soap.SOAPBodyElementDoc ->
com.siemens.icm.nm.rc.eti.framework.common.generated.wsdl.DownloadRelationshipsType
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.jaxrpc.ParameterWrapping]
unwrapRequestParameters:
com.siemens.icm.nm.rc.eti.framework.common.generated.wsdl.DownloadRelationshipsType
  | 2007-03-28 00:17:59,312 INFO  [STDOUT] 0
  | 2007-03-28 00:17:59,312 DEBUG [org.jboss.ws.core.EndpointInvocation] setReturnValue:
null
  |  

 Additonal information:
 - I tried to send a file with size 81 bytes.
 - The [STDOUT] 0 means the filesize of the received attachment (0).
 - It can be seen that I set the binding type properly
getHandlerChain:
[type=POST,info=[service={http://siemens.com/ws}ETI_ReceiverBeanService,po...]

 Do you have any idea what is the problem? 

View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032241#...

Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

[JBossWS] - Re: BUG: MTOM with JBossWS 1.2.0SP1 server and Axis2 client