You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by so...@idoox.net on 2000/08/10 18:03:08 UTC
ANN: IdooXoap pre-release
Hello everybody.
We're proud to announce the pre-release of IdooXoap, a Java
implementation of a SOAP library, compatible (in present features)
with MS and Apache (IBM) implementations.
Our implementation uses the SOAP Contract Language (SCL), it is even
able to (de)serialize any linked graph, and above that handles remote
interface references.
Until we set up the infrastructure for supporting an open-source
project only a package with demos and binaries of the library is
released. By the end of August the sources will be released under
(L)GPL.
The homepage is at http://www.zvon.org/index.php?nav_id=30 and the
package itself is at http://www.zvon.org/idooxoap/download/package.zip
It has been developed under JDK1.3beta and tested on Linux.
Share and enjoy.
the Idoox SOAP crew
P.S: Sorry about the cross-posting but I don't know the overlap in the
lists...
Re: ANN: IdooXoap pre-release
Posted by Jacek Kopecky <ja...@idoox.com>.
> Is this an arbitrary graph of java objects? Do you handle collections of collections
> etc? Also, since there is no source to examine, what do you mean handles
> 'remote interface references'? Could you elaborate?
I'm sorry I forgot to mention the remote interface references...
These allow you to pass around references to interfaces, i.e. a client
can give a server its stub and the server will get a stub of its own,
or the server can return an object that implements a service and the
client will get a stub for that object.
This all is shown in the demo 'interrefs' where references to a
Counter services are passed around.
Jacek Kopecky
Re: ANN: IdooXoap pre-release
Posted by Jacek Kopecky <ja...@idoox.com>.
> Is this an arbitrary graph of java objects? Do you handle collections of collections
> etc? Also, since there is no source to examine, what do you mean handles
> 'remote interface references'? Could you elaborate?
I'm sorry I forgot to mention the remote interface references...
These allow you to pass around references to interfaces, i.e. a client
can give a server its stub and the server will get a stub of its own,
or the server can return an object that implements a service and the
client will get a stub for that object.
This all is shown in the demo 'interrefs' where references to a
Counter services are passed around.
Jacek Kopecky
Re: ANN: IdooXoap pre-release
Posted by Jacek Kopecky <ja...@idoox.com>.
> > Our implementation uses the SOAP Contract Language (SCL), it is even
> > able to (de)serialize any linked graph, and above that handles remote
> > interface references.
>
> Is this an arbitrary graph of java objects? Do you handle collections of collections
> etc? Also, since there is no source to examine, what do you mean handles
> 'remote interface references'? Could you elaborate?
Yes, that is an arbitrary graph of java objects. But we now handle
only public members of objects and we don't have special serializers
for java.util.* so we don't handle any java.util collections. On the
other hand any other structures linked with public members are OK.
We actually now seem to prefer not to use native structure classes, we
generate client stubs and structure helpers from an SCL description
and the service implementation/client can then use these structure
helpers that do have public members.
Jacek Kopecky
Re: ANN: IdooXoap pre-release
Posted by Jacek Kopecky <ja...@idoox.com>.
> > Our implementation uses the SOAP Contract Language (SCL), it is even
> > able to (de)serialize any linked graph, and above that handles remote
> > interface references.
>
> Is this an arbitrary graph of java objects? Do you handle collections of collections
> etc? Also, since there is no source to examine, what do you mean handles
> 'remote interface references'? Could you elaborate?
Yes, that is an arbitrary graph of java objects. But we now handle
only public members of objects and we don't have special serializers
for java.util.* so we don't handle any java.util collections. On the
other hand any other structures linked with public members are OK.
We actually now seem to prefer not to use native structure classes, we
generate client stubs and structure helpers from an SCL description
and the service implementation/client can then use these structure
helpers that do have public members.
Jacek Kopecky
Re: ANN: IdooXoap pre-release
Posted by Rich Johns <rj...@vignette.com>.
soapguru@idoox.net wrote:
> Hello everybody.
> We're proud to announce the pre-release of IdooXoap, a Java
> implementation of a SOAP library, compatible (in present features)
> with MS and Apache (IBM) implementations.
> Our implementation uses the SOAP Contract Language (SCL), it is even
> able to (de)serialize any linked graph, and above that handles remote
> interface references.
Is this an arbitrary graph of java objects? Do you handle collections of collections
etc? Also, since there is no source to examine, what do you mean handles
'remote interface references'? Could you elaborate?
>
> Until we set up the infrastructure for supporting an open-source
> project only a package with demos and binaries of the library is
> released. By the end of August the sources will be released under
> (L)GPL.
> The homepage is at http://www.zvon.org/index.php?nav_id=30 and the
> package itself is at http://www.zvon.org/idooxoap/download/package.zip
> It has been developed under JDK1.3beta and tested on Linux.
> Share and enjoy.
>
> the Idoox SOAP crew
>
> P.S: Sorry about the cross-posting but I don't know the overlap in the
> lists...
Re: ANN: IdooXoap pre-release
Posted by Rich Johns <rj...@vignette.com>.
soapguru@idoox.net wrote:
> Hello everybody.
> We're proud to announce the pre-release of IdooXoap, a Java
> implementation of a SOAP library, compatible (in present features)
> with MS and Apache (IBM) implementations.
> Our implementation uses the SOAP Contract Language (SCL), it is even
> able to (de)serialize any linked graph, and above that handles remote
> interface references.
Is this an arbitrary graph of java objects? Do you handle collections of collections
etc? Also, since there is no source to examine, what do you mean handles
'remote interface references'? Could you elaborate?
>
> Until we set up the infrastructure for supporting an open-source
> project only a package with demos and binaries of the library is
> released. By the end of August the sources will be released under
> (L)GPL.
> The homepage is at http://www.zvon.org/index.php?nav_id=30 and the
> package itself is at http://www.zvon.org/idooxoap/download/package.zip
> It has been developed under JDK1.3beta and tested on Linux.
> Share and enjoy.
>
> the Idoox SOAP crew
>
> P.S: Sorry about the cross-posting but I don't know the overlap in the
> lists...