[SoapRMI] licence issues
Aleksander Slominski
aslom_at_cs.indiana.edu
Fri, 01 Feb 2002 08:09:45 -0500
Pollähne. Ullrich wrote:
> I am currently evaluating XSoap/SoapRMI for the communication between a
> client (GUI) and a server.
nice to hear it.
> Is there any licence text except the ones in the source code files?
the license should be included in distribution and is basically the same as Apache
but with change to our lab, here it is:
Indiana University Extreme! Lab Software License
Version 1.1
Copyright (c) 2001 Extreme! Lab, Indiana University. All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions
are met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in
the documentation and/or other materials provided with the distribution.
3. The end-user documentation included with the redistribution, if any,
must include the following acknowledgment:
"This product includes software developed by the Indiana University
Extreme! Lab (http://www.extreme.indiana.edu/)."
Alternately, this acknowledgment may appear in the software itself,
if and wherever such third-party acknowledgments normally appear.
4. The names "Indiana University" and "Indiana University Extreme! Lab"
must not be used to endorse or promote products derived from this
software without prior written permission. For written permission,
please contact http://www.extreme.indiana.edu/.
5. Products derived from this software may not use "Indiana University"
name nor may "Indiana University" appear in their name, without prior
written permission of the Indiana University.
THIS SOFTWARE IS PROVIDED "AS IS" AND ANY EXPRESSED OR IMPLIED
WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
IN NO EVENT SHALL THE AUTHORS, COPYRIGHT HOLDERS OR ITS CONTRIBUTORS
BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR
OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF
ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> The licence states that we are allowed to use and redistribute the
> software in binary form and we 'only' need to reproduce the copyright
> notice in out documentation. Does this mean that we are allowed to
> create a commercial software that uses XSoap/SoapRMI and 'only' need to
> include the copyright notice in the documentation?
this is the same as for Apache license (which is said to be commercial use friendly
not like GNU). it is also good idea to let us know if you use XSOAP as it gives us
motivation to keep working on improving it, and your suggestions about limitations
/ imporvements will be taken very seriously into consideration :-)
> Excuse me if this was discussed lately (I was not able to find
> sufficient information in the list archive).
> I am also interested in the interoperability between the Java XSoap and
> the C++ XSoap. What are the plans for the C++ version?
current pre release version is now publicly available form our XSOAP page.
both Java and C++ versions *should* be able to interoperate but it was not tested
recently - so there can be minor incompatibilities ....
we are working on performance tuning and evaluation of both Java and C++ XSOAP as
there were some deep changes since last time we did it
> Is it planned to port the C++ version to Win32?
we are thinking about it but currently there no immediate plans to do it (not
enough manpower :-)). we would really welcome somebody to give it a try (we would
help as much as we can but it is not that easy task ...)
thanks,
alek