[
https://issues.apache.org/jira/browse/AXIS2-6046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17626843#comment-17626843
]
Robert Lazarski commented on AXIS2-6046:
----------------------------------------
Please test with 1.8.2 as the package name of HTTPSender changed.
Also, make sure your axis2.xml file is up to date.
Lastly, please paste the entire stack trace.
> AxisFault after upgrade to 1.8.0
> --------------------------------
>
> Key: AXIS2-6046
> URL: https://issues.apache.org/jira/browse/AXIS2-6046
> Project: Axis2
> Issue Type: Bug
> Components: transports
> Affects Versions: 1.8.0
> Reporter: 杨林
> Priority: Blocker
> Attachments: image-2022-10-08-11-48-20-446.png,
> image-2022-10-08-11-49-30-028.png
>
>
> After update to 1.8.0 from 1.7.9 , I received an
> AxisFault：java.text.ParseException: Token expected
> The cause of the AxisFault is that content-type is empty.
> !image-2022-10-08-11-49-30-028.png!
> I use axis2 to send a soap message as a notification to third-party . And i
> only need a response ,don`t care about the response content 。 In addition,
> the third-party simply returns a response with empty body . such as
> !image-2022-10-08-11-48-20-446.png|width=543,height=147!
>
> And OperationClient is OutOnlyAxisOperationClient
> Is content-type mandatory in this scenario?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org
For additional commands, e-mail: java-dev-h...@axis.apache.org
