[ http://issues.apache.org/jira/browse/TUSCANY-258?page=comments#action_12377533 ]
ant elder commented on TUSCANY-258: ----------------------------------- This is yet another classloader issue similar to TUSCANY-253 and all the others. As a hack trying switching back to a saved version or the original thread context class loader gets past this and the fromOMElement call works...but then the BB accountservice fails as, you guessed it, its using the wrong class loader so gets back a dynamic DataObject, hacking in a fix for that gets past that...but then converting that back to an OMElement fails due to...using the wrong class loader! The current code seems to have a fundamental design flaw in the way the current classloader is swapped back and forth between the web app classloader and the Tuscany system classloader. > Static DataObjects are not correctly deserialized from WS request messages > -------------------------------------------------------------------------- > > Key: TUSCANY-258 > URL: http://issues.apache.org/jira/browse/TUSCANY-258 > Project: Tuscany > Type: Bug > Components: Java SCA Axis Binding, Java SDO Implementation > Reporter: ant elder > Priority: Blocker > > All WS entryPoints that used static DataObjects fail as the incoming SOAP > message doesn't get correctly deserialized. Instead of getting a single > DataObject back from dataBinding.fromOMElement(requestOM) it returns an array > of 5 other objects, all SDO type things. > To reproduce run BB > URL to start http://localhost:8080/webclient-SNAPSHOT/login.html > logon with test/password -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
