easysoap-developers — Developer discussions

[Easysoap-developers] Query related to SOAP version supported.

[Ajay K. <aja...@gm...>]

Hi,

I am using EasySoap 0.6.1 for my application, Can you please let me
know shat SOAP version this library supports. According to SOAP 1.1
specification (http://www.w3.org/TR/SOAP-attachments) if the message
Content-Type is Multipart/Related  the  type parameter of the
Multipart/Related media header will always equal the Content-Type
header for the primary SOAP 1.1 message, i.e., text/xml. But in this
version, the type parameter is missing for Content-Type header.
See code,

SOAPonHTTP::WriteAllHeaders(const char* i_szBoundary, bool
i_bBasicAuth, bool i_bFirstTime)
{
        m_http.BeginPost(m_endpoint.Path());
        m_http.WriteHeader("User-Agent", DEFAULT_USERAGENT);
        if( i_szBoundary ) {
        m_http.Write("Content-Type: multipart/related;
charset=\"UTF-8\"; boundary=\"");

Your comments are most appreciated.

Thanks,
Ajay

Re: [Easysoap-developers] EasySOAP++ Compile Fixes

[Terrence C. <ter...@ze...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Charles,

I submitted almost exactly the same patch a few months ago.  Mine didn't
even make it past list moderation, so I hope this gets applied.  I doubt
it will though: it looks like the SourceForge page has not been updated
since about 2001, so I get the impression EasySoap++ is unmaintained.
SourceForge has facilities for "taking over" an unmaintained project, so
if you want to use ES++ (and it does look to be the best C++ SOAP client
out there), then I would suggest you pursue this.  Fortunately for me,
the API I'm using has a REST interface, so I decided to just use libCURL
instead of going to through the hassle.  If I had had the time or need,
I probably would have done this, since EasySoap++ would be a great
project to resurrect.  I hope someone else will beat me to it though,
since I'm swamped at the moment.

Also, have you uncovered any documentation for EasySoap++ that isn't the
code itself?  This (and gcc4 support) seem to be the main deficiencies
at the moment (but then I haven't used it extensively).

Thanks,
Terrence Cole
CTO, Zettabyte Storage
www.zettabytestorage.com


Charles Samuels wrote:
> This makes EasySOAP++ compile with gcc4...
> 
> Well, actually, gcc4 has a bug: 
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25950 which prevents one of the 
> tests from compiling. I didn't fix that.
> 
> And yes, these changes are C++ standard compliant.
> 
> Charles
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE9LhkzVXxCx8aIkERCjdhAJ0W0MCeqrunxv0lGN22ZHzmzj+yLQCfZfqu
R4xnSqATxtiPs7iZwv4K9Z8=
=JIf0
-----END PGP SIGNATURE-----

[Easysoap-developers] EasySOAP++ Compile Fixes

[Charles S. <ch...@vm...>]

This makes EasySOAP++ compile with gcc4...

Well, actually, gcc4 has a bug: 
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25950 which prevents one of the 
tests from compiling. I didn't fix that.

And yes, these changes are C++ standard compliant.

Charles

[Easysoap-developers] [PATCH] gcc34 build and correctness fixes

[Terrence C. <ter...@tr...>]

I have identified the build problems on gcc 3.4(.5).

In 00_gcc34-compat.patch:

1) gcc34 now requires the "typename" identifier to identify types 
declared behind a class: e.g. DispatchMap::Iterator.  For some of these 
instances, the code was already folded in MEMBER_TYPE() to append the 
"typename" automatically.  I have added MEMBER_TYPE to the other 
instances where it was not applied already.

2) gcc34 is stricter about pointer casting semantics.  In XMLParser.cpp, 
I have added "reinterpret_cast" to the offending implicit casts.

3) gcc34 requires explicit template notification for specializations.

This does not fix all the problems with gcc34.  Unfortunately, the 
AC_CXX_TEMPLATE_KEYWORD_QUALIFIER macro (which sets MEMBER_TYPE) appears 
to be broken on gcc34.  You can work around this with a manual override 
by running configure with CXXFLAGS set to 
"-DHAVE_TEMPLATE_KEYWORD_QUALIFIER".  Someone more expert with autotools 
could probably solve this more elegantly.

This changes will build everything not in the test directory on gcc34.

In tests/interopclient.cpp, there are some quirks with the 
initialization and usage of SOAPHex and SOAPHexBase.  Allowing the use 
of the automatic copy and assign constructor gets rid of the problem.  I 
have included this as a separate patch (01_gcc34-compat.patch) because I 
don't think this is necessarily the right way to solve the problem.  If 
you are using gcc34 and absolutely need tests/interopclient to build, 
you can apply this patch and it will "work".

This patch is taken against the 0.6.1 distribution tarball.  In 
retrospect, I should have taken it against CVS.  I would be happy to 
recreate this patch against CVS if these do not apply correctly there.

Thanks for the awesome SOAP library!
-Terrence

[Easysoap-developers] RE: compile error

[mk <ma...@my...>]

Ulrich Staudinger schrieb:
 > Hi,
 > EasySoap won"t compile, i see the following error: Please help me!
 > Many thanks, i need a solution quick ...
 > Making all in src
 > make[1]: Entering directory
 > `/home/us/work/gmx/vssoapapi/EasySoap++-0.6.1/src"
 > c++ -DHAVE_CONFIG_H -I. -I. -I../include/easysoap -I../include
 > -Wall -g -O2 -c XMLParser.cpp
 > XMLParser.cpp: In method `void EasySoap::XMLParser::FreeParser()":
 > XMLParser.cpp:51: ANSI C++ forbids implicit conversion from `void *"
 > in argument passing

Ran into the same problem. I changed the following in XMLParser.h:
  - void *m_parser;
  + struct XML_ParserStruct *m_parser;

Now it compiles without errors.

I'll assume with the latest expat-1.95.8 some structures changed (compared
to expat-1.95.2). Hope that helps.

mattes

[Easysoap-developers] EasySOAP support on Itanium/x86 with SuSE Enterprise 8 linux

[Virag P. <vir...@re...>]

Hi=0A=0ACan you tell me whether EasySOAP is supported with SUSE =0AEnterpri=
se 8 Linux on Itanium/x86?=0A=0AYour help is very much need.=0A=0AThanks in=
 advance.=0A=0AAwaiting your quick response.=0A=0ARegards,=0AVirag=0A=0A

Re: [Easysoap-developers] compile error

[Ulrich S. <ust...@gm...>]

It' s a plain unpatched distribution release from sf.net.

thanks,
ulrich



Paul Boddie schrieb:

>Ulrich Staudinger [mailto:ust...@gm...] wrote:
>  
>
>>A second ago i did another test compile on a 3.3.1 gcc platform ... 
>>(although not target platform)
>>    
>>
>
>OK. This looks like a different problem entirely, although I'd still
>like some hints from someone about the C++ issues. Is this a plain 0.6.1
>release of EasySoap++ or have there been any updates or patches applied?
>
>Paul
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
>Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
>Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
>REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
>_______________________________________________
>Easysoap-developers mailing list
>Eas...@li...
>https://lists.sourceforge.net/lists/listinfo/easysoap-developers
>
>
>  
>

RE: [Easysoap-developers] compile error

[Paul B. <pau...@em...>]

Ulrich Staudinger [mailto:ust...@gm...] wrote:
>
> A second ago i did another test compile on a 3.3.1 gcc platform ...=20
> (although not target platform)

OK. This looks like a different problem entirely, although I'd still
like some hints from someone about the C++ issues. Is this a plain 0.6.1
release of EasySoap++ or have there been any updates or patches applied?

Paul

Re: [Easysoap-developers] compile error

[Ulrich S. <ust...@gm...>]

A second ago i did another test compile on a 3.3.1 gcc platform ... 
(although not target platform)

us@usdev:~/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1> gcc --version
gcc (GCC) 3.3.1 (SuSE Linux)


With this result:
 
us@usdev:~/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1> make
Making all in include
make[1]: Entering directory 
`/home/us/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1/include'
Making all in easysoap
make[2]: Entering directory 
`/home/us/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1/include/easysoap'
make[2]: Leaving directory 
`/home/us/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1/include/easysoap'
make[2]: Entering directory 
`/home/us/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1/include'
make[2]: Für das Ziel »all-am« ist nichts zu tun.
make[2]: Leaving directory 
`/home/us/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1/include'
make[1]: Leaving directory 
`/home/us/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1/include'
Making all in src
make[1]: Entering directory 
`/home/us/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1/src'
c++ -DHAVE_CONFIG_H -I. -I. -I../include/easysoap -I../include    -Wall 
-g -O2 -c XMLParser.cpp
XMLParser.cpp: In member function `void EasySoap::XMLParser::FreeParser()':
XMLParser.cpp:51: error: invalid conversion from `void*' to 
`XML_ParserStruct*'
XMLParser.cpp: In member function `void 
EasySoap::XMLParser::InitParser(const
   char*)':
XMLParser.cpp:63: error: invalid conversion from `void*' to 
`XML_ParserStruct*'
XMLParser.cpp:66: error: invalid conversion from `void*' to 
`XML_ParserStruct*'
XMLParser.cpp:69: error: invalid conversion from `void*' to 
`XML_ParserStruct*'
XMLParser.cpp:72: error: invalid conversion from `void*' to 
`XML_ParserStruct*'
XMLParser.cpp:74: error: invalid conversion from `void*' to 
`XML_ParserStruct*'
XMLParser.cpp: In member function `void*
   EasySoap::XMLParser::GetParseBuffer(int)':
XMLParser.cpp:81: error: invalid conversion from `void*' to 
`XML_ParserStruct*'
XMLParser.cpp: In member function `bool 
EasySoap::XMLParser::ParseBuffer(int)':
XMLParser.cpp:89: error: invalid conversion from `void*' to 
`XML_ParserStruct*'
XMLParser.cpp: In member function `const char*
   EasySoap::XMLParser::GetErrorMessage()':
XMLParser.cpp:97: error: invalid conversion from `void*' to 
`XML_ParserStruct*'
make[1]: *** [XMLParser.o] Fehler 1
make[1]: Leaving directory 
`/home/us/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1/src'
make: *** [all-recursive] Fehler 1
us@usdev:~/samba_home/work/gmx/vssoapapi/EasySoap++-0.6.1>





Ulrich Staudinger schrieb:

> Hi,
> EasySoap won't compile, i see the following error: Please help me! 
> Many thanks, i need a solution quick ...
> Making all in src
> make[1]: Entering directory 
> `/home/us/work/gmx/vssoapapi/EasySoap++-0.6.1/src'
> c++ -DHAVE_CONFIG_H -I. -I. -I../include/easysoap -I../include    
> -Wall -g -O2 -c XMLParser.cpp
> XMLParser.cpp: In method `void EasySoap::XMLParser::FreeParser()':
> XMLParser.cpp:51: ANSI C++ forbids implicit conversion from `void *' 
> in argument passing
> XMLParser.cpp: In method `void EasySoap::XMLParser::InitParser(const 
> char * = 0)':
> XMLParser.cpp:63: ANSI C++ forbids implicit conversion from `void *' 
> in argument passing
> XMLParser.cpp:66: ANSI C++ forbids implicit conversion from `void *' 
> in argument passing
> XMLParser.cpp:69: ANSI C++ forbids implicit conversion from `void *' 
> in argument passing
> XMLParser.cpp:72: ANSI C++ forbids implicit conversion from `void *' 
> in argument passing
> XMLParser.cpp:74: ANSI C++ forbids implicit conversion from `void *' 
> in argument passing
> XMLParser.cpp: In method `void * 
> EasySoap::XMLParser::GetParseBuffer(int)':
> XMLParser.cpp:81: ANSI C++ forbids implicit conversion from `void *' 
> in argument passing
> XMLParser.cpp: In method `bool EasySoap::XMLParser::ParseBuffer(int)':
> XMLParser.cpp:89: ANSI C++ forbids implicit conversion from `void *' 
> in argument passing
> XMLParser.cpp: In method `const char * 
> EasySoap::XMLParser::GetErrorMessage()':
> XMLParser.cpp:97: ANSI C++ forbids implicit conversion from `void *' 
> in argument passing
> make[1]: *** [XMLParser.o] Error 1
> make[1]: Leaving directory 
> `/home/us/work/gmx/vssoapapi/EasySoap++-0.6.1/src'
> make: *** [all-recursive] Error 1
> us@gmxdev4:/home/us/work/gmx/vssoapapi/EasySoap++-0.6.1>
>                                                                                                               
>
>
> Thanks in advance, ulrich staudinger
>
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
> _______________________________________________
> Easysoap-developers mailing list
> Eas...@li...
> https://lists.sourceforge.net/lists/listinfo/easysoap-developers
>
>

Re: [Easysoap-developers] compile error

[Ulrich S. <ust...@gm...>]

us@gmxdev4:/home/us/work/gmx/vssoapapi/EasySoap++-0.6.1> gcc --version
2.95.3
us@gmxdev4:/home/us/work/gmx/vssoapapi/EasySoap++-0.6.1>


I can't switch to 3.x. 2.95.3 is the target platform for many other 
applications ...



Paul Boddie schrieb:

>Ulrich Staudinger [mailto:ust...@gm...] wrote:
>  
>
>>EasySoap won't compile, i see the following error: 
>>Please help me! Many thanks, i need a solution quick ...
>>    
>>
>
>Which C++ compiler are you using? I've experienced some pretty major
>issues in compiling with gcc 3.4.0, whereas gcc 3.3.x (with the older
>parser) seems a lot more tolerant. I'm not entirely familiar with the
>goings-on in the C++ standardisation rituals these days, but was hoping
>that someone might have some suggestions and/or workarounds.
>
>Paul
>
>
>  
>

RE: [Easysoap-developers] compile error

[Paul B. <pau...@em...>]

Ulrich Staudinger [mailto:ust...@gm...] wrote:
>
> EasySoap won't compile, i see the following error:=20
> Please help me! Many thanks, i need a solution quick ...

Which C++ compiler are you using? I've experienced some pretty major
issues in compiling with gcc 3.4.0, whereas gcc 3.3.x (with the older
parser) seems a lot more tolerant. I'm not entirely familiar with the
goings-on in the C++ standardisation rituals these days, but was hoping
that someone might have some suggestions and/or workarounds.

Paul

[Easysoap-developers] compile error

[Ulrich S. <ust...@gm...>]

Hi, 

EasySoap won't compile, i see the following error: 
Please help me! Many thanks, i need a solution quick ... 

Making all in src
make[1]: Entering directory `/home/us/work/gmx/vssoapapi/EasySoap++-0.6.1/src'
c++ -DHAVE_CONFIG_H -I. -I. -I../include/easysoap -I../include    -Wall -g -O2 -c XMLParser.cpp
XMLParser.cpp: In method `void EasySoap::XMLParser::FreeParser()':
XMLParser.cpp:51: ANSI C++ forbids implicit conversion from `void *' in argument passing
XMLParser.cpp: In method `void EasySoap::XMLParser::InitParser(const char * = 0)':
XMLParser.cpp:63: ANSI C++ forbids implicit conversion from `void *' in argument passing
XMLParser.cpp:66: ANSI C++ forbids implicit conversion from `void *' in argument passing
XMLParser.cpp:69: ANSI C++ forbids implicit conversion from `void *' in argument passing
XMLParser.cpp:72: ANSI C++ forbids implicit conversion from `void *' in argument passing
XMLParser.cpp:74: ANSI C++ forbids implicit conversion from `void *' in argument passing
XMLParser.cpp: In method `void * EasySoap::XMLParser::GetParseBuffer(int)':
XMLParser.cpp:81: ANSI C++ forbids implicit conversion from `void *' in argument passing
XMLParser.cpp: In method `bool EasySoap::XMLParser::ParseBuffer(int)':
XMLParser.cpp:89: ANSI C++ forbids implicit conversion from `void *' in argument passing
XMLParser.cpp: In method `const char * EasySoap::XMLParser::GetErrorMessage()':
XMLParser.cpp:97: ANSI C++ forbids implicit conversion from `void *' in argument passing
make[1]: *** [XMLParser.o] Error 1
make[1]: Leaving directory `/home/us/work/gmx/vssoapapi/EasySoap++-0.6.1/src'
make: *** [all-recursive] Error 1
us@gmxdev4:/home/us/work/gmx/vssoapapi/EasySoap++-0.6.1>
                                                                                                               


Thanks in advance, 
ulrich staudinger

[Easysoap-developers] easySOAP support SwA?

[<vda...@in...>]

Hi,

I'm trying to develop a C++ SOAP Client to access an existing Web service
(Secure).
That Web service uses SOAP with Attachment in their service.

I guess easySOAP supports HTTPS (secure using openSSL).

I want to know if the latest version of easySOAP will support SOAP with
Attachment (SwA using MIME)?

Appreciate your response.

Regards,
Vasanth Dandapani

[Easysoap-developers] newbie question on EasySoap

[vivek200120 <viv...@in...>]

Hi ,


   I am trying to write  a tool like the one on the soap client website.Basically i have written a wsdl parser (based on xmlpull) and now need to "dynamically" call the service using a soap library. I tried generating stubs using gsoap ,but it seems to be too complicated beyond that to get it working on runtime (if anyone is intersted,let me know i can tell u my approach!!) .I am sure it is easier with Easy soap ,because unlike gsoap which requires stubs at compile time ,this is diffferent...  
 so can this be done using Easy soap .how does one go about generating serializers and desrialzers for types present in the wsdl .?any ideas
would appreciate any help..
Vivek

 Click onthe image to chat with me

[Easysoap-developers] newbie question on EasySoap

[vivek200120 <viv...@in...>]

Hi ,


   I am trying to write  a tool like the one on the soap client website.Basically i have written a wsdl parser (based on xmlpull) and now need to "dynamically" call the service using a soap library. I tried generating stubs using gsoap ,but it seems to be too complicated beyond that to get it working on runtime (if anyone is intersted,let me know i can tell u my approach!!) .I am sure it is easier with Easy soap ,because unlike gsoap which requires stubs at compile time ,this is diffferent...  
 so can this be done using Easy soap .how does one go about generating serializers and desrialzers for types present in the wsdl .?any ideas
would appreciate any help..
Vivek

 Click onthe image to chat with me

[Easysoap-developers] RespondWith

[John F. <jf...@we...>]

In my most recent prototype I tentatively added a list of
handlers to SOAPServerDispatch to review and revise the
response envelope before sending.  I tried to use the same
style as the original code for the revision (ie: no boost calls),
registering them with a RespondWith() call instead of a
DispatchTo().  I call the functions SOAPHeaderRevisors using
the same callback strategy.

The motivation for the change is that the WS-Reliability
specification has these loose headers that need to be coordinated,
and the response needs to contain some of these headers too.
I can't just let the header handlers setup the response because I
don't have an event to indicate when all the headers have been
processed.

I'm open to any sort of permutation on review.

Thanks,
John
https://sourceforge.net/projects/easywsrm/

[Easysoap-developers] PATCH: fix build with a recent toolchain

[Bernardo I. <be...@de...>]

Hello,

this patch applies to EasySoap-0.6.1 and fixes
some build problems with recent Linux distros
(I use gcc 3.2.3 on a RedHat 9 look-alike system).

Some configure tests were failing until I've
regenerated the autoconf infrastructure from
scratch with my newer auto-tools versions.

Instead of providing updated versions of
configure and other autogenerated files, I've
included a short autogen.sh script in my patch
to help other people making it themself.

Within the next few days, we'll start porting
EasySoap to a Coldfire-based embedded system
running uClinux. If you are interested in our
changes, I could provide them as patches.



diff -Nur EasySoap++-0.6.1/autogen.sh EasySoap++-0.6.1-bernie/autogen.sh
--- EasySoap++-0.6.1/autogen.sh	1970-01-01 01:00:00.000000000 +0100
+++ EasySoap++-0.6.1-bernie/autogen.sh	2003-05-28 16:54:15.000000000 +0200
@@ -0,0 +1,4 @@
+aclocal
+autoheader
+autoconf
+automake --foreign --add-missing --force
diff -Nur EasySoap++-0.6.1/include/easysoap/SOAPDispatchHandler.h EasySoap++-0.6.1-bernie/include/easysoap/SOAPDispatchHandler.h
--- EasySoap++-0.6.1/include/easysoap/SOAPDispatchHandler.h	2002-05-20 18:56:11.000000000 +0200
+++ EasySoap++-0.6.1-bernie/include/easysoap/SOAPDispatchHandler.h	2003-05-28 16:37:35.000000000 +0200
@@ -61,7 +61,7 @@
 	bool ExecuteMethod(const SOAPEnvelope& request, SOAPMethod& response)
 	{
 		const SOAPMethod& method = request.GetBody().GetMethod();
-		DispatchMap::Iterator i = m_dispatchMap.Find(method.GetName());
+		MEMBER_TYPE(DispatchMap::Iterator) i = m_dispatchMap.Find(method.GetName());
 		if (i)
 		{
 			T *target= GetTarget(request);
@@ -109,7 +109,7 @@
 
 	bool HandleHeader(const SOAPParameter& header, SOAPEnvelope& request, SOAPEnvelope& response)
 	{
-		DispatchMap::Iterator i = m_dispatchMap.Find(header.GetName());
+		MEMBER_TYPE(DispatchMap::Iterator) i = m_dispatchMap.Find(header.GetName());
 
 		if (i)
 		{
diff -Nur EasySoap++-0.6.1/include/easysoap/SOAPHashMap.h EasySoap++-0.6.1-bernie/include/easysoap/SOAPHashMap.h
--- EasySoap++-0.6.1/include/easysoap/SOAPHashMap.h	2002-04-10 09:03:41.000000000 +0200
+++ EasySoap++-0.6.1-bernie/include/easysoap/SOAPHashMap.h	2003-05-29 17:36:44.000000000 +0200
@@ -117,13 +117,13 @@
 	{
 	private:
 		const SOAPHashMap		*m_map;
-		Elements::Iterator		m_index;
+		MEMBER_TYPE(Elements::Iterator)	m_index;
 		HashElement				*m_he;
 		
 		friend class SOAPHashMap<K,I,H,E>;
 
 		// private constuctor that can only be called by SOAPHashMap
-		ForwardHashMapIterator(const SOAPHashMap *map, Elements::Iterator index)
+		ForwardHashMapIterator(const SOAPHashMap *map, MEMBER_TYPE(Elements::Iterator) index)
 			: m_map(map), m_index(index), m_he(0)
 		{
 			if (m_map)
@@ -134,7 +134,7 @@
 			}
 		}
 
-		ForwardHashMapIterator(const SOAPHashMap *map, Elements::Iterator index, HashElement *he)
+		ForwardHashMapIterator(const SOAPHashMap *map, MEMBER_TYPE(Elements::Iterator) index, HashElement *he)
 			: m_map(map), m_index(index), m_he(he)
 		{
 		}
@@ -366,8 +366,8 @@
 		{
 			Clear();
 			Resize(r.GetNumBuckets());
-			SOAPHashMap<A,B,C,D>::Iterator e = r.End();
-			for (SOAPHashMap<A,B,C,D>::Iterator it = r.Begin(); it != e; ++it)
+			typename SOAPHashMap<A,B,C,D>::Iterator e = r.End();
+			for (typename SOAPHashMap<A,B,C,D>::Iterator it = r.Begin(); it != e; ++it)
 				Add(it.Key(), it.Item());
 		}
 		return *this;
@@ -397,7 +397,7 @@
 	 */
 	Iterator Begin() const
 	{
-		return Iterator(this, (Elements::Iterator)m_elements.Begin());
+		return Iterator(this, (MEMBER_TYPE(Elements::Iterator))m_elements.Begin());
 	}
 
 	/**
@@ -407,7 +407,7 @@
 	 */
 	Iterator End() const
 	{
-		return Iterator(this, (Elements::Iterator)m_elements.End());
+		return Iterator(this, (MEMBER_TYPE(Elements::Iterator))m_elements.End());
 	}
 
 
@@ -491,7 +491,7 @@
 	 */
 	void Clear()
 	{
-		for (Elements::Iterator i = m_elements.Begin(); i != m_elements.End(); ++i)
+		for (MEMBER_TYPE(Elements::Iterator) i = m_elements.Begin(); i != m_elements.End(); ++i)
 		{
 			HashElement *he = *i;
 			while (he)
@@ -512,7 +512,7 @@
 	 */
 	void Empty()
 	{
-		Elements::Iterator i;
+		MEMBER_TYPE(Elements::Iterator) i;
 		for (i = m_elements.Begin(); i != m_elements.End(); ++i)
 		{
 			HashElement *he = *i;
@@ -588,7 +588,7 @@
 			while (he)
 			{
 				if (he->m_hash == hash && equals(he->m_key, key))
-					return Iterator(this, (Elements::Iterator)m_elements.Begin() + index, he);
+					return Iterator(this, (MEMBER_TYPE(Elements::Iterator))m_elements.Begin() + index, he);
 				he = he->m_next;
 			}
 		}
@@ -603,7 +603,7 @@
 
 		Elements newelements;
 		newelements.Resize(newsize);
-		Elements::Iterator i;
+		MEMBER_TYPE(Elements::Iterator) i;
 
 		for (i = newelements.Begin(); i != newelements.End(); ++i)
 			*i = 0;
diff -Nur EasySoap++-0.6.1/include/easysoap/SOAPParameter.h EasySoap++-0.6.1-bernie/include/easysoap/SOAPParameter.h
--- EasySoap++-0.6.1/include/easysoap/SOAPParameter.h	2002-05-31 02:50:50.000000000 +0200
+++ EasySoap++-0.6.1-bernie/include/easysoap/SOAPParameter.h	2003-05-28 16:21:44.000000000 +0200
@@ -168,7 +168,7 @@
 		Data(const Data&);
 	};
 
-	friend Data;
+	friend class Data;
 
 	Pool			m_pool;
 	SOAPParameter	*m_parent;
diff -Nur EasySoap++-0.6.1/src/Makefile.am EasySoap++-0.6.1-bernie/src/Makefile.am
--- EasySoap++-0.6.1/src/Makefile.am	2002-06-11 16:49:41.000000000 +0200
+++ EasySoap++-0.6.1-bernie/src/Makefile.am	2003-05-28 16:29:32.000000000 +0200
@@ -1,5 +1,4 @@
 lib_LTLIBRARIES = libeasysoap.la
-lib_LIBRARIES = libeasysoap.a
 THESOURCES = \
 	SOAPBase64.cpp \
 	SOAPBody.cpp \
@@ -33,7 +32,6 @@
 	XMLParser.cpp 
 
 libeasysoap_la_SOURCES = $(THESOURCES)
-libeasysoap_a_SOURCES = $(THESOURCES)
 noinst_HEADERS = \
 	SOAPBodyHandler.h \
 	SOAPClientSocketImp.h \
@@ -45,7 +43,7 @@
 	SOAPStructHandler.h \
 	es_namespaces.h
 
-INCLUDES=-I@top_srcdir@/include 
+INCLUDES=-I@top_srcdir@/include -I/usr/kerberos/include
 
 libeasysoap_la_LDFLAGS = -no-undefined -release "0.6.1"
 
diff -Nur EasySoap++-0.6.1/src/XMLParser.cpp EasySoap++-0.6.1-bernie/src/XMLParser.cpp
--- EasySoap++-0.6.1/src/XMLParser.cpp	2001-11-21 07:00:47.000000000 +0100
+++ EasySoap++-0.6.1-bernie/src/XMLParser.cpp	2003-05-28 21:13:02.000000000 +0200
@@ -48,7 +48,7 @@
 {
 	if (m_parser)
 	{
-		XML_ParserFree(m_parser);
+		XML_ParserFree((XML_ParserStruct *)m_parser);
 		m_parser = 0;
 	}
 }
@@ -58,27 +58,27 @@
 {
 	FreeParser();
 	m_parser = XML_ParserCreateNS(encoding, '#');
-	XML_SetElementHandler(m_parser,
+	XML_SetElementHandler((XML_ParserStruct *)m_parser,
 			XMLParser::_startElement,
 			XMLParser::_endElement);
 
-	XML_SetCharacterDataHandler(m_parser,
+	XML_SetCharacterDataHandler((XML_ParserStruct *)m_parser,
 			XMLParser::_characterData);
 
-	XML_SetStartNamespaceDeclHandler(m_parser,
+	XML_SetStartNamespaceDeclHandler((XML_ParserStruct *)m_parser,
 			XMLParser::_startNamespace);
 
-	XML_SetEndNamespaceDeclHandler(m_parser,
+	XML_SetEndNamespaceDeclHandler((XML_ParserStruct *)m_parser,
 			XMLParser::_endNamespace);
 
-	XML_SetUserData(m_parser, this);
+	XML_SetUserData((XML_ParserStruct *)m_parser, this);
 }
 
 void *
 XMLParser::GetParseBuffer(int size)
 {
 	if (m_parser)
-		return XML_GetBuffer(m_parser, size);
+		return XML_GetBuffer((XML_ParserStruct *)m_parser, size);
 	return 0;
 }
 
@@ -86,7 +86,7 @@
 XMLParser::ParseBuffer(int size)
 {
 	if (m_parser)
-		return XML_ParseBuffer(m_parser, size, size == 0) != 0;
+		return XML_ParseBuffer((XML_ParserStruct *)m_parser, size, size == 0) != 0;
 	return false;
 }
 
@@ -94,7 +94,7 @@
 XMLParser::GetErrorMessage()
 {
 	if (m_parser)
-		return XML_ErrorString(XML_GetErrorCode(m_parser));
+		return XML_ErrorString(XML_GetErrorCode((XML_ParserStruct *)m_parser));
 	return 0;
 }
 


-- 
  // Bernardo Innocenti - Develer S.r.l., R&D dept.
\X/  http://www.develer.com/

Please don't send Word attachments.
See: http://www.gnu.org/philosophy/no-word-attachments.html

RE: [Easysoap-developers] [Easysoap-discussion] Solaris CC Linkin g Problem

[Paul B. <Pau...@em...>]

Ramchandra Phadake [mailto:ram...@pe...] wrote:
> 
> I am having a linking problem with EasySoap library.
> The default EasySoap installation uses gcc to build  the library.
> My client program is built using CC compiler.

From what I remember, it can be difficult to build software on Solaris with
mixtures of compiler and linker. It may be the case that you have to use
various compiler and linker flags, eg. -fPIC and one of the -B flags when
building the EasySoap++ installation with the GNU tools.

> If I use the simpleclient.cpp program (which comes along the tarball)&
> link it against easysoap using gcc it works but with CC it produces many
> undefined symbols.
> 
> I have tried to build the EasySoap using CC & then using CC for building &
> linking against my program but the errors remain.

That would potentially rule out linking errors against libstdc++, then.

> I have to use CC to build the client program.
> 
> What should be done to get EasySoap work with CC ?

Given that you have attempted to use CC (and presumably Sun's ld)
throughout, and still have linking issues, it may be a library search issue
that you're encountering. Which symbols are you missing? One common Solaris
problem is the need to explicitly link against various socket and network
libraries; -lnsl sounds familiar but I can't remember clearly.

Paul

[Easysoap-developers] Solaris CC Linking Problem

[Ramchandra P. <ram...@pe...>]

Hi,

I am having a linking problem with EasySoap library.
The default EasySoap installation uses gcc to build  the library.
My client program is built using CC compiler.

$CC -V
CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-07 2002/04/10

$gcc -v
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.0.3/specs
Configured with:
../configure --with-as=/usr/local/bin/as --with-ld=/usr/local/bin/ld --enabl
e-libgcj
Thread model: posix
gcc version 3.0.3

If I use the simpleclient.cpp program (which comes along the tarball)&
link it against easysoap using gcc it works but with CC it produces many
undefined symbols.

I have tried to build the EasySoap using CC & then using CC for building &
linking
against my program but the errors remain.

I have to use CC to build the client program.

What should be done to get EasySoap work with CC ?

Its very urgent for me to solve this issue.

Thanks.

-Ram

[Easysoap-developers] Solaris CC Linking Problem

[Ramchandra P. <ram...@pe...>]

Hi,

I am having a linking problem with EasySoap library.
The default EasySoap installation uses gcc to build  the library.
My client program is built using CC compiler.

$CC -V
CC: Sun WorkShop 6 update 2 C++ 5.3 Patch 111685-07 2002/04/10

$gcc -v
Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.0.3/specs
Configured with:
../configure --with-as=/usr/local/bin/as --with-ld=/usr/local/bin/ld --enabl
e-libgcj
Thread model: posix
gcc version 3.0.3

If I use the simpleclient.cpp program (which comes along the tarball)&
link it against easysoap using gcc it works but with CC it produces many
undefined symbols.

I have tried to build the EasySoap using CC & then using CC for building &
linking
against my program but the errors remain.

I have to use CC to build the client program.

What should be done to get EasySoap work with CC ?

Its very urgent for me to solve this issue.

Thanks.

-Ram

[Easysoap-developers] Apache 1.3 Series Handler for EasySoap++

[Paul B. <Pau...@em...>]

Hello,

I have recently been working on a project where there has been a need to
have a SOAP handler working within an Apache module. As a result, I have
started to develop this functionality within EasySoap++, based somewhat on
the implementation for CGI handlers (SOAPCGIServer and SOAPCGITransport),
producing two new classes (SOAPApacheServer and SOAPApacheTransport) and
employing some modified Makefiles - I suppose that the automake templates
should really be changed.

Subject to various corporate decisions, I would like to be able to
contribute this work back to the project. However, are there any opinions
about what I've done, and is there any specific advice about the licensing
issues (copyright reassignment and that kind of thing)?

Regards,

Paul

P.S. The work involved wasn't particularly challenging - it just involved
changing where EasySoap++ reads from and writes to. Nevertheless, it is
obviously useful in certain situations.

[Easysoap-developers] Non-blocking EasySOAP++

[Frederik R. <fre...@re...>]

Hi,

   I am using EasySOAP++ both as a server and client in a commercial
development (the whole thing is at an early stage but EasySOAP++
seems a good choice and has done well in my proof-of-concept).

One component where I need to use EasySOAP++ is a single-threaded
multiplexed server, where data has to be read and written from/to
network sockets all the time. I cannot afford to halt the whole
operation while waiting for a SOAP response. I need to integrate
EasySOAP++ into my "select" or "poll" infrastructure (which might be
a glib "main loop", not sure yet). 

I guess I'd be capable of doing that myself somehow, but I'd like to
hear your opinions on this because, if done properly, my efforts
could flow back into the project to be used by others in the same
situation.

I would very much like to solve this problem without multi-threading
(for fear of introducing too much complexity) but I'm willing to do
it if it turns out to be the best solution. 

Does anybody have an idea how to best approach my problem? It seems
that I would have to change a *lot* of classes to solve this
elegantly. 

How about this: Create a new "SOAPAsyncProxy" which acts like a
SOAPProxy but, in its "Execute" method, is passed a new
"SOAPAsyncListener" object (usually the caller itself). I would also
need a new SOAPTransport class that is able to communicate with some
kind of central mutliplexing mechanism, e.g. the glib "main loop".
Calling "Execute" would only create the raw XML and schedule it for
sending, then the central "select" mechanism would interact with the
SOAPTransport and associated classes to perform reading and writing,
in multiple steps if required (control of execution passing back and
forth between EasySOAP++ components and the select loop by means of
interfaces/callbacks). When the last byte has been read, the response
is parsed and control is transferred in a call-back to SOAPAsync-
Listener.

Does this sound like something that would fit into the rest of the
EasySOAP++ framework, or rather like an "ugly add-on"? Any better
ideas? Any pitfalls I have overlooked?

Bye
Frederik

-- 
Frederik Ramm  ##  eMail fre...@re...  ##  N49°00.22' E008°24.56'

Re: [Easysoap-developers] EasySoap

[Blaise St-L. <bst...@N-...>]

On Mon, 2002-03-25 at 12:26, Willem Duminy wrote:
> Thank you for the reply.
> 
> You'd be glad to know that I am convinced.  I got the SOAP client to call a 
> remote web service - and I must say, it is easier than I thought!  

Glad to here it! It's really an incredible toolkit, hats of to David for
creating it in such a clean way! :)

> 
> Is anyone working on the WSDL part of the problem?  What about implementing 
> some kind of XSLT based translator: from WSDL to a easySOAP definition?  
> 
The biggest problem is that in effect, you're asking for a way to
dynamically create functions in C++, which traditionally has been a
rather difficult thing to do in a strongly typed language. Since most of
the definitions of the Web Services are created at compile time, it
would be rather difficult to re-engineering the EasySoap libs to be able
to create a set of generic functions (not impossible mind you, just
difficult). As well, the WSDL spec isn't really ironed out yet, and
writing a WSDL parser is non-trivial. 

The simplest way i could see doing it is writting a WSDL to C++ parser
that writes out the stubs for you, but that's of limited use really.

If you want to take a crack at it, i'm sure people on this list have
some good ideas..

> I played around with xslt_proc on Redhat (I think it comes with GNOME), but 
> it does not work as I expected.  Anyone know of a better option?
> 

Not really, as i said, it's not an easy problem to tackle.


> 
> _______________________________________________
> Easysoap-developers mailing list
> Eas...@li...
> https://lists.sourceforge.net/lists/listinfo/easysoap-developers

Re: [Easysoap-developers] EasySoap

[Willem D. <wd...@mw...>]

Thank you for the reply.

You'd be glad to know that I am convinced.  I got the SOAP client to call a 
remote web service - and I must say, it is easier than I thought!  

Is anyone working on the WSDL part of the problem?  What about implementing 
some kind of XSLT based translator: from WSDL to a easySOAP definition?  

I played around with xslt_proc on Redhat (I think it comes with GNOME), but 
it does not work as I expected.  Anyone know of a better option?

Regards,
Willem

On Monday 25 March 2002 16:45, you wrote:
> On Sat, 2002-03-23 at 16:31, Willem Duminy wrote:
> > Hi Guys,
> > I am new to SOAP and web services.
> > Is EasySOAP a good choice to call existing we services from Linux?  I'd
> > like to use C++.
>
> Generally speaking, we'd like to think so :)
>
> It all depends on what your expectations are. We currently don't support
> WSDL so if you want to use that as a way of discovering the web service,
> then you're out of luck.
>
> That being said, if you know the details (e.g. parameters, returns,
> servicename and namespace) then yes, EasySOAP is a great choice.
>
> If you take a look at the website, specifically :
>
> http://easysoap.sourceforge.net/interop/interop2a.html
> http://easysoap.sourceforge.net/interop/interop2b.html
> http://easysoap.sourceforge.net/interop/interop2c.html
>
> You'll see that we do quite well working with various other soap
> implementations.
>
> For the record:
> I'm using EasySOAP in a comercial production environment, using it both
> as a client and a server, as well as interfacing with SOAP::Lite and
> SOAPx4 and certain Microsoft components.
>
>
> It's also fairly easy to use as far as toolkits go, it took some of the
> people working here less then a day to ramp up on the basics of writting
> a client.
>
> > -Willem
> >
> > _______________________________________________
> > Easysoap-developers mailing list
> > Eas...@li...
> > https://lists.sourceforge.net/lists/listinfo/easysoap-developers
>
> _______________________________________________
> Easysoap-developers mailing list
> Eas...@li...
> https://lists.sourceforge.net/lists/listinfo/easysoap-developers

Re: [Easysoap-developers] EasySoap

[Blaise St-L. <bst...@N-...>]

On Sat, 2002-03-23 at 16:31, Willem Duminy wrote:
> Hi Guys,
> I am new to SOAP and web services.
> Is EasySOAP a good choice to call existing we services from Linux?  I'd like 
> to use C++.

Generally speaking, we'd like to think so :)

It all depends on what your expectations are. We currently don't support
WSDL so if you want to use that as a way of discovering the web service,
then you're out of luck. 

That being said, if you know the details (e.g. parameters, returns,
servicename and namespace) then yes, EasySOAP is a great choice. 

If you take a look at the website, specifically :

http://easysoap.sourceforge.net/interop/interop2a.html
http://easysoap.sourceforge.net/interop/interop2b.html
http://easysoap.sourceforge.net/interop/interop2c.html

You'll see that we do quite well working with various other soap
implementations. 

For the record: 
I'm using EasySOAP in a comercial production environment, using it both
as a client and a server, as well as interfacing with SOAP::Lite and
SOAPx4 and certain Microsoft components. 


It's also fairly easy to use as far as toolkits go, it took some of the
people working here less then a day to ramp up on the basics of writting
a client. 


> -Willem
> 
> _______________________________________________
> Easysoap-developers mailing list
> Eas...@li...
> https://lists.sourceforge.net/lists/listinfo/easysoap-developers