close

Contact Information:

Product Inquiry:

License FAQ

Please find below some of the most frequently asked questions regarding the licensing of ICEsoft open source and binary products. If your question is not answered below please do not hesitate to contact us and we will do our best to get your question answered. For more detail or clarity in interpreting the Mozilla Public License and/or the Apache 2 License, interested parties are advised to consult their own legal counsel.

Frequently Asked Questions

Open Source Licenses

  1. What open source license(s) does ICEsoft use?
  2. Where can I get a copy of the MPL Version 1.1 or Apache 2?
  3. Are ICEsoft open source product bundles available under licenses other than MPL or Apache 2?
  4. Does ICEfaces require links to 3rd party software that are licensed differently?
  5. Why change to Apache 2 from MPL?
  6. What is a derived work?
  7. What can I do under the Apache 2 licenses?
  8. How can I use ICEfaces and still protect my own developed intellectual property?
  9. Am I free to commercially license my code under a different license?

Commercial Licenses for ICEsoft's Enterprise Edition Products

  1. What are the various agreements and licenses associated with ICEsoft Enterprise Edition (EE) product?
  2. Do I still have access to ICEsoft EE product source code under the ICEsoft EE End User License Agreement?
  3. Can I continue to develop, use, and deploy my copy of ICEsoft EE Product software even if I let my subscription expire?
  4. Are my customers licensed under my ICEsoft End User License Agreement or will they be required to take one out for themselves?
  5. Is there a royalty for deploying ICEsoft EE Products in a runtime environment?

Commercial Licenses for ICEpdf Pro

  1. What are the various agreements and licenses associated with ICEpdf Pro?
  2. Do I still have access to source code under the ICEsoft End User License Agreement?
  3. Can I continue to develop, use, and deploy my copy of ICEpdf Pro software even if I let my subscription expire?
  4. Are my customers licensed under my ICEpdf Pro subscription or will they be required to take one out for themselves?
  5. Is there a royalty for deploying ICEpdf Pro software in a runtime environment?

Open Source Licenses

  1. What open source license(s) does ICEsoft use?

    ICEsoft's open source products released after January 1, 2012, are licensed under the Apache 2 License.

    Products released into production prior to January 1, 2012 were subject to the Mozilla Public License 1.1 (MPL), or a derivative thereof.

  2. Where can I get a copy of the MPL Version 1.1 or Apache 2?

    The official copy of the Apache License Version 2.0 can be found at https://www.apache.org/licenses/LICENSE-2.0/

    The official copy of the Mozilla Public License Version 1.1 can be found at http://www.mozilla.org/MPL/

  3. Are ICEsoft open source product bundles available under licenses other than MPL or Apache 2?

    Tool Integration bundles for ICEfaces related products are available under the ICEsoft Community Edition license. This license covers binary product bundles and permits free development and distribution of the covered products. It is made accessible to you for review as part of the download process.

    ICEsoft products can also be made available to customers under a standard ICEsoft commercial source code license available with the purchase of ICEpdf Pro or and an ICEfaces Enterprise Edition product subscription. The commercial source code license provides features such as warranty and indemnification. For information on our commercial licenses please fill out our information request form.

  4. Does ICEfaces require links to 3rd party software that are licensed differently?

    ICEfaces, ICEmobile and ICEpdf are all 100% standards based products and are engineered to work within J2EE and general Java based environments. As such they do require links to other 3rd party Java libraries, font libraries etc. Prospective downloaders should be aware that ICEsoft will frequently bundle these 3rd party libraries alongside our own software as part of the download package. This is done for the convenience of our downloaders. For the most part these libraries originate from companies such as SUN and JBoss and are licensed under APACHE or CDDL licenses. A complete list of bundled third party libraries and their respective license information can be found as part of your download.

  5. Why change to Apache 2 from MPL?

    Our decision to migrate from MPL to Apache 2 was based on a set of business criteria that we felt needed to be met in order for our open source initiatives to be successful. First we felt that we needed to use a license that was generally recognized and well received by the open source community. Our sense is that Apache 2 has been established itself as the preferred license technology for medium to large-scale enterprises. Second, we needed to be assured that the license reflect the spirit of open source in its treatment of developer attribution while maintaining business friendly features. Third we believed that the license needed to be clear and unambiguous in stating that end users are under no obligation to open source their application code, and remain free to license their software under whatever commercial conditions they choose. After an extensive review of license models we determined that the MPL best met these business criteria.

  6. What is a derived work?

    Simply put, if you modify any file of the ICEsoft open source software other than a configuration file you are creating a derived work. If you copy and paste chunks of ICEfaces open source software or include ICEsoft open source software which is licensed under Apache 2.0, within the body of a different code base you are creating a derivative work.

    ICEsoft interprets its project code bases to be dynamically linkable software libraries as that term is commonly used in the industry (i.e. code from the library never actually exists within the body of your program). Linking to ICEsoft open source software or making function calls on them from another program, or bundling ICEsoft open source software alongside other applications, does not create a derivative work. The Apache 2 license does not require anyone to make available the source code of programs that use ICEsoft open source software in this manner, and permits those programs (other than the ICEsoft open source software) to be distributed under licenses chosen by the licensor.

  7. What can I do under the Apache 2 licenses?

    Under the Apache 2.0 license you can:

    • Make and distribute unlimited copies of ICEsoft open source software without payment of royalties or license fees provided you give recipients of the software a copy of the Apache 2.0 license.
    • Make changes to the source code of ICEsoft open source software and use those changes internal to your company without having to share those source code changes with others.
    • Make changes to the source code of ICEsoft open source software and distribute those changes to any number of third parties provided you retain the attribution to the original code developers in the manner prescribed in the Apache 2. license.
  8. How can I use ICEfaces and still protect my own developed intellectual property?

    Provided that you have not modified the ICEsoft open source software to create a derivative work as described above in "What is a derived work?" you are under no obligation to disclose your own code base. You can sell or license your software under any license or terms that you wish, except that any ICEfaces open source software must be distributed under the terms of the Apache 2.0 license.

  9. Am I free to commercially license my code under a different license?

    Yes. Provided that you have not created a derivative work of the ICEsoft open source software, you can license your software under any license and terms as you see fit (although ICEsoft open source software must still be licensed under the Apache 2.0 license).

Commercial Licenses for ICEsoft's Enterprise Edition Products

  1. What are the various agreements and licenses associated with ICEsoft Enterprise Edition (EE) product?

    There are two relevant documents associated with an ICEsoft Enterprise Edition license:

    • Apache 2.0 License - The majority of ICEsoft EE product software is shipped under the Apache 2.0 Open-Source license.
    • ICEsoft End User License Agreement - This is a parent level agreement that covers general license terms and conditions for the software and collateral that is made accessible as part of ICEsoft's EE products. It addresses rights and obligations associated with license features such as warrantee, indemnification, and maintenance and support, and provides source code licensing conditions for any non-open source software included in the bundles.
  2. Do I still have access to ICEsoft EE product source code under the ICEsoft EE End User License Agreement?

    Yes. All software provided as part of ICEsoft EE products that is not already covered by the open source Apache 2.0 License, is made available under the ICEsoft EE End User License Agreement. This provides the customer a perpetual, restricted, non-transferrable, non-exclusive development license to use and modify the software in both source code and binary formats. Depending on the nature of the subscription purchased, there may restrictions regarding the use and deployment of the software that the user should be familiar with.

  3. Can I continue to develop, use, and deploy my copy of ICEsoft EE Product software even if I let my subscription expire?

  4. Yes. Both the Apache 2.0 and the ICEsoft End User License Agreement under which commercial ICEsoft software is made available are "perpetual" licenses. The Enterprise Push Server Software and the Composite Component Library however are subject to certain distribution restrictions, and while you can continue to use, develop and deploy them after your subscription expires you can only do so in conjunction with the original application or project you took out the subscription for, and then only onto the number of servers for which you were originally licensed. Once your subscription expires, however, you will lose access to product updates, maintenance releases and the Customer Wiki, and ICEsoft will have no obligations to provide support, indemnification or warrantee beyond the active subscription term.

  5. Are my customers licensed under my ICEsoft End User License Agreement or will they be required to take one out for themselves?

  6. The ICEsoft End User License Agreement allows for multi-tier deployment. This means as far as ICEsoft is concerned, your customers are free to use and re-distribute the application(s) for which you procured an ICEfaces EE subscription without having to take out an ICEfaces EE subscription of their own. This is provided that their usage does not violate any of the restrictions that may have applied to your initial subscription purchase (i.e. licensed applications, server numbers etc.). ICEsoft's warrantee and indemnification coverage does not extend to them, and they are not entitled to direct access of ICEfaces EE software, maintenance releases, training collateral, support etc., unless such access has been provided for in your original subscription procurement.

  7. Is there a royalty for deploying ICEsoft EE Products in a runtime environment?

    The majority of ICEfaces EE software is available under the Apache 2.0 License and as such, you have unlimited, royalty-free distribution rights associated with it. Some software elements, such as the Enterprise Push Server and the Composite Component Library are licensed under the ICEsoft EE End User License Agreement. While there is no ongoing "royalty fee" associated with this software, depending on the subscription procured, the usage of these software elements may be restricted to being associated with the application / project you named when you took out the subscription, and distribution may be restricted to the number of servers identified by the subscription you purchased. These restrictions survive expiration of your subscription (i.e. you can continue to deploy the software even after your subscription expires provided you continue to abide by the original application / server number restrictions). Should you require additional server licenses beyond those granted in your original subscription, please contact sales.

Commercial Licenses for ICEpdf Pro

  1. What are the various agreements and licenses associated with ICEpdf Pro?

    There are two relevant documents associated with an ICEsoft End User License Agreement:

  2. Do I still have access to source code under the ICEsoft End User License Agreement?

    Most software provided as part of ICEpdf Pro is covered by the open source Apache 2.0 License. The ICEpdf Font Engine software is available in source code format but is subject to additional licensing costs and is covered under the ICEpdf Pro Commercial Source Code License.

  3. Can I continue to develop, use, and deploy my copy of ICEpdf Pro software even if I let my subscription expire?

    Yes. Both the Apache 2.0 and the ICEsoft End User License Agreement under which ICEpdf Pro software is made available are "perpetual" licenses. The software is however subject to certain distribution restrictions, and while you can continue to use, develop and deploy them after your subscription expires you can only do so in conjunction with the original application or project you took out the subscription for, and then only onto the number of clients for which you were originally licensed. Once your subscription expires, however, you will lose access to product updates, maintenance releases and the Customer Wiki, and ICEsoft will have no obligations to provide support, indemnification or warrantee beyond the active subscription term.

  4. Are my customers licensed under my ICEpdf Pro subscription or will they be required to take one out for themselves?

    The ICEsoft End User License Agreements all allow for multi-tier deployment. This means as far as ICEsoft is concerned, your customers are free to use and re-distribute the application(s) for which you procured an ICEsoft End User License Agreement without having to take out a license of their own. This is provided that their usage does not violate any of the restrictions that may have applied to your initial product purchase (i.e. licensed applications, server numbers etc.). ICEsoft's warrantee and indemnification coverage does not extend to them, and they are not entitled to direct access of ICEsoft software, maintenance releases, training collateral, support etc., unless such access has been provided for in your original product procurement.

  5. Is there a royalty for deploying ICEpdf Pro software in a runtime environment?

    The majority of ICEpdf software is available under the Apache 2.0 License and as such, you have unlimited, royalty-free distribution rights associated with it. Software elements associated with ICEpdf Pro however, such as the ICEpdf Font Engine are licensed under the ICEpdf End User License. Depending on the terms of procurement, the usage of these software elements may be restricted to being associated with the application / project you named when you took out the subscription, and distribution may be restricted to the number of servers or end users as identified by the license you purchased. These restrictions survive expiration of your subscription (i.e. you can continue to deploy the software even after your subscription expires provided you continue to abide by the original application / server number restrictions). Should you require additional server licenses beyond those granted in your original subscription, please contact sales.