I've not been working with Qt for some time now, but if things go well I could
be put on a Qt project which will likely need SOAP. So You might have some help
in a few weeks/months.
________________________________
From: Tomasz Siekierda <[email protected]>
To: Jason H <[email protected]>; Qt5-feedback <[email protected]>
Sent: Monday, August 15, 2011 2:25 AM
Subject: Re: [Qt5-feedback] Web service functionality in Qt5
I'm quite surprised how much stuff you mentioned already is in my project.
>1. A utility to generate a class implmentation files (cpp, h) from the service
>description file (wsdl) containing QObject->derived class so that signals and
>slots are used for the call and return.
This is exactly what I've done, and it's almost finished. My generator
supports both synchronous (through static methods) and asynchronous
(throug signal/ slots mechanism) code generation, qmake, scons, cmake
build systems, various file structures and, just like my web method
implementation, it supports HTTP ('&' arguments), SOAP 1.0, SOAP 1.2
and JSON.
>3. A SOAP 1.2 w/MTOM+XOP is preferred, and about as complicated as ti will
>get. (SOAP w/MIME attachments (As >opposed to base-64 encoded attachments in
>XML (MS XML .NET parsers has performance issues with large >documents, as well
>as the memory implications and more complicated streaming scenarios)
Currently I've just got basic SOAP 1.0 and 1.2 (+ JSON and HTTP, as
mentioned above) functionality, but:
a) everything is arranged so that it can be easily expanded,
b) currently I'm working just for fun and to learn while coding, so up
until now I haven't been too keen to make everything too complicated.
This can change, though :) But will need help, as I certainly lack
some knowledge and experience now.
>Recently there was talk of a QHttpServer class.
>Could we also provide SOAP services from Qt? That is use the MOC to generate a
>WSDL file as well, that way Qt >coouln provide and consume SOAP resources in a
>first-class fashion?
>Of course, my preference is for REST rather than SOAP, but SOAP services
>aren't going away any time soon.
It is indeed a tempting thought. I've tried to construct my project,
so that it is easy to add server functionality, but I have not started
any implementation of it yet - I think we should do it (if indeed we
want to) together with QHttpServer guys.
Anyway, for a quick overview of my project, you can look at
https://gitorious.org/qwebservice/qwebservice/blobs/master/doc/README.txt
Cheers,
sierdzio
On 14 August 2011 20:01, Jason H <[email protected]> wrote:
>
> Oh, one issue was server-side.
> Recently there was talk of a QHttpServer class.
> Could we also provide SOAP services from Qt? That is use the MOC to generate
> a WSDL file as well, that way Qt coouln provide and consume SOAP resources in
> a first-class fashion?
> Of course, my preference is for REST rather than SOAP, but SOAP services
> aren't going away any time soon.
>
>
> ________________________________
> From: Tomasz Siekierda <[email protected]>
> To: [email protected]
> Sent: Saturday, August 13, 2011 9:51 AM
> Subject: [Qt5-feedback] Web service functionality in Qt5
>
> Hi,
> I'm wondering, whether there are some people interested in seeing (even
> basic) web service communication functionality in Qt5? I think that with Qt5
> being heavily QML (and thus, mobile) oriented, some easy way to call web
> methods, without using 3rd party libs, is needed. Currently, a lot of apps do
> require frequent Internet communication (to mention one use case: stock
> exachnge readers) with WSes. Even a simple implementation, capable of getting
> the result fast, without subclassing anything, would be nice, IMO. At the
> same time, it will leave more complicated issues to well established
> packages, like GSOAP.
> Now, to the main point: a couple of months ago I'v started developing a
> project, which aim is to provide Qt devs with the ability to communicate with
> web services. At that time, there was (and still is) GSOAP, but it was not
> made "the Qt way", was IMO too complicated and not terribly intuitive. There
> also was QSoap, which was more Qt-oriented, but AFAIK had some issues, and
> was not recommended. Later on, while I was already hacking on my project,
> I've learned about KDAB's KD Soap - which looks much better than any
> mentioned above, and is definitely more advanced than my QWebService
> (https://gitorious.org/qwebservice).
> In QWebService, I have focused on making it intuitive, heavily Qt-based
> (actually, there are no external dependencies. Communication is made using
> QNAM, XML parsing - Qt XML module, everything is QDoc docummented). It can be
> used both out-of-the-box, using generic classes, or by subclassing. An
> automatic code generator is also included, it can take bot external URL, or
> local file path to WSDL file. I'm currently developing it alone, but if
> anybody is interested, feel invited to join me :) Most of the functionality
> is already there, but there's still a lot room for improvements.
> I'm not saying my solution has to make it into Qt, I'm perfectly fine to go
> with any that will suit Qt developers' needs. I just want to raise the
> subject here, since we still have a lot of time before Qt5 comes out, there
> is some good stuff out there almost ready to be included, and, as I've said -
> I think it's needed. What is your view here? Do we need it inside Qt, or are
> we sticking to current necessity to use 3rd party stuff?
> Cheers
> sierdzio
> _______________________________________________
> 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
