Thats a fair call Benson :) Will give it a go...
bimargulies wrote: > > How would you feel about making and submitting a patch? > > On Thu, Nov 19, 2009 at 12:51 AM, noosy > <[email protected]>wrote: > >> >> I am trying to use my WSDL2JS generated client code in an existing >> project >> that uses the Ext JS library. I'm finding that it is no longer calling WS >> operations successfully. >> >> When I compare my WSDL2JS generated client code integrated with Ext, and >> without Ext, I notice the following differences: >> >> Ext adds a remove() method to the Array prototype. >> >> This seems to be causing problems within the following lines of code in >> cxf-utils.js (line 718) >> >> if (headers) { // must be array indexed by header field. >> for (var h in headers) { >> this.req.setRequestHeader(h, headers[h]); >> } >> } >> >> First itereation, h = "SOAPAction", second iteration, h = "remove" >> >> This seems to stuff up my request and my WS call doesn't work. >> >> If I break out of the for loop after one iteration the code works. >> >> Googling tells me Ext have no intention of changing this extension and so >> I'm wondering, would you guys consider supporting it or do I need to try >> and >> override what Ext is doing somewhere in my code? I'm new to JS so I'm >> sort >> of not sure whether CXF developers would consider this a bug or simply >> say >> that what Ext is doing is my problem? >> >> I would like to know a recommended solution if someone who knows more >> about >> this stuff than me could provide some insight? >> >> >> -- >> View this message in context: >> http://old.nabble.com/WSDL2JS-and-Ext-JS-woes-tp26420788p26420788.html >> Sent from the cxf-user mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://old.nabble.com/WSDL2JS-and-Ext-JS-woes-tp26420788p26470946.html Sent from the cxf-user mailing list archive at Nabble.com.
