gSOAP on OpenVMS Blog

gSOAP on OpenVMS v.11 Released

2011-09-29T15:25:00.000+02:00

gSOAP on OpenVMS v.11 is now available. See the release notes for additional information.

If you would like a kit, please submit an email to brett.r.cameron(at)gmail.com and johndapps(at)gmail.com stating which platform and, if you have time, your intent for the software.

Please see the BC&JA homepage for additional information and other available products from the world of open source.

gSOAP on OpenVMS V.10 released

2011-03-24T12:11:00.000+01:00

V.10 of gSOAP on OpenVMS is now available for download.

You may wish to peruse the release notes prior to requesting a kit by sending an email to brett.r.cameron(AT)gmail.com stating platform and OpenVMS version.

If you are an ACMS user, you might want to glance through the gSOAP FIDDLE User Guide, an utility which translates STDL into WSDL, thus automating the process of exposing ACMS Tasks as Web Services.

We are always happy to hear from people using the software and do try to listen to what you all have to say and recommend!

NOTE: please ensure that any DCL symbols for compilers and linkers are deleted prior to building gSOAP applications!

To align or not to align, that is the question!

2010-11-22T10:49:00.003+01:00

All of the gSOAP runtime is compiled with member alignment (and needs to be for various reasons), so if you have code you are integrating with that contains structures that need to be compiled with /nomember_alignment, you will have to be a little careful about how you mix and match; however, aligned and unaligned structures can happily co-exist, if you do things right. What I typically do in this circumstance is to use the following #pragma directives:

#pragma member_alignment save

#pragma nomember_alignment

/* unsligned.h contains structures that need /nomember_alignment (or you could just include the actual structure definitions within

The #pragma directives */

#include "unaligned.h"

#pragma member_alignment restore

Please ensure that generated gSOAP stubs and code that includes gSOAP header files is compiled with member alignment. Note that you can use the #pragma statements to include in your code structures that are not aligned.

The following brief example might help to illustrate how to adjust for aligned and unaligned structures being mixed in the same program module.

___________________________________

#ifndef __UNALIGNED_H__
#define __UNALIGNED_H__

typedef struct
{
   double a;
   double b;
   char str[60];
}
unaligned_i_struct_t;

typedef struct
{
   double result;
   char str[60];
}
unaligned_o_struct_t;

#ifdef __cplusplus
    extern "C" {
#endif

extern int unaligned_cstruct(unaligned_i_struct_t *, unaligned_o_struct_t *);

#ifdef __cplusplus
    }
#endif
#endif

_____________________________________________________

#include       /* toupper() */
#include
#include "unaligned.h"

int unaligned_cstruct(unaligned_i_struct_t *ibuf, unaligned_o_struct_t *obuf)
{
   char *tmp;

   obuf->result = ibuf->a * ibuf->b;
   strcpy(obuf->str, ibuf->str);
   tmp = obuf->str;
   while (*tmp)
   {
      *tmp = toupper(*tmp);
      tmp++;
   }
   return (1);
}

______________________________________

#include "soapH.h"
#include "cstruct.nsmap"

/* Change value of PORT to your assigned port number */
#define PORT 9191

int main(int argc, char **argv)
{
   int m, s;             /* master and slave sockets */
   struct soap soap;

   soap_init(&soap);

   m = soap_bind(&soap, NULL, PORT, 100);
   if (m < 0)
   {
      soap_print_fault(&soap, stderr);
      exit(-1);
   }

   fprintf(stderr, "Connection successful: master socket = %d\n", m);

   while (1)
   {
      s = soap_accept(&soap);
      fprintf(stderr, "Connection successful: slave socket = %d\n", s);
      if (s < 0)
      {
         soap_print_fault(&soap, stderr);
         exit(-1);
      }
      soap_serve(&soap);
      soap_end(&soap);
   }

   return 0;
}

____________________________________________

//gsoap ns service name:        cstruct
//gsoap ns service style:       rpc
//gsoap ns service encoding:    encoded
//gsoap ns service location:    http://www.somewhere.com:9191/cstruct.exe
//gsoap ns schema namespace:    urn:cstruct

struct i_struct
{
   double a;
   double b;
   char *str;
};

struct o_struct
{
   double result;
   char *str;
};

int ns__cstruct(struct i_struct *ibuf, struct o_struct *obuf);

____________________________________

#include "soapH.h"
#include       /* toupper() */

#pragma member_alignment save
#pragma nomember_alignment
#include "unaligned.h"
#pragma member_alignment restore

int ns__cstruct(struct soap *soap, struct i_struct *ibuf,
                                   struct o_struct *obuf)
{

    unaligned_i_struct_t unaligned_ibuf;
    unaligned_o_struct_t unaligned_obuf;

    unaligned_ibuf.a = ibuf->a;
    unaligned_ibuf.b = ibuf->b;
    strcpy(unaligned_ibuf.str, ibuf->str);

    unaligned_cstruct(&unaligned_ibuf, &unaligned_obuf);

    obuf->result = unaligned_obuf.result;
    obuf->str = soap_strdup(soap, unaligned_obuf.str);

       return (SOAP_OK);
}
_______________________________

$! build.com

$ cc:=cc ! ensure that CC is really CC and not some symbol

$ lin*k:= ! ensure the LINK command is just that

$ soapcpp2 :== $gsoap$root:[bin]soapcpp2.exe
$
$ soapcpp2 "-c" cstruct.h
$ cc/names=(as_is,shortened)/prefix=all/float=ieee/ieee=denorm -
/warning=(disable=EMPTYSTRUCT) -
/include=gsoap$root:[include] cstruct.c
$
$ cc/names=(as_is,shortened)/prefix=all/float=ieee/ieee=denorm -
/warning=(disable=EMPTYSTRUCT) -
/extern=common/share_global/nomember_alignment -
/include=gsoap$root:[include] unaligned.c
$
$ cc/names=(as_is,shortened)/prefix=all/float=ieee/ieee=denorm -
/warning=(disable=EMPTYSTRUCT) -
/include=gsoap$root:[include] main.c
$ cc/names=(as_is,shortened)/prefix=all/float=ieee/ieee=denorm -
/warning=(disable=EMPTYSTRUCT) -
/include=gsoap$root:[include] soapc.c
$ cc/names=(as_is,shortened)/prefix=all/float=ieee/ieee=denorm -
/warning=(disable=EMPTYSTRUCT) -
/include=gsoap$root:[include] soapserver.c
$
$ link/exe=cstruct.exe main,cstruct,unaligned,soapc,soapserver,sys$input/opt
gsoap$root:[lib]gsoap.olb/lib
$

gSOAP on OpenVMS V0.9 Released

2010-11-19T12:20:00.001+01:00

BC&JA are happy to announce that V09 of gSOAP on OpenVMS is now available for download.
You may wish to peruse the release notes prior to requesting a kit by sending an email to brett.r.cameron(AT)gmail.com and johndapps(AT)gmail.com stating platform and OpenVMS version.

If you are an ACMS user, you might want to glance through the gSOAP FIDDLE User Guide, an utility which translates STDL into WSDL, thus automating the process of exposing ACMS Tasks as Web Services.

We are always happy to hear from people using the software and do try to listen to what you all have to say and recommend!

NOTE: please ensure that any DCL symbols for compilers and linkers are deleted prior to building gSOAP applications!

gSOAP on OpenVMS V0.8 Released

2010-07-07T16:36:00.000+02:00

BC&JA are happy to announce the latest version of gSOAP on OpenVMS!
The Release Notes contain information on installation and operation of the software.

The major additions in this release follow:

Plug-ins
gSOAP provides a powerful mechanism for extending its capabilities through the use of plug-ins, and a variety of pre-existing plug-in modules are available. These plug-ins are now included with the OpenVMS kit and may be found in the gsoap$root:[plugin] directory. There are plug-ins to support HTTP GET requests, WS-Security, and many more. It should be noted that not all of the supplied plug-ins have been tested on OpenVMS, and the authors would appreciate feedback on any issues that are encountered.

DOM support
The gSOAP DOM implementation is now provided and may be utilised by linking applications with the object library gsoap$root:[lib]gsoapdom.olb. Please note that this library also includes SSL support, and it is therefore necessary to link applications with the OpenVMS SSL libraries (see Section 4.4). This requirement will be removed in future releases.

WS-Security (WSSE) example
An example program that illustrates the use of the WSSE plug-in is now included with the distribution. This fairly complicated example also uses the gSOAP DOM implementation and SSL. It should be noted that it will be necessary to obtain new certificates in order to use the SSL functions.

Please do let us know how you get on with this latest kit! As always, send an email to brett.r.cameron(AT)gmail.com and johndapps(AT)gmail.com stating whether you require Alpha or Integrity or both kits.

gSOAP on OpenVMS V0.7 Released

2010-05-26T11:06:00.001+02:00

BC&JA have released version 0.7 of gSOAP on OpenVMS for Alpha and Integrity. The release notes and installation guide contain notes on changes specific to the OpenVMS version.
This releases encompasses all changes and additions made to the gSOAP Version 2.7.9 and its revisions. See the following list and http://www.cs.fsu.edu/~engelen/soap.html for further information.

Version 2.7.9 revisions a/b/c/d/e/f/g/h/i/j/k/l (10/24/2006-09/26/2007)

Added wsdl2h option -j to omit the generation of SOAP Header and Faults for customization of these.
Added wsdl2h option -q to generate C++ namespace qualified header files.
Added SOAP_SSLv3, SOAP_TLSv1, SOAP_SSL_SKIP_HOST_CHECK flags.
Added file input and output specifications (with < and >) to wsdl2h's typemap.dat to specify input and output for wsdl2h.
Added WS-Addressing 2005/03 support.
Added function soap_free() = soap_done() + free() and renamed previous soap_free() to soap_temp_free().
Added wsdl2h option -_ to translate _USCORE.
Added xsd:anyAttribute (using DOM parser) with wsdl2h option -d.
Added multi-WSDL types section schema component merging.
Added TCP keep-alive settings.
Added QName list normalization.
Changed soapcpp2 default rule for generating attribute form qualified to unqualified.
Improved wsdl2h SOAP Fault coding.
Improved performance and stability.
Improved portability.
Improved wsdl2h empty namespace handling ("" namespace).
Improved wsdl2h and schema conversion to C and C++.
Improved SSL timeouts and error handling.
Improved soapcpp2 option -i (generate proxy and service classes).
Improved class instance initialization.
Improved use of IPv6.
Improved proxy and server code output for soapcpp2 option -i.
Improved soapcpp2 code output with additional exception checks.
Fixed MIME/MTOM start id handling (SOAP message no longer required to be first attachment).
Fixed WS-Security wsse plugin canonicalization format issue.
Fixed ZIP content remainder parsing (CRC check).
Fixed WSA API handling of messages with MIME/DIME attachments.
Fixed wsdl2h relative path includes.
Fixed _XML literal string parsing of root attributes.

Please do let us know whether you would like a kit and state if for Alpha or Integrity. This release is only available for OpenVMS 8.3 and higher. If you require a kit or need a release for OpenVMS 7.3-2, then please drop us an email at brett.r.cameron (AT) gmail.com and johndapps (AT) gmail.com.

Regards, BC&JA

gSOAP on OpenVMS Kit Announcements

2010-01-18T16:59:00.006+01:00

BC&JA are proud to formally announce that Version 06 for gSOAP on OpenVMS is available!

Version 06 includes support for FastCGI and multi-national character sets such as Hebrew. The release have been updated to include documentation on using gSOAP with Apache FastCGI and with WASD. We have created a new Web page for FastCGI on OpenVMS and encourage you to take a look.

Please see the first comment to this entry for details on additional Web Services you might wish to try. We hope to provide examples of these with the next kit release. Meanwhile, if you manage to implement one or two, we would be very happy to include them in the kit!

Please send a brief note requesting a kit to:

brett.r.cameron@gmail.com and
johndapps@gmail.com

Please specify in your mail:

OpenVMS version (can be 7.3.-2 on Alpha)
Hardware platform (Alpha or Integrity)

You may review the installation guide and release notes prior to requesting a kit. C++ is not required unless you wish to develop code using that language, of course. If you using ACMS, you might also wish to peruse the FIDDLE

Please do leave a comment, it can be anonymous if you prefer, when you download a kit!

We very much wish to keep track of who is using the software. Why?

So that we can influence management to turn the gSOAP on OpenVMS software into a supported Open Source product, for instance
So that we can write SPAM mails to you :-)
So that we can see how much interest there really is...

Regards, BC&JA

gSOAP Kit Announcements

2009-05-24T20:30:00.008+02:00

BC&JA are truly ecstatic to announce that
Version 06 for gSOAP on OpenVMS is available!

Version 06 includes updated documentation and a completely rewritten user guide for (Fast Interface Dynamic Definition Language for lusty Enterprises) FIDDLE, a tool for developing gSOAP interfaces for HP ACMS applications.

Version 06 includes support for FastCGI and multi-national character sets such as Hebrew. The release notes have been updated to include documentation on using gSOAP with Apache FastCGI and with WASD. We have created a new Web page for FastCGI on OpenVMS and encourage you to take a look.

There will be an update to this note shortly where we hope to announce a few Web Services which you may call from Xignite.

Please send a brief note requesting a kit to:

brett.r.cameron@gmail.com and
johndapps@gmail.com

Please specify in your mail:

OpenVMS version (can be 7.3.-2 on Alpha)
Hardware platform (Alpha or Integrity)

You may review the installation guide and release notes prior to requesting a kit. C++ is not required.

Please do leave a comment, it can be anonymous if you prefer, when you download a kit!
We very much wish to keep track of who is using the software.

Why?

So that we can influence management to turn the gSOAP on OpenVMS software into a supported Open Source product, for instance
So that we can write SPAM mails to you :-)
So that we can see how much interest there really is
...

Regards, BC&JA

Type of support required for gSOAP on OpenVMS?

2007-11-10T15:52:00.000+01:00

Please indicate through a comment how and if you would like support for gSOAP from the OpenVMS engineering group.
Some possible items:

support should be part of the OpenVMS support contract, similar to the Apache Web Server
support can come from a group other than OpenVMS for which a small fee (how much?) can be paid
support must be available 24x7, 5x8 (office hours), world-wide
the gSOAP news list and other sources on the Web suffice
no support required

Old gSOAP kit announcement.

2007-10-31T13:30:00.015+01:00

This entry has been replaced by the gSOAP Kit Announcements. The entry has been retained due to the valuable comments entered against it.

Regards, BC&JA

Introduce Yourselves!

2007-10-30T20:28:00.000+01:00

We would be very happy to hear about what you are doing and how things are progressing!

If you prefer to post anonymously, then that is fine. If, however, you feel you would like to get in touch and let us know more about what you are doing, but do not wish to publish that information here, then please drop us an email at:

Brett.R.Cameron (AT) gmail.com
JohnDApps (AT) gmail.com
Thomas.Siebold (AT) gmail.com

Thank you!

Bugs found in gSOAP on OpenVMS

2007-10-30T20:26:00.000+01:00

Every attempt has been made to provide stable and tested software. However, things can go wrong...
Please report bugs that you find with the gSOAP on OpenVMS software here.
Don't forget to mention:

platform (Alpha or Integrity)
OpenVMS version
name of the gSOAP kit you are using (the ZIP file name)
source code required to reproduce the problem (if possible) or at least sufficient detail for the problem to be investigated further

Suggestions for gSOAP on OpenVMS

2007-10-30T20:16:00.001+01:00

Please enter comments containing your suggestions and ideas around gSOAP on OpenVMS.

Questions about gSOAP on OpenVMS documentation

2007-10-30T20:15:00.001+01:00

Questions about gSOAP on OpenVMS documentation. Please enter comments and questions to this blog entry about the gSOAP on OpenVMS documentation.

Questions about gSOAP on OpenVMS software

2007-10-30T20:13:00.000+01:00

Please resond to this entry with questions about the gSOAP on OpenVMS software.

Welcome to the gSOAP on OpenVMS Blog

2007-10-30T15:32:00.001+01:00

This blog is intended for the users of gSOAP on OpenVMS.
The blog is currently open to all comers in the hope that it will not be abused by people who insist on posting rubbish...

There is a gSOAP discussion group on Yahoo! that you might wish to regsiter with.

So, welcome!