OK thank you all for your comments, I'll try to address them all. 1. I AM using QXmlStreamReader to read WSDL files - I just assumed it's in QXML module without checking, so - my bad. It would now seem that XML module is not required by my project.
2. Licence. I am open for suggestions here, if you prefer LGPL, so it could be. Since AFAIK I am currently the only user of this code, I can change it without any problems caused to anybody. Mind you, only a part of the project is a library (QWebService), the second part is the WSDL converter, which is - obviously - a console app. Would that be a problem? I'm not an expert when it comes to licences. 3. @Peter Hartmann - it's actually my first project using XML in Qt, I would certainly like to learn more, but I cannot guarantee anything extraordinary now. Partially that is why I post info about it here - if you like it, and want to see it not just as a hobbyist project, but as part of Qt, you'll have to help me - especially in a) licencing issues, b) more hardcore web service details (I lack experience in big WS projects, too). 4. Regarding providing server functionality. Just to mention - it would be a major endeavor, as we'll have to implement various tricky features like BPEL4WS, and use of still not ready QtServer functionality. 5. Since talks are getting more serious, another point to consider is whether we like to see QWebService as a major platform for accessing any WS, or just a simple reader for out-of-the-box use (this approach will make other commercial packages happy :) ). What I mean here is, say: you are writing a Qt app for a mobile device, and need to make a simple query - for example, get current Euro to Dollar ratio. You don't have to write much of your own code, nor use big monsters like GSOAP, you simply fire a QWebMethod::sendMessage() and parse the reply on your own. This is possible right now, as my current implementation does that. I am extending the functionality, of course, but if we were to make it really full-featured web service suite, it might require different approach. Or maybe not? Just a thought. sierdzio. On 15 August 2011 15:00, Jason H <[email protected]> wrote: > Various comments: > - I would prefer it to be LGPL so it might be included in Qt proper... > - Someone asked about not using QtXML and just stream reader classes. I > agree for the run-time stuff it would be nice to use the stream stuff in > QtCore, but I don't see the wsdl utility usign QtXML being a big deal. > - A purist might want to see it not require networking (just provide request > serialization) so you could do SOAP over email > (http://www.w3.org/TR/soap12-email) and other exotic bindings (RPC, etc) > > - I haven't had time to check this out in detail, but I am excited about it > and I will attempt to enhance it rather than roll my own again. For > contributions, I'll share what I do, but I'd prefer my work being LGPL > licensed. > > ________________________________ > From: qt next <[email protected]> > To: [email protected] > Cc: [email protected] > Sent: Monday, August 15, 2011 8:33 AM > Subject: Re: [Qt5-feedback] Web service functionality in Qt5 > > @Tomasz : Do you plan to release QWebService with another licence : Lgpl > ?MIT? BSD? to allow commercial uses ? > > > 2011/8/15 Peter Hartmann <[email protected]> > > (the reply might not show up in thread, I joined the mailing list after > this message was posted) > > @Tomasz: > > I like your idea regarding a SOAP code generator approach, here some > thoughts: > > * regarding your WSDL-to-C++ generator: Are you planning to access the > Qt schema data model in xmlpatterns (src/xmlpatterns/schema/)? That > might be the way to go, so you get a Qt representation of the XML schema > portion of a WSDL file for free. Accessing the functionality might be > tricky though, you would need to include private header files etc. > > * Using Qt XML module: How about using QXmlStream* classes in the core > module? They are much more memory efficient, but operate on a lower > layer (like SAX), but in the case of SOAP where XML messages can become > quite big you might not want to have the whole DOM in memory. > > Btw. there will be a talk titled "Qt Networking - Web Services" at the > DevDays 2011 (see http://qt.nokia.com/qtdevdays2011/techtrack), but that > talk will be targeting REST based Web Services... > > Regards, > > Peter > > -- > Qt Developer Days 2011 – REGISTER NOW! > October 24 – 26, Munich > November 29 – December 1, San Francisco > Learn more and Register at http://qt.nokia.com/qtdevdays2011 > _______________________________________________ > Qt5-feedback mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback > > > _______________________________________________ > Qt5-feedback mailing list > [email protected] > http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback > > > _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
