Forum Discussion
nmrao
9 years agoChampion Level 3
Have you checked with the service provider or with your team if it is internally developed? My guess is that it is something to do with the application than soapui?
- giriraj9 years agoNew Contributor
It is internally developed in the team.
Could you point as to what exactly is missing?
Giriraj.
- nmrao9 years agoChampion Level 3Did you show it to your team then? I meant application defect.
java.lang.Exception: Missing message wrapper element [http://company.com/entity/Entity@EntityInstance.- giriraj9 years agoNew Contributor
This doesn't look like an application defect.
The attachment goes fine when there is no outgoing/incoming WS-Security configuration.
I have noticed that this error only occurs when I add an Encryption WSS Entry.
Without encryption, the attachment is sent even when other WSS entries are present.
It is complaining about a wrapper element being not present.
This wrapper element has the file attachment element.
Since the SOAP body is encrypted the actual wrapper element is encrypted too.
Is there a config/property that I am missing in SoapUI?
Giriraj.
Related Content
- 11 years ago
- 8 years ago
Recent Discussions
- 15 years ago