[ 
https://issues.apache.org/jira/browse/CXF-7861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16646452#comment-16646452
 ] 

Colm O hEigeartaigh commented on CXF-7861:
------------------------------------------

I meant what does the message look like on the wire? It is obviously expecting 
"*{urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0}RegistryResponse*". What does the 
message contain instead?

> getting IllegalEmptyResponseException in ClientImpl class
> ---------------------------------------------------------
>
>                 Key: CXF-7861
>                 URL: https://issues.apache.org/jira/browse/CXF-7861
>             Project: CXF
>          Issue Type: Bug
>         Environment: CXF 3.2.6
> JAVA 1.8
> WSS4J 2.2.2
>            Reporter: yagnya dutta dhal
>            Priority: Major
>         Attachments: exchange.PNG, soapmessage.PNG
>
>
> Hi,
> After debugging a lot I found out following exception in 
> processresult method of ClientImpl class.
> *org.apache.cxf.endpoint.ClientImpl$IllegalEmptyResponseException: Response 
> message did not contain proper response data. Expected: 
> \{urn:oasis:names:tc:ebxml-regrep:xsd:rs:3.0}RegistryResponse*
>  
> *GIT link- https://github.com/yagnyadutta/wss4jpoc/tree/master/wss4jtest*
> +*code snippet from ClientImpl*+
> if (ex != null) {
>  throw ex;
> } else {
>  if (resList == null && oi != null && !oi.getOperationInfo().isOneWay()) {
>  BindingOperationInfo boi = oi;
>  if (oi.isUnwrapped()) {
>  boi = oi.getWrappedOperation();
>  }
>  if (!boi.getOutput().getMessageParts().isEmpty()) {
>  throw new ClientImpl.IllegalEmptyResponseException("Response message did not 
> contain proper response data. Expected: " + 
> ((MessagePartInfo)boi.getOutput().getMessageParts().get(0)).getConcreteName());
>  }
>  }
>  return resList != null ? resList.toArray() : null;
> }
> This is coming after upgrading CXF to 3.2.6 from CXF2.7.6
> Please do suggest if anything I'm missing in upgradation.
> Thanks,
> Yagnya



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to