At 10:08 31/10/00 +0600, you wrote:
>We are developing our packaged enterprise application server, and are very
>keen on basing it around jBOSS/Tomcat. On top of this, we would add our own
>libraries, and management related features, and package and resell it as a
>product.
>
>Again, like Vince, I am NOT A LAWYER! So please excuse any license-related
>misconceptions I may have, and please help clarify them! :)
>
>1) As I understand it, achieving what I hope to achieve above, Tomcat's
>Apache license will work fine, as long as I state that I use Tomcat as a
>base engine to my product (and provide the relevant disclaimers, links to
>the Tomcat sources, etc etc).
nope - that is illegal.
>2) What about GPL? How would I integrate jBOSS into this product? I
>understand that any code enhancements I make to jBOSS would be GPL'd as
>well - this is fine with me, as I am willing to contribute. I would even
>assign a team to constant jBOSS and Tomcat development and contribution.
anything the is in the same jvm would becom GPL'ed
>3) How would this affect my company's proprietary code and libraries, which
>we hope to ship with the product? In addition, we will be writing GUI
>installers, JavaBeans to the libraries (as plugins to IDE's), etc etc.
>Other proprietary stuff further down the line may be resource pooling and
>cacheing algorithms, transaction managers, other performance enhancements,
>etc etc. How would this proprietary code be affected, and would it be
>affected by incorporating jBOSS into the product?
Anything that was in the same JVM would cease to be propritry and start to
be covered by GPL which means that you would have to give away all these
libraries.
Cheers,
Pete
*------------------------------------------------------*
| "Nearly all men can stand adversity, but if you want |
| to test a man's character, give him power." |
| -Abraham Lincoln |
*------------------------------------------------------*
