It is internally developed in the team.
Could you point as to what exactly is missing?
Giriraj.
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.
