Dare I say it... Why not try VS.NET... Nah. gSOAP is one product, Systinet WASP C++ is another.
-----Original Message----- From: Benjamin Tomasini [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 04, 2003 11:00 AM To: [EMAIL PROTECTED] Subject: Re: client in C++ There was some discussion on this list about a product called gSOAP. Ben On Tue, 2003-02-04 at 10:03, Ghershony, Arie wrote: > Hi, > I developed a webservice using axis in Java. the client application is in > C++. doees any one can give me an idea how to go about invoking the service > using C++? > > Thanks. > Arie > > -----Original Message----- > From: Tom Jordahl [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 04, 2003 9:45 AM > To: '[EMAIL PROTECTED]' > Subject: RE: bean serializer and field names like A_BCD (underscore) > > > > The meta-data (including the XML name of the fields) are in the WSDL2Java > generated Beans. Look for the FieldDesc type. > > JAX-RPC specifies XML Schema -> Java mappings for names of complex types so > they match the JavaBean style of naming (lower case letters start variable > names). This should NOT affect the generated XML. > > You should try Axis 1.1beta and the latest CVS to see if this problem has > been fixed. > > Tom Jordahl > Macromedia Server Development > > -----Original Message----- > From: Dmitri Colebatch [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, February 04, 2003 6:48 AM > To: [EMAIL PROTECTED] > Subject: bean serializer and field names like A_BCD (underscore) > > Hey all, > > I'm using the bean serializer for a fairly boring javabean, and most of the > process is going well - however... I have a couple of fields - G_L_ACCT and > C_AMT_BAPI - that aren't coming through properly; they come through as: > > <g_L_ACCT xsi:type="xsd:string">4703000</g_L_ACCT> > <c_AMT_BAPI xsi:type="xsd:string">100.00</c_AMT_BAPI> > > where the rest of the fields are fine. I'm suspecting that this has to do > with the underscore in the name. Now, I see a few possible answers: > 1. There's something in the javabean spec that explains this > 2. There's some assumption in the bean serializer that explains this. > > Now, looking at the BeanSerializer (release 1.0), there doesn't seem to be > anything obvious screaming out at me, so I'm leaning towards explanation #1 > but I find it hard to believe that is the source of the problem. > > The next thing I see in the code is comments about metadata, although I'm > not sure where this comes from, I haven't been able to find any doco on the > serializers apart from the basics at http://ws.apache.org/axis/index.html - > am I missing something, or could someone point me in the right direction > here? > > I suppose my other option is to write my own serializer, which will no doubt > lead to another email, but I'm not that far yet... > > cheers > dim > >
