[Info-vax] Axis2 for VMS

[Richard Maher]

Hi Arne,

"Arne Vajhøj" <arne at vajhoej.dk> wrote in message
news:4aeba31e$0$274$14726298 at news.sunsite.dk...
> Richard Maher wrote:
> > Can someone please point me at the latest HP web-pages containing
> > information on Axis2 for VMS?
> >
> > I keep getting directed to: -
> > http://h71000.www7.hp.com/openvms/products/ips/axis2/index.html
> >
> > Which is quite old and tells me that Axis2 replaces the SOAP/Toolkit and
> > that Axis2/VMS is a complete port of  the Apache Axis2 1.3 project, but
when
> > I go to apache's web site: -
> > http://ws.apache.org/axis2/
> >
> > that tells me that 1.5.1 is the latest version. What's more, I can't
find
> > anywhere to download Axis2/C for VMS as in: -
> > http://ws.apache.org/axis2/c/
>
> Why do you think Axis2/C for VMS should be there because Axis2/Java for
> VMS exist?

1) Because they are two sides of the same coin.
2) VMS customers have much more C/3GL code than JAVA that they'd like to
expose to SOAP
3) If HP was ever to support a SOAP via 3GL option for its VMS customers
then logic and consistency dictates it would be the industry standard Apache
Axis2/C.
4) HP/VMS already has the implementation teams and lines of communication in
place with Apache via the Axis2/JAVA implementation.
5) Both the JAVA and C implementations of the Axis2 architecture are
designed and implemented by the same people that designed an implemented the
HP-chosen/HP-supported Apache Web-Server on VMS [C]SWS
6) The expectation of the most seemless and smoothest integration and
compatibility experience, across versions, between Web-Server, SOAP
architecture, and Operating System must surely come from an Industry
Standard Apache Web-Server and the Apache implementation of an Apache SOAP
architecture supported and integrated by HP on a HP operating system
7) Axis2/C could enable the joke that is the Waste of Substantial Investment
in Technology (WSIT) to be retired and funds freed up for more worthy causes
8) Axis2/C could free up the HP/VMS resources that have been wated on gSOAP
for far more worthy causes
9) Any HP/VMS support for gSOAP or other SOAP implementation would send a
clear signal to customers that not only was Axis2/C for VMS never gonna
happen but also that Axis2/JAVA was dead in the water. (Perhaps along with
Apache SWS?)
10) According to Arne, gSOAP can be ported to VMS in somebody's lunch time,
so why should Axis2/C require any more investment?

I dunno; it all stacks up pretty well for me! Pray tell "Why do *you* think
Axis2/C for VMS should [not] exist?".

I'll tell you what, if we could delay things a bit so that those busily
building their gSOAP fifth-column-esque empire could scuttle over to the
Axis2/C for VMS implementation would that satisfy you?

> It is two different products

No they are not. They are two implementations of the same modular SOAP
archictecture both of which have been designed, driven and implemented by
the same orginization. But if Arne stands up here and proclaims that there
is absolutely no cross-fertilization or coordination between the two
implementations then I'll not argue with you but rather ignore you.

>
> And why are you surprised that the VMS version of something is
> not based on the latest version? That is more the rule than the
> exception.

My purpose here was less about expressing emotion and more about fact
finding the HP support status for Axis2. To that end I consulted the very
recent Swedish TUD presentations (that have now ripped down by those that
don't want the truth getting out). As reported in my initial post, there I
found only a single crappy Axis2 slide sandwiched between 12 slides of Cecil
B DeMill's gSOAP presentation and 10 slides of WSIT.

My personal interpretation of those slides is that is that the overriding
factor dictating HP/VMS investment in middleware technology is all about
keeping the incumbents' snouts in the trough. (Certainly nothing to do with
VMS Customers' best interests.) I guess some things never change :-(

>
> Arne

Regards Richard Maher