Hello Anders,
Strange, but somehow that seems to be allowed according to the soap spec, even though it would normally not be allowed according to the spec of XML schema. Maybe I have to create some exception/special case. I'll look into it later this week.
In the mean time you could try to add an '<anyAttribute>' element to the schema that defines processNPCMsg. It could look roughly like this:
<complexType ...processNPCMsg...>
         ... your elements
    <anyAttribute namespace="##any"/>
Good luck,

On Sat, Jun 21, 2008 at 8:31 AM, Anders Nygren <anders.nygren@gmail.com> wrote:
I am receiving SOAP requests that contains soap:encodingStyle attributes.
This causes erlsom:scan to complain.
It is my understanding that soap:encodingStyle is an attribute that shall be
possible to use anywhere.
Is that correct?
If so what do I have to do to make erlsom happy and accept these messages?

The received messages starts like this
<?xml version="1.0" encoding="UTF-8"?>


<ns1:processNPCMsg soapenv:encodingStyle="UTF-8"

And I get this error

yaws_soap_srv(224): Cli Error: {decoding,
                                  "Unexpected attribute: encodingStyle"}},



Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
Erlyaws-list mailing list