On 28.10.2011 21:07, Michael Bayer wrote:
Looks like something related to deserializing without mappers set up, or 
deserializing into an environment where the class structure and/or mappers are 
not configured the same way.  This is usually not the way that manifests 
itself, though.   The key would be the change that started causing the issue.


actually, i guess this bug has been there the whole time, it's just that someone discovered it now.

    If you want to pdb into the mechanics of _new_state_if_none it might become 
apparent what the mismatch is - I can't do much without being shown how to 
reproduce it exactly.

Any more specifics/details/reproducing cases here would shed more light.

the link I provided has both the client and server implementations to reproduce the issue, maybe you didn't scroll up?

you can use suds the soap client or use curl wget etc. to perform a HTTP POST with the following data to http://localhost:7789/

|<SOAP-ENV:Envelope xmlns:ns0="com.mydomain.mobile" xmlns:xs="http://www.w3.org/2001/XMLSchema"; 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:ns1="http://schemas.xmlsoap.org/soap/envelope/"; 
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/";>
   <SOAP-ENV:Header/>
   <ns1:Body>
      <ns0:tpz_setPatients>
         <ns0:patients>
            <ns0:some_string>qwerty</ns0:some_string>
            <ns0:id>888</ns0:id>
         </ns0:patients>
      </ns0:tpz_setPatients>
   </ns1:Body>
</SOAP-ENV:Envelope>|


hope that helps,
burak




On Oct 28, 2011, at 12:30 PM, Burak Arslan wrote:

hi,

any ideas on what could be the cause of the following backtrace here?
https://gist.github.com/1322636#comments. this is probably something
i'll need to fix in rpclib code, but I don't see what causes this.

sqlalchemy version is latest trunk from today. the backtrace is one line
off because of a comment, no change in source code around there.

thanks,
burak

--
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en.


--
You received this message because you are subscribed to the Google Groups 
"sqlalchemy" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sqlalchemy?hl=en.

Reply via email to