You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@xml.apache.org by James Snell <jm...@intesolv.com> on 2001/02/05 20:25:56 UTC
RE: COM Pluggable provider interest.
Rick,
Just wanted to make sure this didn't get lost... yes, I think there is
interest in this and the work is appreciated. Once you've got it hammered
down a bit more (and once some (haha) free time opens up for me) I'd like to
take a look.
- James
>
> Rick Rineholt/Raleigh/IBM@IBMUS on 01/31/2001 07:34:43 AM
>
> Please respond to soap-dev@xml.apache.org
>
> To: soap-dev@xml.apache.org
> cc:
> Subject: COM Pluggable provider interest.
>
>
>
> I have been working on a Microsoft COM pluggable provider for
> Apache SOAP.
> Currently, I have been able from an Apache SOAP client to invoke on an
> Apache SOAP server, services I have written in MS Visual
> Basic. The code
> as it is today only supports primitive parameters and return
> types. The
> approach taken is a pluggable provider that contains JNI code
> that does the
> marshaling between Java parameters and return types to COM
> Variants and
> creates the COM object and then invokes requested the method. The COM
> object to create is specified as in an option to the
> pluggable provider in
> the deployment descriptor by its progid or CLSID. There is
> no framework to
> support state and to be quite honest the support of COM is at
> an elementary
> level. The code is both Java and C++, which is compiled with
> MS Visual C++
> compiler version 6.0.
>
> What I like to get is a feel from the Apache developers'
> community if this
> is ultimately something it would be interested in having
> contributed to the
> Apache SOAP project.
>
> Rick Rineholt
> "The truth is out there... All you need is a better search engine!"
>
>
>