function readOnly(count){ }
Sign Up ›
Starting November 20, the site will be set to read-only. On December 4, 2023,
forum discussions will move to the Trailblazer Community.
Learn More

Browse by Topic
ShowAll Questionssorted byDate Posted
+ Start a Discussion
MerialMerial 

JS S-Control and SOAP Fail in Summer 08

Greetings:
 
I've several s-controls that generates XML to talk with BEA Weblogic, since summer 08 they won't work fine, the error jumps in "connection.js" and i'm building the XML with JS. The code for this is:
 
Code:
var altaString= '<Alta xmlns="http://xxx/sva/">' 
 + '<canal>' + canal + '</canal>' 
 + '<login_ip>' + login_ip + '</login_ip>' 
 +'<deal_compra>' + vchDealCompra +'</deal_compra>' 
 +'<id_incidente>' + id_incidente + '</id_incidente>' 
 +'<precio_producto>'+ precio + '</precio_producto>' 
 +'<nombre>'+ nombre+ '</nombre>' 
 +'<apellido>'+ apellido + '</apellido>' 
 +'<id_cliente>' + id_cliente + '</id_cliente>' 
 +'<tipo_cliente>' + tipo_cliente + '</tipo_cliente>' 
 +'<tipo_venta>' + tipo_venta + '</tipo_venta>' 
 +'<asignado>'+asignado+'</asignado>' 
 +'</Alta>'; 
 var oSoapClient = new ActiveXObject("MSSOAP.SoapClient30"); 
 oSoapClient.mssoapinit ('http://xxx/xxx/xx/xxx.wsdl'); 
 
 var resultado = oSoapClient.xxx(altaString);

 
I'm really complicate with this, anyone please?
 
werewolfwerewolf
I don't see anything in here that would cause a problem with summer 08, it looks like straight up Javascript.  What error are you getting?
MerialMerial
Thank's for responding.

BEA responses well, the problem jumps in "connection.js", maybe were some changes in summer for this one, this is a picture:



The window who made the connection to BEA should give one alert ("succes") and close by itself, but instead of that it keeps waiting because the error.  The problem is that bejore summer 08 it works just fine..now it doesn't.

Any ideas?

Thanks
werewolfwerewolf
Have you examined the fault to see exactly what the error is?  Maybe run it with Firebug or the VS debugger to look into it?  My first guess would be a cross-site scripting block.
MerialMerial
this is a screenshot of the messages of the Firebug when the s-control fails
MerialMerial
Hi:

Thanks for your help, we've found the error, leave it here in case someone else's search for it.

The problem was a query bellow my code, which create a new opp and change the owner, so, i was creating a new "Owner" but in summer '08 the field is named "OwnerId"...so that's why everything else fail starting in the next line after send the new XML to Weblogic...

Again thank you for your help...
SuperfellSuperfell
Well, the field has always been ownerId, not just from summer '08