Re: Connecting db through odbc bridge in tomcat 5.5
TwelveEighty wrote:
On Dec 23, 11:01 am, Arne VajhHj <a...@vajhoej.dk> wrote:
If done properly - no use of MySQL classes, no hardcoded
driver class name or URL, everything read from a config file - then
I would also think MySQL had a weak case.
But most commercial ISV's would not take the chance.
And besides the same ISV's may want the support anyway.
OK, time-out here. I was not aware of these issues with MySQL - I
thought they were the good guys? Can someone explain what the deal
with licensing issues with MySQL is?
What is that potential problem if I use MySQL as a database backend
and use config files for storing of driver names and urls? Do I have
to pay these guys now?
The issue is that the MySQL JDBC driver is released under GPL license
(with FLOSS exception).
It has some implications for usage, because the GPL license states
that code "linked" to GPL code most also be GPL code (or in MySQL
cases: at least be open source).
So:
1) if your solution is GPL or other source => no problem
2) if your solution is only used inhouse (not distribued) => no problem
3) in other cases you may have a problem
I have given some opinions of mine above.
But if your business depend on the answer them you should not
take my word for it but consult an IP lawyer.
You can start reading here:
http://www.mysql.com/company/legal/licensing/opensource-license.html
http://www.mysql.com/company/legal/licensing/foss-exception.html
http://www.mysql.com/company/legal/licensing/commercial-license.html
Arne