Google

Locations of visitors to this page

Hosted by:
SourceForge

Overview of Java Service Wrapper Licenses
Overview of Java Service Wrapper Licenses
Choosing an Appropriate License

The Java Service Wrapper is being put to use by a wide range of users for a wide range of projects. Including corporate and government infrastracture projects, buildling with commercial products and systems, and open source projects.

The Wrapper is available under any one of three licenses making it possible to choose to license most appropriate for a given project.

The full text of each license can be viewed by clicking on the license name.

  • Community Software License Agreement: This license agreement is the popular GPLv2 license used by many open source projects. For open source projects this is a good choice as it allows the Wrapper to be distributed as part of any application provided that all source of the application is made available to the user base free of charge.

  • Server Software License Agreement: This license agreement is useful for users who wich to use the Wrapper on one or more specific machines. It licenses the user to use multiple copies of the Wrapper on a single machine.

  • Development Software License Agreement: Commercial users who wish to redistribute the Wrapper as part of a larger application, and users who wish to distribute the Wrapper without being tied to specific machines will find this license useful. License keys must be provided for each specific application.

Examples

If you are unsure which license is appropriate for your particular project please read over the following examples.

  • Q: I am a member of a team developing a popular open source project which may or may not be used in commercial situations.

    A: The Community Software License Agreement will work fine in most cases as long as the entire application and all of its components are distributed in such a way that the users of your solution can easily obtain the full source of the entire application.

  • Q: I would like to distribute the Wrapper with our proprietary application to customers.

    A: The Development Software License Agreement will allow you to distribute the Wrapper with your application without any restrictions on how you sell the resulting package.

  • Q: I would like to distribute a modified version of the Wrapper with our proprietary application to customers.

    A: Currently only the Community Edition source is being made available for modification. If it is at all possible, we encourage you to contrubute a patch to the wrapper-user mailing list where it will be discussed. If it fits the goals of the product suite, it will be included for all users to make use of.

    In cases where submitting a patch is not possible, the Development Software License Agreement will allow you to distribute the modified copy of the Wrapper with your application without any restrictions on how you sell the resulting package.





User Comments

If you notice something that is incorrect, missing, or simply feel that some part of this page could be explained better, feel free to log in and add a comment. You will need to register before you can log on.

Email:
Password:
by Josinaldo Leal (2008/11/05 21:54:41 JST from 189.108.186.66)
Gravatar

www.mintternet.com

by Ali Kalufya (2008/06/30 21:02:29 JST from 217.157.58.179)
Gravatar

Is there a factory class that can be used to export modules as Windows services by configuration in Spring Framework fashion?

last modified: