I would go for the new Apache Axis SOAP libraries. If the Library is *lightweighted* build in it could be a future advantage that OpenLaszlo can quickly adopt new SOAP version or extended SOAP procedures like SOAP with attachement by simply replacing / upgrading the server side part with the new Axis libs. That should be less work then maintaining an own Client Side Soap lib and adopt that to new WSDL-Versions.
Anotherother features of Axis2 is a REST-Style WebService Gateway, maybe usefull for OpenLaszlo too. sebastian 2008/7/23 Henry Minsky <[EMAIL PROTECTED]>: > On Wed, Jul 23, 2008 at 12:06 PM, Sebastian Wagner > <[EMAIL PROTECTED]> wrote: > > +++ for: try to upgrade the apache libraries on the server ... I jut run > > into the problem that OpenLaszlo cannot speak to Axis2 > > > > *try to do a completely client side SOAP implementation* > > => nice but I think as consequence you will see plenty of mails on the > > mailing list asking: > > *SecuritySandBox error whats this???* > > Well, we would still support proxying via the LPS server, or some > basic XML proxy. The > XMLRPC implementation I just did uses the standard lzt=xmldata request to > proxy > XML-RPC requests as a regular data proxy request. > > For SOAP, I think the same thing could be done, just treat the SOAP > message as the XML payload, and relay > the XML response. > > What do you think, Sebastian, is it worth trying to use the new Apache > Axis SOAP libraries > on the server, or to try to do a completely client-side SOAP client? > > > > > just my thoughts > > > > 2008/7/23 Henry Minsky <[EMAIL PROTECTED]>: > >> > >> I have a changeset which implements client-side XMLRPC support for > >> swf8, dhtml, and swf9. > >> This means that you can do SOLO XMLRPC (conditional on the security > >> model of the runtime allowing the requests). > >> > >> I'm thinking of just checking this in, even though it breaks javarpc and > >> soap. > >> > >> My next task is to make the javarpc responder in the LPS server return > >> XMLRPC instead of json/swf, and then > >> java rpc will work again. > >> > >> After that, the question is what to do about SOAP support. > >> > >> The quick fix is to modify the DHTML SOAP server side code to return > >> XMLRPC instead of JSON, > >> and then SOAP will work as much as it does now, in theory. However, it > >> might be a good time to > >> either try to upgrade the apache libraries on the server to something > >> more modern for proxied SOAP requests > >> (gah), or else to try to do a completely client side SOAP > >> implementation (painful, but would allow SOLO > >> operation, again subject to security model of the runtime). > >> > >> > >> -- > >> Henry Minsky > >> Software Architect > >> [EMAIL PROTECTED] > > > > > > > > -- > > Sebastian Wagner > > http://www.webbase-design.de > > http://openmeetings.googlecode.com > > http://www.laszlo-forum.de > > [EMAIL PROTECTED] > > > > -- > Henry Minsky > Software Architect > [EMAIL PROTECTED] > -- Sebastian Wagner http://www.webbase-design.de http://openmeetings.googlecode.com http://www.laszlo-forum.de [EMAIL PROTECTED]
