2nd gsoap service with ws4d

35 views
Skip to first unread message

Maxim Akristiniy

unread,
May 14, 2012, 8:40:56 AM5/14/12
to WS4D-gSOAP Users
Hello.
I need to launch 2-nd gsoap service with ws4d device, which will
provide support for wsa2005.
I created shared library with it, and trying to load it from ws4d
executable.
In these library creating process to process requests on different
port with pthread.

But have following error when processing request in shared library :
Error 39 fault: SOAP-ENV:VersionMismatch [no subcode]
"Invalid SOAP message or SOAP version mismatch"
Detail: [no detail]

As I see problem is, that during the library call function, if main
program have function with same name, it calling from main program,
not from library. And because there are different headers even
soap_new() are different in main program and in library.

Is there only one way to use 2-nd gsoap service - create separate
process ?

Elmar Zeeb

unread,
May 14, 2012, 3:35:36 PM5/14/12
to ws4d-gso...@googlegroups.com
Hi Maxim,

Am 14.05.2012 14:40, schrieb Maxim Akristiniy:
> Hello.
> I need to launch 2-nd gsoap service with ws4d device, which will
> provide support for wsa2005.
> I created shared library with it, and trying to load it from ws4d
> executable.
> In these library creating process to process requests on different
> port with pthread.
You can do this with the hosting-service feature. It's a seperation of
device and service part of dpws.

>
> But have following error when processing request in shared library :
> Error 39 fault: SOAP-ENV:VersionMismatch [no subcode]
> "Invalid SOAP message or SOAP version mismatch"
> Detail: [no detail]
>
> As I see problem is, that during the library call function, if main
> program have function with same name, it calling from main program,
> not from library. And because there are different headers even
> soap_new() are different in main program and in library.
>
> Is there only one way to use 2-nd gsoap service - create separate
> process ?
>
It should also be possible to have different headers and name spaces for
services but ws-addressing is a special case. It's built into ws4d-gsoap
directly. So I didn't have a usecase to use two versions of
ws-addressing, so it's not implemented :-). It should be possible but
it's complicated.

Regards,
Elmar

--

*******************************************************************************
Dipl.-Inf. Elmar Zeeb
EXIST-Gr�nderstipendiat Projekt �PipesBox�
Institut f�r Angewandte Mikroelektronik und Datentechnik
Universit�t Rostock, Fakult�t f. Informatik und Elektrotechnik
18051 Rostock
Deutschland/Germany
Tel. : ++49 (0)381 498 - 7262
Fax : ++49 (0)381 498 - 7252
Email: elmar...@googlemail.com
www : http://www.pipesbox.de/
*******************************************************************************

Reply all
Reply to author
Forward
Message has been deleted
0 new messages